Flow Callback SLA Hub
Tenant: global | Missed-call recovery med tidszonssignal
Callback recovery path
Dispatch, retry and timezone policy should lead straight to the next owner action, not just a queue count.
Keep overdue, unattempted and timezone risk together.
Route to dispatch, retry or owner handoff immediately.
Publish the callback plan once the queue is under control.
Self-serve recovery
Use this lane when dispatch, retry and timezone checks need to be visible to the team before more calls are lost.
Open the callback queue and work overdue items first.
Check timezone signal before dispatching more retries.
Push the callback lane into launch mode and ship the current plan.
Callback strip
The callback queue should show urgency, dispatch ownership and timezone health in one place for the operator.
0
0
0
0
0
0
Work next
Lead path: missed-call queue, overdue callbacks and retry coverage should be worked before normal triage.
Attempt coverage - 0 utan försök
Köra retry-orchestration och fallback till message-lane.
| Lane | Signal | Status | Action | Open |
|---|---|---|---|---|
| Attempt coverage | 0 utan försök | ok | Köra retry-orchestration och fallback till message-lane. | Öppna |
Review cadence
Owner: Callback ops | Next review: 2026-06-22 10:00:00
Callback recovery automation
Cron route: /flow/scheduler/callback/recovery/run | Secret: FLOW_CALLBACK_RECOVERY_CRON_SECRET | Schedule: Veckovis måndag 10:00 Europe/Stockholm