Bookings · 4 min read
How do I take orders on WhatsApp without losing them?
The short answer
WhatsApp is fine for the conversation and bad for the record. Keep it as the place people talk to you, but make the order itself land somewhere structured — a form, a booking, a basket — so it has a date, a status and a price rather than existing only in a chat you have to scroll.
On this page
A large share of small businesses here run on WhatsApp, and the advice to stop is usually written by someone whose customers do not use it. Nobody is going to move to a form because a website told them to.
So the question is not how to get people off WhatsApp. It is how to stop the orders disappearing inside it.
Where orders actually go missing
Not in the conversation — in the gap between the conversation and the work.
Someone messages on Thursday asking for a delivery on Saturday. You reply. Four other people message. On Friday you are looking at forty unread chats trying to remember who wanted what and when, and one of them scrolled past. The customer does not complain. They just do not come back, and you never learn why.
That is the failure mode, and it has nothing to do with WhatsApp being bad software. A chat is a conversation, not a record. It has no date field, no status, no total, and no way to answer "what is due tomorrow" except by reading everything.
Keep the chat, move the commitment
The change that works is small: let people talk to you wherever they like, and make the commitment land somewhere structured.
Concretely, that means when a conversation turns into an actual order — a date, a quantity, a price — it gets written down somewhere that has fields. A booking, a form submission, a basket, an order line. Somewhere you can sort by date and mark as done.
The conversation stays on WhatsApp. The obligation does not.
The three things the record needs
It does not need to be elaborate. It needs:
- A date. What is due, and when. This is the one that prevents the Saturday problem.
- A status. Waiting, confirmed, done. Three states is enough for most businesses and more than most have.
- Who and what. A name, a way to reach them, and what they asked for.
If your current system cannot answer what is due tomorrow in one look, that is the gap, whatever the software is called.
Send them to the form, from the chat
The practical move, which costs nothing: keep a short link to your booking or order page, and paste it into the conversation once the person is clearly buying.
"Yes we can do Saturday — send it through here so it does not get lost" works, because you are not asking them to use a form instead of talking to you. You are asking at the moment they already decided, which is the moment people will do a small amount of work.
This is what Helm is built around, and it is why it suits a business that runs on chat rather than one that has abandoned it. A request lands in your dashboard as Pending and carries the person's name, their email, their WhatsApp number, the thing they want, the date they want it and whatever they typed. You accept or decline it in one tap, and the confirmation goes out in the language they wrote to you in.
So the thread and the record point at each other instead of living in separate worlds — you still reply in the chat they started, and the obligation is now somewhere you can sort by date. Nobody has to be moved off WhatsApp for that to work, which is the reason most attempts at this fail.
If you already have a site you like, bookings can be added to it without rebuilding anything, and this covers what a booking system actually needs to do.
Reply in the language they wrote in
Worth a line because it gets missed: if someone messages you in Arabic, the confirmation should go back in Arabic. It sounds small and it is the difference between a business that feels local and one that feels like a form.
We wrote about what bilingual booking actually involves — the request is the easy half, and the reply is where most setups fall over.
What not to do
Do not move everything to a form and hope. You will lose the customers who were only ever going to message you, and they are often your best ones.
Do not run two systems that do not know about each other. A form that lands in an inbox nobody opens is worse than the chat, because at least the chat gets read. If enquiries dried up without an obvious reason, test the form before you rebuild anything — a silently broken form looks exactly like a quiet month.
The test
At the end of a busy week, can you answer three questions without scrolling: what is due tomorrow, who is still waiting on a reply, and what did we take this week?
If yes, your setup is fine however informal it looks. If no, the fix is not more discipline. It is one place where the commitments live.