To order from your app someone has to have downloaded it, remember it exists, find it among forty others, be logged in and not have forgotten the password. Five conditions. WhatsApp has none — and WhatsApp is already open.
What the agent really looks up is your stock: it says whether there is any or not, never how many units are left. The order closes in your store, where prices are recalculated on the server and the sale lands in Sales like any other channel. The agent does not confirm orders and does not charge — that happens where there is a number that can be verified.
Food is the most repeated order there is, and the channel that pays no marketplace commission is exactly the one with the most friction to repeat it.
And never opened again. Someone who installed and did not come back is a customer you already won and are losing every month.
The message arrives anyway. It sits unanswered until morning, and by morning they ordered somewhere else.
Hours, address, payment methods, and whether a product is in stock — that last one looked up against your real stock, not a list loaded on the side that goes stale. Of stock it says whether there is any or not, never how many units are left.
It sends the link. That is your catalogue, with prices recalculated on the server, and the sale lands in Sales with its channel and its customer, just like a counter order. The agent does not confirm orders and does not charge.
If it cannot solve it, a person on your team picks it up with the whole conversation in view. Nobody asks the customer to explain again.
If it is asked something it does not know, or for a complaint, a refund or anything with consequences, it says it is passing it to a person. A customer waiting a while for someone on the team is far better than an invented answer.
| A reply bot | Delorean | |
|---|---|---|
| What it knows about your business | Whatever someone loaded into a flow, last week | Your hours, your address and your real stock, looked up on the spot |
| Where the menu comes from | A list loaded separately, which goes stale | The same catalogue your app uses, with today prices |
| When it does not understand | Repeats the options menu | Hands over to a person with the full conversation |
| What happens next | The conversation closes and is lost | It stays in Customer support, for a person to pick up |
| Charging | Sometimes asks for card details over chat | Never, and it cannot: the order closes in your store and is paid on delivery |
| If the customer returns | Starts over | The thread carries on where it stopped: the messages are kept |
| Where the sale lands | Nowhere, or in a separate spreadsheet | The same table as every other channel, with its customer and amount |
| Who configures it | An integrator, with a flow editor | You, writing the brief in plain language |
Written from each product's public documentation. They are mature tools and this page says where they are still better. No prices here: they change on their own and the page would end up lying without anyone touching it.
One branch WhatsApp Business number connected to its real catalogue and prices. The app and the marketplace stay exactly as they are.
Levels and rewards: whoever orders three times a week moves up, and gets something the marketplace does not have. That is the concrete reason they stop ordering there.
The rest of the locations, the regional board, and a daily summary that arrives on its own at eight in the morning without anyone opening a screen.
No. They write to the brand WhatsApp the way they write to anyone. No app, no signup, no password.
It is a WhatsApp Business number connected through the official Meta API. It can be the one you have or a new one; routing is decided by the number itself, so two brands can share the same system without mixing.
It hands the conversation to a person with the whole thread in view, and a ticket remains with an owner. The odd case is not lost: it is escalated.
Never, and it cannot: it has no tool that writes. It sends your store link and the order closes there. No card data goes through the chat.
The same catalogue your app uses. There is no second list someone has to remember to update.
Yes. Each brand has its number, its catalogue and its points programme, and the system is the same. What is not shared is one brand customers with the other.
They stay the same. This replaces nothing: it adds a channel that does not exist today, for the customer who was never going to download the app.
Yes, the same agent. Same knowledge, same stock, same points, for the visitor who arrived from a campaign and has not downloaded anything yet.
You write the brief in plain language, the way you would to someone starting a job. There is no flow editor and no nodes to connect.
In the same table as every other channel, with its customer, amount and origin. "How much did I sell today" has one answer, not three partial ones that do not add up.