What Happens When Nobody Picks Up
Every alert is designed for the case where somebody is watching. The interesting design is the other case. A drawing of the ladder our live chat climbs when a customer is waiting and nobody has answered — and what it teaches about any alert that matters.
An alert that reaches one person on one screen is a bet that the person is looking at that screen. Most of the time the bet pays. The question that decides whether an alert system can be trusted is what happens on the afternoon it does not: the representative has gone to make tea, the laptop lid is shut, the phone is in a bag. This is the ladder our live chat with AWRA support climbs in that case, rung by rung.
The ladder
At once — the people on shift
Every representative who is online gets a push to the AWRA app on their phone, a browser notification that stays on screen until it is clicked, and an alert card inside the app showing who is waiting, from where, what they wrote and how long they have waited. The card rings every few seconds until someone acts.
At 45 seconds — everyone who can answer
If nobody has picked it up, the push goes to every support owner, online or not, with the title changed to say the chat is still waiting.
At two minutes — the shared inbox
An email to the support inbox, naming the customer, their organization, their first message and how long they have waited, with a link straight into the chat.
At three minutes — a promise instead of a wait
The customer is told the conversation has gone to the support inbox and will be answered by email. Their messages and files travel with it.
Any time — someone answers
The first reply, or a press of Accept, claims the chat. Every rung that has not fired yet is cancelled, and the alerts on everyone else’s screens clear.
What “online” means
A representative counts as online when they have switched themselves on and some page of AWRA of theirs has checked in within the last forty-five seconds — any page, not just the chat console, so working on something else does not take them off the rota. Close every tab and within a minute they are offline, and customers stop being offered live chat. The rota is a fact about who is reachable, not a toggle somebody forgot to turn off.
Each rung fires once
Two things check the ladder: the customer’s own chat, every few seconds while they wait, and a background sweep every minute for the customer who closed their tab. Each rung is claimed in a single database write that only one of them can win, so the two-minute email is sent once however many times the question is asked.
Positions we hold
We do not page people who are off shift for a chat that someone on shift can take; the wider net only opens at forty-five seconds. We do not leave a customer watching a spinner past three minutes; a written promise is better than an open-ended wait. And we do not keep ringing after someone has answered: an alert that outlives its reason teaches people to silence it.
Design the alert for the afternoon nobody is watching. The other afternoons take care of themselves.
The shape works for any alert that matters
Replace “customer waiting” with “approval blocking a delivery” or “stock-out at a branch” and the same four questions apply: who is reachable right now, who is reachable at all, where is the shared fallback, and what does the person waiting get told. For how alerts in your own workspace reach people, see mute the email, keep the alert and which alerts deserve a phone buzz.
Draw the ladder for your most important alert
Who gets it first, and how do you know they are there?
Answer
A named rota, not a mailing list.
Watch for
An alert sent to someone on leave.
After how long does it widen, and to whom?
Answer
A time, and a second group.
Watch for
A ladder with one rung.
What is the shared fallback?
Answer
An inbox or queue someone owns.
Watch for
A fallback nobody reads.
What does the person waiting see?
Answer
A clock, then a promise.
Watch for
A spinner with no end.
Verdict
An alert is only as good as its worst afternoon. Know who is actually reachable, widen the net on a timer, keep a shared fallback that someone owns, tell the person waiting the truth, and stop the moment someone answers.
See how support reaches you
Live chat with AWRA support, with an honest clock and an email fallback.
How support chat worksFrequently asked questions
What happens if nobody answers a live chat with AWRA support?
Representatives on shift are alerted at once. After 45 seconds every support owner is alerted, after two minutes the support inbox is emailed, and after three minutes the customer is told the conversation will be answered by email.
How do representatives get alerted?
By a push to the AWRA app on their phone, a browser notification that stays until clicked, and an alert card in the app that rings until someone acts.
What stops the alerts?
The first reply or a press of Accept. Every later step is cancelled and the alerts on other screens clear.
How is an escalation ladder useful outside live chat?
The same four questions apply to any alert that matters: who is reachable now, who is reachable at all, what the shared fallback is, and what the person waiting is told.
