Selling on WhatsApp: the 24-hour window and lost messages

The 24-hour window

A message from the customer opens a 24-hour window during which the business can write freely, in any wording. Once it closes, free-form text no longer goes through: only pre-approved templates do.

This is where most scenarios designed without that rule fall apart. "Remind the customer in three days" does not work as an ordinary message. It needs a template submitted for review in advance, worded so that it passes.

Why "ok" does not mean "delivered"

The API returns success for accepting the message, not for delivering it. After that it can fail for a dozen reasons, and the most common carries code 131049: the platform itself limits how many messages reach a given recipient, to keep marketing from flooding them.

The practical consequence is simple: after every send, read the status log rather than the response code. A system that treats an API acknowledgement as success will report a hundred delivered messages on a day when seventy arrived.

What to automate and what to leave alone

Automates well: order confirmation, delivery status, sending the invoice, payment reminders. These are messages the customer is waiting for, and the platform passes them most willingly.

Automates badly: the sale itself. A bot trying to walk someone through choosing a complex product irritates faster than it helps. The split that works: the bot takes everything repetitive and hands a human the moment where a decision is needed.

In our own messenger-based sales system, twenty months produced 3,332 processed messages and 260 orders. The bot there does not sell — it receives, confirms and reminds.

Frequently asked