Why our WhatsApp AI will never reply to your customers
Every WhatsApp AI on the market can auto-reply. Ours deliberately cannot. Here's why that limit is the product, not a missing feature.
The first question in almost every demo is the same: why can’t it just reply on its own?
Not because we haven’t got round to it. This system has no ability to send, in code: no outbound path, no sending credential, no sendText on the ChannelAdapter. Adding it isn’t flipping a switch, it’s changing the architecture.
Why it’s built this way
The cost of auto-reply isn’t the average case. It’s the worst one.
An AI answers a hundred customer questions and gets ninety-seven right. Of the remaining three, one quotes the wrong price, one gives the wrong lead time, and one commits to something you can’t deliver — and all three have already been sent. What you’re managing isn’t “97% accuracy”. It’s three customers who need cleaning up after.
In draft mode, those same three end differently: a colleague reads the draft, decides it’s wrong, and types their own. The cost is thirty seconds.
Three things that follow from it
Meta bills you nothing. Messages leave from your staff’s own WhatsApp rather than the Business API, so there are no conversation charges and the 24-hour service window never blocks a reply.
IT review is short. “It cannot message our customers” is a property of the code, not a promise about configuration. That distinction carries real weight in a compliance meeting.
AI cost is predictable. One drafting call per settled batch of messages — not one per staff click.
So what is the AI actually doing
When a customer’s message arrives, the system waits 40 seconds. People type one thought across several messages; waiting for them to finish produces one complete reply instead of five fragments.
The draft is written only from knowledge you approved — prices, lead times, policies all reviewed before they entered the knowledge base. With nothing relevant on file, it says so rather than guessing.
Your staff keep using WhatsApp Web. Open a chat, the Chrome side panel shows the draft, copy, send.
When this isn’t right for you
If what you want is closing deals unattended at 3am, this won’t do it. That’s a different product with a different risk profile, and we’d rather say so than quietly add a send path.
