Messaging and channels

Moving a Web Chat to a Phone Call Without Losing the Customer

When and how to move a web chat conversation to a phone call: the signals to look for, how to ask, what to pass on and how to record the outcome.

Call editorial team · Published · 5 min read

Web chat is quick and convenient, but it has limits. Some questions need a tone of voice, a long explanation or a screen walkthrough. Others are simply too tangled to untangle by typing. In those cases a short phone call can save both sides a long chat. The trick is making the switch feel like service, not like being passed along.

A support agent with a headset switching between a chat window and a phone
Illustrative image

This guide covers when to propose a call, how to ask, what must be handed over and how to keep the whole thing tidy. It complements Omnichannel Support, which looks at how channels work together.

Signs a chat should become a call

Do not move people to the phone by habit. Do it when it is clearly better for them. A few signals help an agent decide.

Good reasons to offer a call

  • Long threadThe conversation has gone back and forth several times without progress.
  • ComplexityThe problem has many parts or needs a live walkthrough.
  • EmotionThe customer sounds upset, worried or confused, and a voice will reassure them.
  • Sensitive detailsThe matter involves information that should not be typed into a chat.
  • Customer requestThe person has asked to speak to someone.

The last one is simple: if the customer asks for a call, arrange it. Do not try to talk them out of it.

How to ask, and how not to

The offer should sound like help. "This might be quicker to sort out by phone. Would you like us to call you?" is respectful. "Please call our helpline" feels like a brush-off. Make clear that the customer is in control, and give them options: call me now, call me later or stay in chat.

Ways to offer a call

HelpfulUnhelpful
Wording"Would a short call help? I can ring you.""Please phone us instead."
EffortAgent calls the customer.Customer must find a number and wait.
TimingA time the customer chooses.Whenever the line is free.
HistoryThe agent already knows the chat.Customer starts again.

If the customer prefers to stay in chat, respect it. Some people dislike calls, cannot talk where they are or simply want a written record.

What to collect before the call

A smooth hand-off depends on a few details, gathered in the chat while you still have the customer's attention.

  1. Consent. Ask clearly whether they would like a call, and note the answer.
  2. Number. Confirm the number to call, with the country code if relevant, and say who will be calling.
  3. Time. Agree a window, in the customer's time zone, and check the opening hours of the team that will call.
  4. Topic. Write down in a line or two what the call is about, so the agent is prepared.
  5. Language. Note the language the customer would like to speak.

Never call a number someone typed in as a contact detail for another purpose without checking. If you are unsure, ask. And if you plan to record the call, tell them. See Call Recording Consent.

The hand-off itself

From chat to call

  1. Agree in chatConfirm consent, number, time and topic, and tell the customer what will happen.
  2. Pass the contextAttach the chat transcript and a short summary to the call task.
  3. Call on timeRing at the agreed time, introduce yourself and refer to the chat.
  4. ResolveWork through the problem, confirming what has been done.
  5. Follow upSend a short message with the summary and add the outcome to the record.

Speaking first, the caller should show they have read the chat: "I have your messages about the delayed delivery in front of me." That one sentence prevents the most common complaint, having to explain everything again. Hold and Transfer Etiquette has more on handing a customer from one person to another.

When nobody can call right now

Chat often runs outside phone hours. If no one is available, take a call-back request: record the number, preferred window and topic, and tell the customer when to expect the call. Make sure the request goes into a list that someone checks first thing, with the oldest at the top. Callbacks and Voicemail explains the principles. Keep a record of how many requests are completed on time, and treat the figure as a sign of whether the promise can be kept.

Set expectations about timing

Customers in chat are online right now and usually want help right now. If a call cannot happen straight away, say how long it will be and give them a choice: wait in the chat, take a call in an hour or choose a time tomorrow. Do not say "someone will call you soon". Soon means different things to different people, and a vague promise turns into a complaint.

Remember time zones and local habits. A customer might be in a country where the working day is different from yours, or may be unable to take calls at work. Ask when they are free and record the time with its zone. If the call cannot be made in your opening hours, say so and offer another channel.

Use the call to improve the chat

Every chat that turns into a call tells you something. Why could the chat not solve it? Perhaps a help article is missing, a question needs a form, or an agent needs a clearer script. Keep a note of the reason with each transfer and review the list monthly. If the same topic appears again and again, fix the cause, and the number of calls you need to make will drop.

Keep one record

The risk in any hand-off is that the history splits in two: a chat transcript in one system and call notes in another. Make sure both end up against the same customer, so whoever helps next sees the whole story. One Customer, One History Across Channels explains how to organise it.

Chat-to-call checklist

  • The customer agreed to a call
  • Number, time, time zone and language confirmed
  • Topic and chat history attached
  • Caller knows the case before dialling
  • Outcome recorded and summary sent
  • Call-backs that cannot be met are rescheduled before the time passes

Chat and call-backs in Call

In Call, the website chat widget is set up by an operator, and customer messages arrive in the Inbox alongside phone inquiries, where a conversation can be assigned and resolved. Callers waiting too long on a queue can be offered a message or chat instead of waiting, and the Offer a message report shows how often the offer was made and taken. For call-backs, the Callbacks list under Inbound ops shows who is waiting, lets an agent take one and record whether the customer was reached, and the Calendar has a Call-backs tab with the promised time and the number of attempts. Online booking lets a visitor pick a slot, and call-backs requested there land in the same list.

Frequently asked questions

Should I always offer a call in a long chat?

Offer it when it helps, such as when progress is slow or the problem is complicated. Do not make it automatic, and respect a customer who prefers to stay in chat.

Do I need permission to call someone from a chat?

Yes, ask clearly and record the answer. Be careful that the number belongs to the person who agreed.

What if the customer does not answer?

Try again once at a reasonable interval, leave a short message that does not reveal private details, and send a note in the chat or by message so they can choose another time.

How do I stop customers repeating themselves?

Attach the chat history and a short summary to the call task, and have the caller read it before dialling.

Can a chatbot or AI take the call-back request?

It can collect the details and pass them on, but a person should confirm the time and make the call.

What if the call runs outside opening hours?

Offer a time within the team's hours in the customer's time zone, and record it as a call-back request.

Offer a call-back from chat in Call

In the demo console you can try incoming calls in a simulation.

Related guides