In this market WhatsApp is not a channel, it is the channel. Which is why the gap between an enquiry arriving at 9 p.m. and being answered at 10 a.m. costs real money, and why automating the first response is usually the highest-return thing a small business can do to its sales process.
First, work out which WhatsApp you are on
- The WhatsApp Business app
- Runs on a handset. Quick replies, labels, an away message. No programmatic access, so nothing can read or answer for you. Fine for one person answering; it does not automate.
- The WhatsApp Business Platform
- Messages are delivered to your server and sent from it, which is what makes automation possible. It is also the version with rules — verification, approved templates, messaging windows — and those rules shape your design more than the software does.
What you need before you start
- A number you control that can receive a verification code, and that is not currently active in the Business app.
- A display name that matches how your business is actually known. It goes through review.
- Business verification documents, which take time to be processed. Start this first, not last.
- One person who owns the account. Not a departing intern, and not a personal account belonging to someone who may leave.
The 24-hour window shapes everything else
When a customer messages you, a service window opens and you can reply freely inside it. Once it closes, you can only reach that customer with a message template that has been submitted and approved in advance. Every design decision downstream follows from this.
- A same-session reply is free-form. That is your automated first response, and it is the easy case.
- A follow-up the next day is a template. So is a reminder, an order update and a workshop confirmation.
- Templates take time to approve and are sometimes rejected. Write them in week one, not the day before launch.
- Anything proactive needs the customer to have opted in, and you need to be able to show when and how.
What the first response should actually say
- 01Acknowledge in seconds, in a sentenceThe reply that matters most is the one that says a real business is on the other end. Say who you are and that you are handling it.
- 02Answer the three questions everyone asksWhat does it cost, do you have it, and where or when can I get it. Answer these before you ask anything, because an enquiry that gets a question instead of an answer is an enquiry that stops.
- 03Ask one qualifying questionOne. The one whose answer changes what you would say next. Not a form delivered a line at a time.
- 04Hand over with the conversation summarisedWhen a person takes it, they should arrive knowing what has been asked and answered. Making your salesperson scroll is how automation creates work instead of removing it.
Handover is the part that decides whether people trust it
- Make the switch to a person visible. "Tendai is picking this up now" is worth more than any amount of natural-sounding text.
- Know your own business hours and say so. Promising a call back in ten minutes at 22:00 is worse than saying nothing.
- Escalate on the obvious triggers: a complaint, a price negotiation, a request for a human, or two failed attempts to answer the same question.
- Never let the automation argue. If it does not know, it says so and fetches someone — the same rule the rest of our assistant work follows.
Measure the right things, and record the baseline first
| Measure | Why it matters |
|---|---|
| Median first response time | The number that changes most and the one that moves revenue. |
| Share of enquiries handled with no person involved | Tells you whether it is saving work or just adding a layer. |
| Share escalated to a person | Too high and it is not helping. Near zero and it is probably stonewalling people. |
| Enquiries arriving outside working hours | Usually the number that justifies the whole project. |
| Enquiries that became quotes | The only measure that survives a conversation with a finance director. |
Things that will bite you
- One number, one integration. Two systems on the same number will fight over every message.
- Template quality ratings fall if people block or report you. Sending less, and only to people who asked, is how you protect the number.
- Group chats are not part of this. Do not design a flow that assumes them.
- Test on a real handset, on mobile data, before launch. A message that renders correctly on your laptop is not evidence.
- Keep a way to answer manually on day one. Something will need it in the first week.
The work here is mostly not technical. It is deciding what the first message says, which questions it may ask, and when it must stop and fetch a person. Get those three decisions right and the integration itself is a fortnight of work — see Augustus AI for the version we already run for clients.