How to Design a Better Handover from Phone or WhatsApp to a Person

When an automated phone or WhatsApp flow needs a person, pass on a short, structured summary of what the enquirer wants, what has already been asked and what should happen next. Make it clear whether the person is available now, and give the enquirer a way to correct or add to the summary.

A handover is not just a technical connection between channels. It is a small piece of service design: the customer needs to know what will happen, and your team needs enough context to pick up the conversation.

Decide when automation should stop

Set clear points where a person should take over. For example:

• The enquirer asks to speak to someone.
• The request needs judgement, negotiation or a site-specific answer.
• The system is uncertain about an important detail, such as which property or job the enquiry concerns.
• The person has already tried to resolve the issue through the automated flow.
• The enquiry falls outside the information the system is meant to handle.

These are design choices, not features you should assume a particular tool provides. Write them down before building anything, so the system has a clear boundary rather than attempting to handle every conversation.

Pass context, not just a notification

A useful handover note can be brief. Consider including:

• The person’s name and their preferred way to be contacted, if provided.
• The phone number or WhatsApp conversation identifier needed to find the exchange.
• What they are asking about, in their own words where helpful.
• Any answers already collected, such as a location, preferred appointment time or type of work.
• What is still unknown, and what the person has asked your team to do next.

Avoid presenting a guess as a confirmed fact. If the system is unsure whether two messages refer to the same person or job, mark that uncertainty for the team to check instead of merging the records automatically.

Keep the channel change understandable

If someone starts by phone and the next step is a WhatsApp message, explain the change and ask whether that works for them. If they would rather stay on the phone or be called back, record that preference instead. Do not assume a mobile number means the person wants to move the conversation to WhatsApp.

The same principle applies in the other direction. If a WhatsApp conversation needs a call, tell the person who will call and what they will discuss. Where nobody is available, state that the request has been passed on and give a realistic next step. Do not imply that a live transfer or immediate reply is available unless your setup can actually provide it.

The technical building blocks vary. Twilio’s documentation describes its WhatsApp APIs for one-way messages and two-way conversations, while its voice documentation describes inbound-call flows that can gather caller input. Those are implementation options, not evidence that a phone-to-WhatsApp handover is automatically connected: the application still needs to pass the right context between channels. See the Twilio WhatsApp documentation and Programmable Voice documentation for the capabilities and setup described there.

A simple handover checklist

Before putting a flow into use, check that:

• The customer knows when a person will take over and through which channel.
• Your team can find the original conversation or call.
• The handover summary separates confirmed details from uncertainty.
• A person can correct the summary and record the next action.
• There is a fallback for out-of-hours enquiries or failed transfers.
• You have tested unclear answers, repeated contacts and requests to speak to someone.

Hypothetical example

A property enquiry arrives by phone. The automated flow records that the caller wants to view a particular flat and prefers a call back. The caller then adds a detail through WhatsApp. A useful handover would link the messages only if the system can confidently associate them, show the viewing request and call-back preference, and flag anything it could not confirm. The team can then check the original messages before responding. This is an illustration, not a description of a delivered project.

Does a handover need to include a full transcript?

Not always. A concise summary plus a way to open the original exchange may be easier to scan. Keep enough detail for a person to verify what was said, especially when a summary is uncertain.

What should happen if no one can take over immediately?

Tell the enquirer what will happen next, record the request in a place the team checks, and avoid promising a response time you cannot support. If you are planning a phone-based intake flow, see the Voice AI Receptionist project.