
Table of contents
Teams Calls
Teams calls are one of the clearest signals of active collaboration. WorkSights receives a complete record of each call after it ends, with every participant's real session duration, without accessing any meeting content.
Teams call activity does not depend on audit logging. It arrives through Microsoft Graph and works whatever your tenant's audit status.
For connection steps, see Connecting Microsoft 365.
What WorkSights Receives
When a call ends, WorkSights receives the call record, including the organizer, participants, and each session. Every mapped participant gets their own activity, titled with the participant names, reflecting their actual time in the call from first join to last leave. Joining from multiple devices or rejoining after a drop is folded into that single duration automatically.
On connect, WorkSights imports 29 days of call history, which is Microsoft's limit.
How It Appears in WorkSights
Each participant's call appears as a single block in the Call category, reflecting their actual attendance. Calls appear after they end, not while in progress, and process within about 20 minutes of ending.
If the call was scheduled on the calendar, both entries coexist on purpose: the calendar event reflects the scheduled time, and the call entry reflects what actually happened.
What Is Not Captured
Audio, video, transcripts, chat logs, screen shares, and meeting notes are never received. External participants are visible only to the extent Microsoft's call record identifies them, which is usually minimal.
Troubleshooting
A call is not appearing during the call
This is expected. Call records are created after the call ends.
Call activity is missing for a user
Confirm the user is mapped and the Teams Calls feature is enabled for them. Confirm the call ended after the connection was made, or falls within the 29-day backfill window.
Activity appears late
This is expected. Calls process within about 20 minutes of ending.