Out-of-Office Analytics
Measure absence days, affected appointments, handoff success, and conflicts across users and teams
The Out of office tab in Analytics shows how planned absences affect appointments and whether automatic handoffs succeed.
Open Analytics, select Out of office, then choose a date range. The same user, team, and group filters used elsewhere in Analytics also apply here. Company admins can review the company; workspace admins and analytics viewers only see users covered by their existing Analytics permissions.
Metrics
| Metric | Meaning |
|---|---|
| Out-of-office days | Total absence time that overlaps the selected date range. Partial days are shown as decimals. |
| Affected appointments | Future appointments considered when an out-of-office period activated in the selected range. |
| Successful handoffs | Affected appointments reassigned to another host. |
| Unassignable appointments | Affected appointments that could not be reassigned. |
| Average time to successful handoff | Average processing time for successful automatic reassignments. |
The user and team tables show the same measures as a breakdown. A user who belongs to more than one team contributes to each relevant team row, but is counted only once in the totals.
Absence days are clipped to the part of the absence that overlaps the selected range. Handoff metrics belong to the range in which the out-of-office period started, so a long absence is not counted as a new handoff in every later report.
Conflict causes
The conflict list groups unassignable appointments into bounded categories, such as no available teammate, an availability check failure, a handoff failure, or no configured target. Calendar event titles and other private calendar details are not stored in Analytics.
Older out-of-office records were created before detailed timing and conflict categories were recorded. Their successful and unassignable counts are still included, but unavailable timing is shown as a dash and their conflict cause is labelled as historical/unknown.
Cancelled out-of-office periods are excluded because their actual active duration cannot be reconstructed reliably.
Use the results
- A high unassignable count usually means the backup team needs more coverage or fewer calendar conflicts.
- A recurring No target cause means the absent user was the only eligible queue member or no backup target was configured.
- Compare team rows before changing queue membership so you can see where absence coverage is concentrated.
Related articles
Was this article helpful?
Let us know if this article answered your questions.