Calls drop, people are busy, systems go down. These are the moments that decide whether a CX leader trusts Sayra. Each state says when it appears and what happens next, for the team and for the caller.
A · Call status
Every call in Live carries exactly one status, always as icon + word, so colour is never the only signal.
Sayra · on track
Default. No action needed.
Frustration rising
Mood down 3 turns in a row.
Asked for a person
Honoured at once, shown for the record.
Needs approval
A guardrail asks a person first.
Handing over
Packet sent, waiting for a person.
With a person
Priya has the call.
Resolved
Goal met, confirmation sent.
Caller hung up
Ended before resolution.
B · Handover edge cases
The promise is “a person, with the full story”. These states keep it when the team is busy or something breaks.
B1 Nobody is free
When: No person accepts within 30 s; queue is full.
Waiting for a person · 2:10
Sayra to caller:
“Everyone's helping other travellers right now. I can keep looking for flights with you while you wait, or Priya can call you back within 15 minutes. Which would you prefer?”
B2 Handover not accepted
When: The person misses the 10 s accept window.
Re-routed to the next available person with the same packet. The caller hears nothing new; the wait counter keeps going.
Re-routed to Marcus · 0:14
B3 Caller hangs up mid-handover
When: Line drops while waiting for a person.
Caller hung up
The handover becomes a callback task with the packet attached. An SMS goes out:
“Sorry we got cut off. Priya will call you back in the next 15 minutes.”
B4 Emergency words
When: Medical, safety or threat words detected.
Priority handover · skipped the queue
No questions first, no hold. The packet marks it as urgent for the person.
C · When Sayra or a system fails
Sayra says what's wrong in plain words and hands over, instead of guessing.
C1 Booking system offline
When: An integration doesn't respond in 3 s.
Booking system not responding
Sayra to caller:
“I can't reach our booking system right now. Let me get a colleague who can help another way.”
All rebooking calls switch to “hand over first” until it's back.
Auto-switched 14 calls
C2 Low confidence on a policy
When: No approved source above 80% confidence.
Generative answer blocked. Sayra uses the scripted fallback:
“I want to give you the right answer on that, so I'll ask a colleague.”
Declarative fallback used
C3 Publish blocked
When: A critical test fails in simulation.
1 critical test failing
“Medical reason at the gate” must pass before v14 can go live. A lead can override with a written reason.