Transfer service on WhatsApp: how to do it without losing history

How to transfer a WhatsApp service to another colleague without the customer repeating everything? Direct answer: WhatsApp doesn't have a "transfer conversation" button — what solves this in practice is for the entire team to see, live, the same conversation and the same history, on the same number. Without this, "transfer" becomes forwarding a separate message, taking a screenshot or asking the customer to tell everything again.

Why transferring service on WhatsApp is so difficult

Support tools like Zendesk or Freshdesk were born for this: each conversation is a "ticket" that can be reassigned to another agent with one click, uploading the entire history along with it. WhatsApp wasn't designed like that. The application — personal or Business — presupposes one person per number, a conversation flow that lives within that app, with no concept of "queue" or "conversation owner" that can be changed.

In practice, this means that the conversation is stuck on the device (or logged in WhatsApp Web) of the person who started answering. If someone else needs to take over, they will only see what is on the screen if they are looking at the same cell phone, or if someone copies and pastes what was said. There's no such thing as truly "passing the buck" — there's reconstructing the context at hand, every time.

Improvised exits — and what they cost

In the absence of a native way to transfer, most teams resort to three workarounds. They all work "more or less", and they all charge a price:

Improvised exit	What breaks
Forward latest messages	Only takes what was forwarded manually — the rest of the history is left behind, and the customer sees the "forwarded" mark, which sounds impersonal
Screenshot of the conversation	It takes time to take and send, it goes out of date in the next second and gets lost in the team's internal group in a few minutes
Pass the physical cell phone from hand to hand	Only one person answers at a time, the device becomes a bottleneck, and the risk of it being lost or someone accidentally tampering with it is real
Ask the customer to repeat	It is the quickest to execute and the worst for those on the other side — the client feels like they are starting from scratch

There is one point that goes unnoticed in these outlets: prints and conversation forwards usually carry the customer's name, telephone number and order details, and circulate freely in internal groups, sometimes on the personal WhatsApp of those on duty. This is exactly the type of data handling without access control that the LGPD asks a company to avoid, even in a small business.^[1] — the problem is not just one of customer experience, it is one of governance.

When it really makes sense to transfer

It's worth separating two things before proceeding: not every transfer is a symptom of a mess. There are times when passing on the service is exactly the right decision:

• The question was beyond the scope of who answered first. Seller receives a technical question that only the support team resolves, or the opposite — support receives a commercial negotiation.
• Shift change or end of working day. Whoever started the conversation at 5:50 pm cannot be available until it ends; Someone from the next shift needs to continue without reopening the issue from scratch.
• Absence — vacation, day off, leave. The client portfolio of those who leave needs a temporary person responsible, with the history attached.
• Complaint escalation. A more delicate case requires input from a manager, and the customer should not need to justify again why they are dissatisfied.

The realistic goal isn't to "never transfer again" — it's to do so without friction, when it's actually necessary.

Which solves the problem in the bud: shared number with unique history

The structural solution is not to find a faster way to forward a message — it is to eliminate the forwarding step. This happens when the entire team already sees the same conversation, live, because they are connected to the same WhatsApp number. There's no copy, there's no print, there's no "let me tell you what he said": the colleague opens the conversation and the entire history is already there.

This is the principle behind Zapext's Plus plan: up to 4 users on the same WhatsApp number, each on their own screen, all seeing the same conversations and the same CRM Kanban shared. The complete setup guide — how to connect each user, what changes from native WhatsApp, and the actual limits of the feature — is at multiservice on WhatsApp. It is worth noting what WhatsApp itself already allows natively: connecting up to 4 devices to the same number using the multi-device function^[2] — what the native feature lacks is the organization on top (who owns each conversation, what stage it is in, what has already been agreed), which is the role of the extension's CRM Kanban.

What the baton passing looks like in practice

With the conversation now visible to the entire team, "transferring" stops being about moving a file and becomes just about reassigning responsibility within the same space. The flow looks like this:

1. Change the label or move the card for the column that represents who takes over now — from "Sales" to "Technical Support", for example, or for a "Waiting for Specialist" column.
2. Leave a short note on the card with what remains to be resolved: "customer wants to change the plan, has already confirmed the CPF, all that remains is to pay". Two sentences are enough — the goal is to save the person arriving, not to write a report.
3. Colleague opens the same conversation — without changing devices, without asking for a print from anyone — and you can already see the most recent message, the complete history and the context annotation.

Note that this is not a magic "transfer service" button: it is the natural consequence of everyone already looking at the same place. Honesty matters here — Zapext does not move the conversation to another number nor does it have automatic routing using artificial intelligence; the chatbot by keywords of the extension performs simple screening via text trigger, useful for directing a recurring question, but whoever decides who a specific case goes to remains human.

Good handoff practices even without relying solely on the tool

Part of the solution is not technological — it's a team habit, and it applies even to those who still don't use any paid tools:

• Never leave an open conversation without leaving a trace. A native WhatsApp Business label ("awaiting return") or a line in a shared spreadsheet already prevents the customer from waiting without anyone knowing that they are in the queue — the complete method of organizing this queue by status is in WhatsApp service queue.
• Warn the customer, don't disappear. A simple phrase — "I'll connect you with [name], who takes care of this" — avoids the feeling of silence and sets the stage for whoever takes over.
• Summarize instead of copying the entire conversation. Whoever receives the handoff does not need to reread everything; you need to know what the customer wants and what has already been promised.
• Agree on a waiting time limit. If the transfer is not accepted within a few minutes, someone on the team needs to notice and charge — prolonged silence is what turns a common handoff into a lost customer.

What this doesn't solve

Three limits are worth the usual honesty. First: the multiple user feature works within the same number — if each branch or department has a separate WhatsApp, the conversation does not go from one number to the other alone, and in this case manual forwarding is still the way to go. Second: there is no automatic reading of intent — the keyword chatbot reacts to triggers defined by you, it does not freely interpret what the customer wants, so subject routing continues to depend on someone to decide. Third: labels and notes only work if the team has the discipline to fill them in — the tool organizes the process, it does not replace the habit.

For those who work alone or in pairs, with few transfers per week, native etiquette and a verbal agreement will do the trick. The gain of having several people seeing the same conversation in real time appears when the volume grows and waiting for someone to copy and paste context starts to cost real sales time. If this is your moment, Zapext's Plus plan — R$59/month, up to 4 users on the same number, 7 days guarantee — was designed exactly for this; the step-by-step configuration is in the guide multiservice on WhatsApp.

Sources

1. [1] Guia Orientativo — LGPD para pequenas empresas — ANPD (Autoridade Nacional de Proteção de Dados) (2022). accessed 2026-05-19.
2. [2] About multi-device beta — WhatsApp Help Center — WhatsApp (2024). accessed 2026-05-19.