Why customers like it

Support by email is slow and formal. Support by phone means waiting.

Messaging is neither. The customer sends a question, gets on with their day, and comes back to the reply.

And it is asynchronous for you too. One agent can hold several conversations at once, which a phone call does not allow.

The service window works in your favour here. The customer starts the conversation, so a window is open and you can reply freely for a period — usually 24 hours. No templates needed.

What has to be in place first

Three things. Without them, WhatsApp support becomes a worse version of a shared inbox.

Conversations must reach a system

Not a phone somebody carries. If support lives in an app on one person’s device, it disappears when they are on leave and there is no record of what was said.

Conversations should create or update records in your helpdesk or ERP.

Agents must see who they are talking to

Their orders, their invoices, their deliveries, their previous conversations.

Without this, agents ask customers to repeat information the company already has — which is the single most irritating thing in support.

Somebody must be responsible

WhatsApp creates an expectation of speed. A message sitting for two days is worse than an email sitting for two days, because the channel implies immediacy.

Decide who watches it and during what hours, and say so to customers.

Setting expectations

The most useful thing you can do, and it costs nothing.

State your hours. In your business profile, and in the first automated reply.

Give a realistic response time. “We reply within two hours during business hours” is better than saying nothing and replying in three.

Acknowledge out of hours. A short automated message saying when somebody will reply.

Customers accept limits. They do not accept silence.

Where automation belongs

Four things, in order of how safely you can adopt them.

Context for the agent. Assemble the customer’s history so the agent sees it immediately. No customer-facing risk at all, and it makes every reply better.

Suggested replies. Drafted from the question and the customer’s record. The agent edits and sends.

Routing. Reading the message and sending it to the right team with a summary attached.

A narrow bot for a defined set of factual questions, with a one-message escape to a person.

Start with the first. It improves your team without the customer noticing anything.

Where automation does not belong

Anything unread going to a customer. A confident wrong answer sent automatically is worse than a slow correct one.

A bot that will not hand over. On WhatsApp this is more damaging than on a website, because the channel feels personal.

Pretending a bot is a person. People work it out.

Anything involving money. Refunds, credits, disputes. A person decides.

Managing the volume

WhatsApp usually increases contact volume. People message who would not have phoned or emailed.

That is not necessarily bad — it can mean problems surfacing earlier. But plan for it.

Three things that help:

Templates for common replies. Saved responses agents can send and adapt.

A knowledge base. Every question answered publicly is one that arrives less often.

Clear hours. Volume outside working hours is manageable if expectations are set.

The handover problem

Conversations span time. A customer messages Monday, replies Wednesday, and a different agent picks it up.

Three things this needs:

The full history visible. Not just this conversation — their orders and previous tickets too.

Notes from the previous agent. What was agreed, what is pending.

A clear status. Waiting on customer, waiting on us, resolved.

“Waiting on customer” matters more than it sounds. Without it, conversations blocked on a customer reply look like conversations your team is ignoring — and your response time reports become meaningless.

Measuring it

First response time. What customers feel most.

Resolution time. Whether conversations actually close.

Reopened conversations. The honest test. If this rises, you are answering faster and worse.

Volume by topic. What people actually contact you about. The most actionable number here, and the least used.

Blocks and reports. Threatens the channel itself.

Watch reopened conversations closely. Fast wrong answers look excellent on a response time report and cost you customers.

What goes wrong

Support on somebody’s phone. No record, no handover, no continuity.

Agents without customer context. Asking people to repeat what you already know.

No status for waiting-on-customer. Response metrics become meaningless.

Unclear hours. Customers expecting replies at midnight.

Volume without capacity. Opening the channel and not staffing it.

A bot deployed too early. Before anybody knew what customers actually ask.

A sensible rollout

Weeks 1–4. Manual only. Conversations reaching your helpdesk, agents with full context. Record what people ask.

Week 5. Add agent-side automation — summaries and suggested replies.

Week 6. Add routing.

Week 8. Review reopened conversations and volume by topic.

Week 10. Consider a narrow bot for the five most common questions.

The first four weeks are not wasted time. They tell you what to automate, which is not what you would have guessed.

The short version

WhatsApp support works because customers prefer messaging, and because the service window means no templates are needed once they contact you.

Conversations must reach a system, agents must see the customer, and somebody must own the queue. Without those three it is a shared inbox with a nicer app.

State your hours. Customers accept limits and not silence.

Start with agent-side automation, and watch reopened conversations rather than response time alone.