One agent. On the phone and on WhatsApp

One brain, two channels

What makes this useful is not that there is a bot on WhatsApp — it is that there are not two brains to maintain. Answers come from the same approved knowledge base, catalogue lookups from the same data table, and escalation rules are identical, so a customer never gets one answer on the phone and a contradicting one in a message. When a procedure changes, you change it once. The converse holds too: an accidental edit in one channel cannot create a gap between channels, because no channel has content of its own.

• One knowledge base, with the same human approval before use
• The same data tables — catalogue, branches, stock — available on both channels
• The same tools for calling your systems mid-conversation
• The same guardrails and the same automatic escalation

One continuous thread with the customer

Identification is by the phone number, and specifically by its digits — so the international format used on a call and the WhatsApp identifier resolve to the same person. In practice, the agent opens the thread with the context of the previous conversation and does not ask for a name, an order number or details already given. For your team, that removes the frustrating moment when a customer writes "I already explained this on the phone". Conversations that have been anonymised drop out of this memory, so a deletion request really deletes.

What text does better, and what voice does better

Text wins when you need to send a link, spell out a list, give an exact address, or leave something the customer will come back to — and when the customer cannot talk right now. Voice wins when the matter is urgent, when hands are busy, when the customer is older or simply prefers to speak, and when the request needs a back-and-forth that would take ten messages. Our practical recommendation: do not pick a channel — let the customer pick, and let the agent move between channels without losing context. An agent that can say "I've sent it to you on WhatsApp" at the end of a call saves a second call.

Privacy, control and human handoff

A WhatsApp conversation is treated like any other in the system: identifying details are detected and masked in the transcript, the anonymisation flow applies to it, every administrative action is written to the audit log, and access to content is role-controlled. When a customer asks for a person, or when guardrails block answers repeatedly, the conversation escalates to a human — with the summary and context attached, not as a message thread they must read from the top. On a self-hosted install, all of this sits on your infrastructure.

What you need to bring, and what the agent will not do on WhatsApp

You need an active WhatsApp Business account; continuity works best when it is the same number your customers already know. Responsibility for opt-in and for platform policy compliance sits with the business — the agent honours and records a stop request, but it does not replace a policy. Finally, two caveats: this is a text channel, which makes it the wrong place for a negotiation or for a sensitive conversation that needs a human tone; and scenarios requiring strong identity verification should move to whatever route you defined for that, rather than being resolved in a message.