omnichannel

Phone, WhatsApp, chat — one agent, one memory

Kupe Team · July 11, 2026

Customers do not think in channels. They called, then they texted, then they opened WhatsApp because the hold music was rude. Your stack, unfortunately, often thinks in channels. Four bots. Four memories. Four ways to ask for the same folio number.

That split is not a technical accident. It is how vendors sell. Voice is one SKU. WhatsApp is another. Chat is a third. Each comes with its own prompt, its own CRM sync, its own “context window” that resets when the customer switches apps. The customer did not switch companies. You did.

Kupe treats voice, WhatsApp, chat, and SMS as surfaces on one agent. The conversation is the unit, not the socket. If the night-line already pulled the medical record number, the morning WhatsApp should not start from zero. If a borrower promised to pay on the call, the reminder text should already know the amount.

This is not a unified inbox skin. Unified inboxes still dump work on humans. An omnichannel agent actually does the work: books the slot, logs the promise-to-pay, sends the SKU-aware nudge, then shuts up. The human only joins when the account is genuinely messy.

Teams coming from IVR vendors try to bolt WhatsApp on as an add-on. That is how you get two personalities and a compliance headache. One bot is formal on the phone. The other is chatty in chat. The customer notices. Regulators notice. Your brand does not survive the screenshot.

Keep one prompt, one tool set, one set of voices. Change the wire, not the brain. Phone is a wire. WhatsApp is a wire. The agent is the same person, with the same memory, with the same permission to look things up.

The test is simple. Call, hang up, text. If the agent remembers, you have a product. If it asks you to start over, you have four products wearing a trench coat. Do this on a real number, not in a sandbox. Sandboxes remember because you told them to. Production forgets because nobody wired the memory.

Memory is not a vector database you query after the fact. Memory is “this is Priya, she already confirmed the EMI, she asked to be called after 7pm.” If your architecture cannot say that sentence, you do not have memory. You have search.

We see teams celebrate “omnichannel” because they bought a WhatsApp BSP and a voice vendor and a chatbot. Procurement is happy. Operations is not. Operations still copies account numbers between tabs. That is the tell.

Build the agent once. Put it on every surface the customer already uses. Pay for the minutes they talk, not for a new seat every time a new channel appears. Channels are not products. They are doors.

If you are starting this week, pick the two doors that actually matter — usually phone and WhatsApp — and make them share a brain before you add a third. A shallow third channel is worse than none.

Phone, WhatsApp, chat — one agent, one memory · Kupe