Notes for owners · CRM, automation and RevOps
Chatbot or a person on WhatsApp: who should answer the first message
A rule for deciding which WhatsApp messages a bot should answer and which need a person at once, with a handover point written down before you switch anything on.
The GullySales team · Updated 17 Oct 2026 · 5 min read
On this page
Let a bot take the first message when the answer is the same for everyone and the customer wants it at an odd hour. Opening times. The address. Which documents to bring. Whether a product is in stock. Put a person on the first message when the customer is about to talk price, has a complaint, or is deciding whether to trust you. The practical answer for many small businesses is both, with one written line saying where the bot stops.
What does the customer want from the first reply?
A WhatsApp message is rarely a question you can answer in the abstract. Read your last thirty chats and sort the first message of each into three piles.
Lookups. "Are you open on Sunday?" "Where is the shop?" "Do you deliver to Hunsur?" The answer is a fact. A bot does this faster than you, and at 11 pm.
Fit questions. "Can you make this in 6 mm?" "My mother has knee pain, which package?" The answer depends on the person. A bot can collect details, but a human should read them.
Trust moments. "Why is your price higher than the other shop's?" "The last one arrived damaged." The customer is not asking for information. They are testing whether anyone is there.
If most of your pile is lookups, a bot pays for itself. If most is trust moments, a bot is a risk, and a better rota is the fix.
The handover rule
Write one sentence before any tool is switched on: "The bot stops and a named person takes over when the customer says X, Y or Z, or after N messages without a result." Then fill it in for your trade.
| Message from the customer | Who answers | Why |
|---|---|---|
| Hours, address, parking, documents to bring | Bot | Same answer every time |
| "Price?" for a standard item with a fixed list price | Bot, with the price | Quick, and nothing is hidden |
| "Price?" that depends on size, site or quantity | Bot asks two questions, then a person quotes | A wrong quote costs more than a slow one |
| Booking a slot | Bot, if the calendar is real; else a person | A bot that double-books is worse than none |
| Complaint, delay, refund | Person, at once | The customer wants to be heard |
| Anything on health, money, law | Person | Rules differ and the answer carries risk |
| Silence for ten minutes after the bot's question | Person reaches out | The bot has lost them |
The last row is easy to miss. A bot asks a question, the customer goes to lunch, and the chat is never opened again by anyone.
Where the handover happens in the conversation
Do not hand over at the end of a long bot flow, after the customer has typed their name, city, budget and need for the third time. Hand over as soon as the customer's answer tells you the chat needs judgement. For a chat on your website, where visitors arrive cold, see what to ask web visitors and when to hand over. On WhatsApp the customer already has your number, so the order is:
- The bot greets, says it is an automatic assistant, and gives two or three buttons or numbered choices.
- One of those choices is always "Talk to someone".
- The bot asks at most two questions to sort the request.
- A person gets the chat, with those answers already attached, and replies in a stated time that the owner decides and keeps. If nobody can keep a time, say "we reply during working hours" and mean it.
The customer should never have to repeat what the bot already heard. If your setup cannot pass the answers across, fix that before adding any more flows.
For example: a heritage-tour operator in Udaipur
This case is invented. A small tour operator in Udaipur gets most of its WhatsApp messages from visitors, many in the evening and many from abroad. Four questions repeat: timings, meeting point, what is included, and whether children can join. The owner and one guide handle everything by phone while out with groups.
A bot answers the four questions in English and Hindi at any hour and offers "Talk to someone" on every reply. When a visitor asks for a private tour, a change of date or a price for a group of twelve, the bot asks for the date and the group size and stops. The owner replies when the tour ends.
The first mistake was letting the bot quote group prices from a table. A visitor with fourteen people got the rate for twelve and arrived angry. Price questions for groups now sit behind the handover, and the bot says a person will confirm the figure.
When not to use a bot at all
Skip it if you get a few messages a day and you can answer them yourself within the hour. A bot is one more thing to maintain. A customer who wanted you and met a menu may not return. Skip it, too, if one person owns sales and delivery and is unreachable after a certain hour. An honest away message naming the hour you will reply beats a flow that promises more.
Choose a bot when you get repeat lookups in volume, when messages arrive outside working hours, or when two or three people share one number and answers differ between them.
Decide the stop line first
Before choosing a tool, write the handover sentence and the table above for your trade. Then ask any provider one definite question: can this tool pass the customer's answers to a person, so nobody types them again? WhatsApp Business API setup is the service that covers the number, the account and the provider, and the marketing hub shows how it sits with the rest. If you want a second pair of eyes on your handover rule, tell us what you need.
