Chat is excellent, until it isn't
Most conversations belong in chat — it is fast, low-pressure, and keeps a record. But some outgrow the text box, and forcing them to stay there serves nobody. Knowing when to offer a call is a skill: escalate too readily and you lose chat's efficiency; cling to text through a conversation that needs a voice and you frustrate the customer. The goal is the fastest path to resolved.
The signs a call will serve better
A few patterns reliably signal that voice beats text: a problem so tangled it has produced twenty back-and-forth messages, an emotionally charged situation where tone matters more than words, or something genuinely faster to talk through than to type. When you notice a chat spiraling in message count or heat, that is the moment to consider the phone.
Make the switch feel like help, not a brush-off
“Please call our support line” can read as “go away.” The difference is ownership: offer the call as an upgrade, carry the context so the customer never re-explains, and ideally hand off to a specific person rather than a general queue. “This will be quicker on a quick call — can I ring you now? I have your details in front of me” feels like care, not dismissal.
Don't escalate out of habit
The opposite failure is real too: pushing every slightly hard question to the phone because it is easier for the agent. That discards chat's speed and record, and annoys customers who chose chat precisely to avoid a call. Reserve the phone for the conversations that genuinely need it, and keep resolving the rest where the customer chose to be.
How MyLiveChat fits
MyLiveChat keeps the full transcript so the context travels when a conversation moves to a call, and it offers richer options — voice, video, and cobrowsing — for the moments a text box can't cover. The judgment of when to escalate stays with your agents; the tool makes the handoff seamless when they do.
Get the timing right
Escalating too early wastes a call that a sentence would have settled; escalating too late
means the customer has already repeated themselves four times and is now annoyed as well as
unresolved. The reliable rule is to watch for the second failed explanation. If you have tried
twice to explain something and it has not landed, the medium is the problem, not the wording,
and a third attempt will not go better.
The other clear trigger is emotional. When a customer is genuinely upset, text strips out the
tone that would have calmed them. A voice carrying real concern does work that no amount of
careful typing can replicate, and moving quickly at that point is a kindness rather than a
retreat.
Offer it as an upgrade, not an exit
The phrasing determines whether a call feels like help or like being passed along. Make it an
offer with a reason attached, and keep ownership of the outcome.
- This will take me two minutes to walk through on the phone and about fifteen to type — want me to call you? Gives the reason and offers rather than instructs.
- I have got your account open in front of me. Shall I ring you now so we can finish it together? Signals that nothing is being restarted.
- Happy to keep going here if you prefer — just offering the quicker route. Leaves the choice genuinely open.
Retire you will need to call support. It hands the customer a task and takes your
name off the problem. If a call is right, arrange it; do not assign it.
Never make them start again
The failure that undoes the whole exercise is the customer repeating their story to whoever
answers the phone. Everything gained by moving channel is lost in the first thirty seconds.
- Summarise the chat into the record before the call — the issue, what has been tried, the account reference.
- Pass the transcript, or a short written handover, to whoever will take the call.
- Tell the customer what the person on the phone will already know, so they are not braced to explain it all again.
- Give them a reference and a name, so a dropped call is recoverable rather than a fresh start.
Respect the reason they chose chat
Plenty of people use chat specifically because they do not want to speak on the phone. That
may be a noisy office, a shared space, a language they read more comfortably than they speak,
a hearing difficulty, or simple preference. None of it is your business to interrogate.
So take a declined call at face value and continue in chat without a second attempt at
persuasion. If the issue genuinely cannot be resolved in text, say what you can do instead
— email with steps, a callback at a time they choose, a screen-sharing session —
rather than repeating that a call would be easier. For some customers it would not be.
What to measure
Track the escalation rate and, more usefully, its reasons. A rise in escalations for one
issue type usually points at a documentation or tooling gap rather than an agent skill gap,
and it is fixable at the source.
Compare resolution time from the customer’s point of view: chat start to actual
resolution, including the call. Watch acceptance rate on offered calls, since a low rate means
the offer is being made at the wrong moment or worded as a brush-off. And check how many
escalated calls end without resolution — those are the cases where the phone was not the
answer either, and something structural is missing.