Warm Handover: Pass the Promise, Not the Chat

Warm Handover: Pass the Promise, Not the Chat

Passing a WhatsApp customer to a colleague loses them when only the chat moves. A warm handover carries the promise, the next step and one owner.

Tan Wei LinTan Wei LinGeneral
9 Nov 26
17m
Part of the series:CRM Automation for Malaysian SMEs: The Complete 2026 Guide to Replacing Manual Processes

A warm handover on WhatsApp passes four things from one staff member to the next: where the customer stands, what was promised, the next step with a date, and one named owner. Most handovers in small businesses pass a screenshot of the chat and a phone number instead, which is why the customer ends up explaining everything again to a stranger who could have scrolled up.

The position this post takes: the chat history is the easy part, and on a shared business number you already have it. The promise is the part that gets lost. "Let me pass you to my colleague" costs you customers when the colleague does not know what you promised, messages from a number the customer has never seen, and opens with "How can I help?".

Key Takeaway

A warm handover keeps the customer in the same WhatsApp chat, introduces the new person by name, and gives that person a four-line note: where things stand, the promise in exact words, the next step with a date, and the new owner. It matters because 66% of customers say they often have to repeat or re-explain information to different representatives (Salesforce, 2022). Hand over as rarely as you can, and when you do, make the new person's first message prove they already know what was promised.

What is a warm handover on WhatsApp?

A warm handover is passing a customer to a colleague with the context sent ahead of them, so the customer never has to start again. The term comes from call centres. A warm transfer means the first agent briefs the second before the caller is put through. A cold transfer means the caller lands with someone who knows nothing.

On WhatsApp the same split shows up in a different shape. The cold version is a phone number: "for installation, please WhatsApp my colleague Ah Seng at this number." The customer now has to save a stranger's number, open a new chat and explain the job from the beginning. Or the colleague messages first, from a personal phone, with "Hi boss, can send me your address?" In a country where people are told again and again to ignore strangers on WhatsApp asking for addresses and payments, that message looks exactly like the ones they are told to ignore.

What happensCold handoverWarm handover
Where the customer talksA new number they have never savedThe same business number, in the same chat
Who introduces the new personNobody, or the customer is told to message themThe outgoing person, in the chat, by name and role
What the new person knowsWhatever the screenshot showedA four-line note: status, promise, next step, owner
Their first message"Hi, how can I help?"Restates the promise and offers the next step
Who owns the customer afterUnclear, usually "the after-sales team"One named person, recorded on the lead

Keeping the whole team on one business number is what makes a warm handover possible at all. We covered the options, from linked devices to the API, in our guide to WhatsApp multiple users on one number.

Why does "let me pass you to my colleague" lose customers?

Because it turns your internal change into the customer's work. Every handover asks the customer to do something: find a new chat, explain again, trust someone new. Research on service loyalty has said the same thing for more than a decade. Customers leave over effort, not over a lack of delight.

A study by the Customer Contact Council, covering more than 75,000 customers, found that 56% reported having to re-explain an issue and 59% reported being transferred. Customers were four times more likely to leave a service interaction disloyal than loyal, and 81% of those who had a hard time getting a problem solved said they intended to speak badly of the company (Harvard Business Review, July/August 2010).

56%
of customers report having to re-explain an issue, and 59% report being transferred

More recent research points the same way. In Salesforce's 2022 research, 66% of customers said they often have to repeat or re-explain information to different representatives, and 60% said it generally feels like they are dealing with separate departments, not one company (Salesforce, State of the Connected Customer, May 2022, cited in its State of Service report, 5th edition).

66%
of customers say they often have to repeat or re-explain information to different representatives

Now picture it in a small business. Take an 11-person renovation contractor in Puchong. Mei Ling, the designer, has spent five weeks with Mr Lim on a 3-room condo: two site visits, four revisions of the quotation, and one phone call where she agreed three things to close the deal. Wet works finished before Chinese New Year. Hacking on weekdays only, because a neighbour complained during the last renovation in the block. And the old window grilles removed, included in the RM42,500.

The deposit lands on a Monday. Mei Ling sends Mr Lim the site supervisor's number and moves on to her next client. Ah Seng messages from his own phone: "Hi boss, Ah Seng here. Send me the address and what you want to do." Mr Lim retypes the job from memory. He leaves out the grilles and the weekdays, because he assumed the company already knew. The crew hacks on a Saturday, the neighbour complains to management, and at handover the grilles are still on the windows.

Nobody lied. The promise simply never crossed from one phone to the other. This is a composite of a pattern, not one customer's story, and it repeats wherever a sale is closed by one person and delivered by another.

Isn't the chat history enough?

No, and this matters most for businesses that have already moved the team onto one shared number. Shared history makes a handover possible. It does not make it happen.

There are three reasons. First, the promises that close a sale are often not in the chat at all. They were made on a call, at a site visit or in the showroom, and the chat only says "ok noted, see you Monday". Second, when a promise is in the chat, it is buried. The grille removal is message 87 of 140, written as "ok can, we settle that also". Nobody taking over a customer reads 140 messages before replying, so they reply with "How can I help?", and the customer hears: start again. Third, a history everyone can read has a next step nobody owns. Five people can see the chat, and nobody's name is on it.

Businesses also tend to overestimate how much context survives a transfer. In a survey of 600 business decision-makers and 3,000 consumers in the US, UK and Germany, nearly all of the decision-makers said their organisation preserves context when a chat moves from AI to a human, yet 83% of consumers said they still have to repeat themselves at least sometimes after being transferred (Five9 with Hanover Research, June 2026). That study is about bot-to-human transfers, which we covered in when a WhatsApp chatbot should hand over. Between two humans the gap is the same: the business believes the context went across, and the customer is the one who finds out it did not.

What should a handover note carry?

Four lines, written by the person who made the promise, before the new person sends a single message.

Where it stands. One line on what the customer wants or bought, the stage it is at, and anything already paid.
What we promised. The exact commitments that closed the sale or calmed the complaint: price, inclusions, dates, free extras. "Before Chinese New Year" gets written as a date.
The next step, with a date. Who does what next, and when the customer was told to expect it.
The owner from today. One named person. "The after-sales team" is not an owner.

Here is what that looks like for the Puchong job. This is our sample, not a note from a customer account.

HANDOVER  Mr Lim, 3-room condo, Puchong
Status:   Deposit RM8,500 paid 2 Nov. Quote RM42,500, revision 4.
Promised: Wet works done by 20 Jan (told him "before CNY").
          Hacking Mon to Fri only, 9am to 5pm (neighbour complained before).
          Old window grilles removed, included in the quote.
Next:     Ah Seng confirms start date with Mr Lim by Tue 10 Nov.
Owner:    Ah Seng from today. Design questions still go to Mei Ling.

The owner line is the one most teams skip, and it is the one that quietly kills customers. Inside the 20-plus-agent agencies we work with, roughly 3 in 10 dead leads had been assigned to someone who never acted on them, and nothing happened to that person for it. A handover to "the team" is the same failure in a different shape: everyone assumes someone else has it.

Each kind of handover loses something different, so the promise line changes with it.

HandoverWhat usually gets lostThe line the note must carry
Sales to after-sales or installationThe inclusions and dates agreed to close the saleExactly what is included, at what price, by when
One branch to anotherThe price, stock or slot quoted at the first branchThe quote or booking, and that the new branch will honour it
Rep to managerWhat was already offered, and why the customer is pushingThe offer on the table and the decision being asked for
Cover for a day off or a shiftThe time the customer was told to expect an answerWhen the answer is due and what it is

Leave is where the day-off row gets tested, and our December leave coverage plan sets out who answers which customers while someone is away.

How do you hand over a WhatsApp customer without them repeating themselves?

Keep the customer where they are, brief the new person first, and make the new person's first message carry the promise. Six steps.

How to Hand Over a WhatsApp Customer to a Colleague

Decide whether it needs a handover at all. If the customer only needs one answer from a specialist or a manager, bring that person into the same chat and keep the owner. Hand over only when someone else will carry the customer from here.
Write the four-line note before anyone messages the customer. Where it stands, what was promised in exact words with prices and dates, the next step with a date, and the new owner by name. Put it on the customer record, not in a group chat where it scrolls away.
Change the owner on the record, not just in conversation. One named person takes over, they know it is theirs, and anyone who opens the lead can see who owns it now.
Introduce the new person in the same chat. The outgoing person names them and their role, says they already know what was agreed, and says when the customer will hear from them. Never hand the customer a new number to message.
Have the new owner open by restating the promise. Their first message shows they know the history and offers the next step as a choice, not "How can I help?".
Check that the promise was kept. Put the next-step date where it will surface, and have the outgoing person look at the chat once, a few days later, before the customer has to chase.

Step 4 and step 5 are two short messages. Here is the pair for the Puchong job, first from Mei Ling and then from Ah Seng, both in the chat Mr Lim has always used. These are our samples, so swap in your own details.

Hi Mr Lim, deposit received, thank you! From today Ah Seng, our site
supervisor, is your main contact for the works. He has your layout and
everything we agreed, including weekday-only hacking and the grille
removal. He will message you here by Tuesday with the start date. I'm
still in this chat for any design questions.
Hi Mr Lim, Ah Seng here, site supervisor for your condo. I have the
revision 4 layout and our target to finish wet works by 20 January.
Hacking will be Monday to Friday only, 9am to 5pm, and the old grilles
come out in week one. Can we start on Monday 16 November, or is
Monday 23 November better for you?

For a customer who writes in Bahasa Malaysia, the second message reads like this.

Hai Encik Lim, saya Ah Seng, penyelia tapak untuk kondo encik. Saya
sudah ada pelan susun atur versi 4 dan sasaran siapkan kerja basah
menjelang 20 Januari. Kerja hacking hanya Isnin hingga Jumaat, 9 pagi
hingga 5 petang, dan gril tingkap lama dibuang pada minggu pertama.
Boleh kita mula Isnin 16 November, atau Isnin 23 November lebih sesuai?

Notice what Ah Seng's message does not do. It does not ask for the address, the budget or the layout. It does not say "how can I help". It repeats the two promises Mr Lim cares about most, before he has to ask, and ends with a choice between two dates.

Frequently Asked Questions

A warm handover is passing a customer to a colleague with the context sent ahead of them, so the customer does not have to start again. The outgoing person briefs the new one, introduces them to the customer by name, and the new person opens by showing they already know what was agreed. A cold handover just gives the customer a new contact and leaves them to explain.
In a cold transfer the customer is passed on with no briefing, so the next person starts from zero. In a warm transfer the first person briefs the next one before the customer reaches them. On WhatsApp, cold usually means giving the customer a new number to message, and warm means the new person replies in the same chat, already knowing the history and the promise.
Four things: where the customer stands, what was promised in exact words (prices, inclusions, dates), the next step with a date, and the one person who owns the customer from today. Keep it to four lines so it gets written every time, and keep it on the customer record rather than in a group chat where it scrolls away.
Avoid it. A message from a number the customer has never saved, asking for an address or a payment, looks like a scam. It also splits the conversation in two, so the history and the promise stay behind on the first phone. Keep the team on one business number, so the new person replies in the chat the customer already trusts.
Say who is taking over and their role, that they already know what was agreed, and when the customer will hear from them. For example: From today Ah Seng, our site supervisor, is your main contact. He has your layout and everything we agreed, and he will message you here by Tuesday with the start date. Then make sure his first message restates the promise.

How does Raion HUB handle a handover?

In Raion HUB, the team replies from one shared WhatsApp business number, so a handover never needs a second number. The colleague taking over replies in the same chat the customer has always used, with the full thread above them. Customer voice notes are transcribed, with the transcript shown under each one, so the new owner can read what the customer said instead of playing twelve recordings before the first reply. A noisy clip can come out wrong, which is why the recording stays there to replay.

Assigning the lead to the new owner is done from the lead itself, or in bulk from the leads table. Every owner change lands in the lead's activity log with the time and who made it, next to every field and stage change. If a promise is disputed three months later, the log and the thread answer who owned the customer and what was said.

Two honest limits. Raion HUB has no internal notes or @mentions. The handover note lives on the lead itself, in the shared Remarks field or in fields you add for the purpose, such as Promised, Next step and Next step date, and everyone who opens the lead reads the same note. A date field also lets a manager filter the leads table for every next step due this week. And changing the owner does not message the customer. The introduction is still a message a person writes, and it should be.

On plans that include AI Summary, the AI writes a short summary of the chat when it goes quiet. That covers the "where it stands" line well. It cannot know what was promised on a phone call or at a site visit, so the Promised line is still written by the person who made the promise.

When should you not hand over at all?

When the customer only needs one answer from someone else. The best handover is the one you did not need. When South Africa's Nedbank set out to cut customer effort, it introduced an "AskOnce" promise: the rep who picks up the phone owns the customer's issue from start to finish (Harvard Business Review, 2010). A 6-person business cannot promise that for every question, but it can stop handing over customers who only need one answer.

Rep to manager is the clearest case. A customer pushes for a bigger discount, the rep says "let me check with my boss", and the manager messages the customer directly. The customer learns that the rep cannot decide anything, and from then on they ask for the manager every time. Better: the manager decides and the rep delivers the answer as the owner. If the customer needs to hear it from the manager, the manager replies once in the same chat, by name, and the rep stays the owner. The same goes for a technician answering one technical question before the sale.

Keep a real handover for the moments when someone else will carry the customer from here: the sale closes and installation starts, the customer moves to another branch's area, or the job moves to a different team. The hardest version is the one where the person handing over is leaving the company, which we covered in what happens when a salesperson quits.

The bottom line

Key Takeaway

A warm handover is not forwarding the chat. It keeps the customer in the same WhatsApp thread, gives the new person a four-line note with the promise written in exact words, puts one named owner on the record, and has that owner open by repeating what was agreed. Hand over only when someone else will truly carry the customer, because 56% of customers already report having to re-explain an issue and 59% report being transferred (Harvard Business Review, 2010). The chat history was never the hard part. The promise is what has to cross from one person to the next.

Ready to grow with Raion

Hand over the customer, not a screenshot

Raion HUB keeps every WhatsApp chat on one shared business number, lets you assign the lead to whoever takes over, and logs each owner change, so the next person starts from the record.