Shift verification
Shift verification asks the on-call user to confirm they are available when a duty segment starts. Incido sends a notification through the user's notification contact methods. Acknowledgement closes the verification; a timeout notifies team administrators.
Verification uses effective shift history (durable duty segments), not the live computed-shift view. See Rotations and overrides.
When verification runs
Verification runs when all of the following are true:
- Your organization has the on-call feature on its subscription.
- The schedule is Available for on-call.
- Verification is enabled for that schedule (directly or by inheriting the organization default).
- A new effective duty segment enters in progress for the on-call user.
At most one verification exists per effective shift.
Organization defaults
Open Settings → Organization settings → On-call verification:
| Setting | Purpose |
|---|---|
| Enable shift verification by default | When on, schedules that Inherit organization default run verification unless overridden. Default is on for new organizations. |
| Verification timeout (minutes) | How long to wait for a response before timing out (3–1440 minutes; default 15). |
Per-schedule override
On the schedule view, Edit schedule includes Shift verification:
- Inherit organization default
- Enabled
- Disabled
Disabling verification at organization or schedule scope cancels open verifications for the affected scope.
What the on-call user sees
When verification triggers, Incido pages the on-call user using their contact methods (same delivery order as incident pages).
- Acknowledge from the notification (or linked My notifications page) marks the verification verified.
- If the user does not respond before the timeout, the verification is timed out, open notification attempts fail, and team administrators receive email.
Shift verification notifications appear in personal notification history alongside incident escalations.
Recent verifications
On the schedule view, Recent verifications lists verification attempts: status, on-call user, effective shift, and timestamps. Use it to audit whether responders confirmed availability.
Relationship to incident alerting
Shift verification is separate from escalation policies. It confirms the scheduled person is ready at shift start. Incident pages still follow Escalation policies.
The On-call overview landing does not list verification state; check My notifications or the schedule's Recent verifications table.
Operational effects
Verification settings take effect on the next eligible effective shift. Turning verification off cancels open verifications for that scope.
Timeout duration is stored in seconds internally; the Dashboard form uses minutes.
Troubleshooting
Verification never fires. Confirm organization default or schedule mode is enabled, the schedule is available for on-call, and computed shifts show the user on duty. Check Recent verifications for suppressed or completed attempts.
User cannot acknowledge. Only the notification recipient can acknowledge while status is awaiting response. Expired or timed-out verifications are terminal.
Admins received timeout email but user was available. Check contact methods and delivery order under profile settings. Review Recent verifications and notification history for failed channel attempts.
Related guides
- On-call schedules — per-schedule verification mode
- Rotations and overrides — effective shift history
- On-call overview — personal notifications and landing
- Escalation policies — incident paging