Simple path
Keep live chat, typing and callback recovery in one place
The live lane should feel like a real support center: recover the thread, then move the team into the ticket or callback queue.
Flow Conversation Live Hub
Live chat, presence och delivery
Tenant: global | Mode: Ready | Presence: Available
Conversation hubLaunch reportGo live nowTickets hubCallback hubCallback SLATicket SLASupport centerROI export pack
Live recovery path
Keep the live chat lane readable and recoverable
When presence, typing or callback dispatch drifts, send the team to the exact lane that can recover the conversation without breaking the thread.
Keep typing, delivery and presence together in one lane.
Move to tickets, callbacks or support command based on the pressure.
Hand off to launch mode once the live lane is stable.
Live recovery
Keep the chat lane readable while customers are still active
This strip is for live threads that need presence, delivery and callback recovery to stay in one customer-facing lane.
Keep thread state visible so operators know the customer is still there.
Pull missed-call recovery into the same live lane.
Move straight into launch mode when the lane is ready.
Open tickets
0
Waiting internal
0
Callback queued
0
Callback overdue
0
Typing & read receipts
Signals stay visible in the support thread
Support and customer typing, read receipts and delivery state should stay attached to the same thread-level workflow.
Presence service
Available
Keep dispatch, queue and callback state in one support surface so the next owner can act without hunting for context.
Work next
Live chat lane is ready
This lane is for the support team when typing, presence and callback dispatch need a quick operational read.
Delivery states
Typing, sent, retry and sent-again remain part of the live support thread.
Callback motor
Missed-call recovery should always stay one click away from the support lane.
Launch decision
Ready for handoff
Realtime support strip
Typing, presence and callback dispatch in one live lane
Keep the customer conversation easy to read: the live chat state, callback state and ticket owner should all point at the same next move.
Keep message delivery visible while the thread is active.
Available keeps ownership clear for the next responder.
Missed-call recovery stays one click away from the live lane.