WhatsApp is read on a phone, in the same list as messages from the reader's family. That one fact drives nearly every rule below: be brief, be prompt, be recognisably human, and never message someone who did not ask you to. Get those four right and the rest is detail.
Here is the short version, then the reasoning behind each line.
Do and don't, at a glance
| Do | Don't |
|---|---|
| Publish a response time you can hit on a bad day | Advertise a time you only hit on good days |
| Reply with the whole answer in one message | Send five fragments in a row, each buzzing their phone |
| Ask permission before the first message you send | Add numbers from an order form to a broadcast list |
| Start from a template, then change at least one line | Send the template exactly as stored |
| Use the customer's name once, early | Use it in every message, which reads as a script |
| Name the person taking over | "This has been escalated to the relevant team" |
| Send a link with a sentence of context around it | Reply with a bare URL |
| Say plainly when you cannot help, and who can | Keep a thread alive so it looks like progress |
| Keep the thread as the record | Move the customer to email and lose the history |
| Close with a check that it is actually sorted | Close because the ticket needed closing |
Response time: publish the number you can keep
Nobody expects a small business to answer at 11pm. What people do expect is that the stated promise is real. A profile claiming "replies within minutes" that answers in six hours does more damage than one claiming "within one working day" that answers in four.
Three things worth separating:
- •First acknowledgement. Can be automatic, should be within seconds, must say when a person appears.
- •First human reply. The number you publish. Choose it from your worst week, not your best.
- •Resolution. Often longer, and fine as long as you keep updating. A thread that goes quiet for two days is read as abandonment even when someone is working on it.
The habit that fixes most complaints about slowness is the interim update: a line saying you are still on it, what you are waiting for, and when you will next report back, sent *before* the customer has to ask. Chasing is what annoys people, more than waiting does.
Tone: write like a person who works there
WhatsApp tone sits between email and a text to a colleague. Contractions are fine. One-line replies are fine. Full formality reads as a form letter in this context, and so does corporate hedging.
Four moves that reliably land well:
- Answer first, explain second. "Yes, Thursday at 4 works" before the paragraph about availability.
- Say "I" when you are doing it. "I'll check and come back by lunchtime" commits; "this will be looked into" does not.
- Drop the throat-clearing. "Thank you for reaching out to us regarding your enquiry" says nothing. Start with the answer.
- Match their register, within reason. If they sent two words, do not send six paragraphs. If they are formal, be a notch more formal.
Where to stay careful: emoji are acceptable in a greeting or a thank-you and wrong in a complaint. Voice notes are efficient for you and often inconvenient for the customer, who may be somewhere they cannot listen; ask before sending one. And never use humour on a thread where somebody is upset.
Consent: the rule that protects the channel
This is the one that gets businesses into actual trouble, as opposed to merely making them look clumsy.
Someone giving you a phone number to complete an order has not agreed to be messaged on WhatsApp about anything else. Consent for support is not consent for marketing, and a bulk send to a list built from order forms is the fastest way to collect spam reports, which is also how businesses lose the ability to message anyone.
The workable standard:
- •They message you first, or they tick a box that specifically says WhatsApp. Either is fine. An unchecked assumption is not.
- •Keep a record of where consent came from. Which form, which date. You will want it.
- •Make opting out one word, and honour it immediately. "STOP" should work, and should not be followed by a message asking them to reconsider.
- •Keep support and marketing separate. Agreeing to delivery updates is not agreeing to a sale announcement.
Two more points people forget. Chat threads contain personal information, so be deliberate about who on the team can read them, and use a business number rather than a personal one so a staff departure does not take the history with it. And if a customer asks you to delete their messages or their number, do it and say you have.
Message length: one screen, one message
The practical ceiling is what fits on a phone screen without scrolling, which is roughly four short lines. Beyond that, put the detail behind a link and keep the message as the summary.
- •One answer, one message. Compose the whole reply, then send. Sending it in pieces notifies them repeatedly and makes a simple answer feel like an interrogation.
- •Use line breaks, not paragraphs. Three short lines read faster than one dense block.
- •Numbered steps, maximum four. If it needs eight, it needs a page, and the message should link to it.
- •Never paste a policy. Summarise the bit that applies to them, then link the full text.
Templates versus writing it fresh
Templates are good for speed and consistency and bad at sounding like anyone. The resolution is not to abandon them but to treat them as a first draft.
The rule that works: every template gets one line of this specific customer in it before it goes out. Their order, their date, their problem, named. That single edit is the difference between a reply that reads as handled and one that reads as processed.
Where templates belong: hours, prices, policies, what is included, how to return something, the first acknowledgement of a complaint. All of these have one correct answer and you should not be rewriting it.
Where they do not: anything about *this* order going wrong, anything where the customer has been let down twice, anything where the honest answer is no. Those need a person composing from scratch, because a template arriving at a bad moment is read as indifference. Copy-ready auto reply wording is worth having, as long as somebody is checking which situation it is landing in.
Staying on the right side of spam
A business can behave reasonably and still get flagged, usually through one of these:
- •Unsolicited first contact. The biggest one. If they did not message you first and did not opt in, do not send.
- •Volume without content. Three "just checking in" messages on a dead thread. Silence is better.
- •Promotion inside a support thread. Someone asking where their parcel is does not want a discount code.
- •Obvious broadcast mechanics. No name, no reference to anything they said, a tracking link, an unsubscribe footer. People recognise all of it.
- •Messaging at antisocial hours. A 6am delivery notification is technically useful and still resented. Hold non-urgent sends to daytime in the customer's own time zone.
Treat the block rate as the metric that matters most here, because unlike a bad review it affects every future message you send.
Handing off to a person, properly
Whether the handoff is from automation to a human or from one colleague to another, the same three things make it work.
- Say it is happening, and name who. "Passing this to Priya, who handles returns."
- Carry the context across. The customer should never have to repeat themselves. Having to explain it twice is the most common complaint about any support system, automated or not.
- Give a time. A handoff without one feels like being put down rather than passed on.
And know the points where a person should take over regardless: the customer asks for one, it is the third message on the same issue, there is money or safety involved, the tone has turned, or the automation has failed to answer once already. What automation can and cannot sensibly handle is worth reading before you set those thresholds, and the same logic applies to a chatbot on your website.
Pointing people at self-service without being dismissive
Sending a link is good practice done well and insulting done badly. The difference is entirely in the sentence around it.
- •Bad: a bare URL.
- •Better: "Returns window is 30 days, details here: [link]"
- •Best: "Returns window is 30 days and postage is on us, so you are fine. Full process here if you want it: [link]. If your situation is different, tell me and I'll sort it."
The structure is: answer the question, offer the link for depth, leave a door open. Done that way, most people never need the link, and the ones who do get more than you would have typed. It also quietly reduces the volume arriving in the first place, which is the same mechanism behind cutting repetitive support tickets in any channel. Answrii exists to make that link worth sending: one structured, searchable set of answers rather than a page nobody can navigate on a phone.
Three habits that matter more than any single rule
- •Read your last ten replies as a customer. Not as the person who wrote them. The pattern you notice is usually the thing to fix.
- •Keep the thread. Do not move people to email unless the matter genuinely needs attachments and a record. The history in one place is WhatsApp's main advantage over a ticket queue.
- •Close properly. "Is that sorted, or is there anything still open?" costs one message and catches the cases where you answered a slightly different question.
Frequently asked questions
How fast should a business reply on WhatsApp?
As fast as your published promise, and the promise should be one you can keep in a bad week. An automatic acknowledgement within seconds plus a real reply inside the stated window beats a fast reply on Tuesday and silence on Friday.
Is it acceptable to use templates for WhatsApp support?
Yes, for anything with one correct answer. Edit in at least one detail specific to the customer before sending, and write complaints and bad news from scratch.
Can I message customers on WhatsApp after they buy from me?
For things directly about their purchase, where they gave you the number for that purpose, generally yes. For anything promotional you need consent that specifically mentions WhatsApp, a working opt-out, and a record of where the consent came from.
Should support staff use their personal WhatsApp?
No. Use a business number. Personal numbers mix work into private threads, leave no record when someone leaves, and give one person sole custody of the customer history.
How do I stop WhatsApp support eating the whole day?
Answer the repeat questions once, in a structured place, and link to it. Set an away message with real hours. Keep replies to one screen. The time goes on long typed answers to questions you have already answered elsewhere.
Is WhatsApp ever the wrong channel for support?
When the matter needs documents and version history, when it involves regulated advice, when it will run over weeks, or when you cannot staff it at the hours customers expect. In those cases say so early and move it, rather than letting the thread decay.
Generate your FAQ page
Paste your product description and get a complete FAQ page - free, no sign-up.
Try Answrii free →