WhatsApp Business API: what it takes to run one properly

Most teams approach the WhatsApp Business API expecting an integration problem and find an operational one instead. The technical work is well documented and fairly routine. The parts that cause delays are the rules about when you are allowed to send anything, and the question of who reads the replies.

What you cannot do

The most important constraint first: you cannot message people freely.

WhatsApp separates two situations. When a customer messages you, a 24-hour window opens during which you can reply with whatever you like. Outside that window, you may only send a template — a message whose content was submitted and approved in advance.

This single rule shapes everything. Support workflows are comfortable, because customers start the conversation. Marketing and notification workflows are not, because you are initiating contact and every variation of every message needs to exist as an approved template.

Opt-in is not optional

You need permission before contacting someone, and you should be able to say where that permission came from — which form, which checkbox, on what date.

This matters beyond compliance. WhatsApp tracks a quality rating based on how recipients react. Enough blocks or reports and messaging limits tighten; keep going and access can be withdrawn. The channel polices itself more aggressively than email ever has, and a list built without genuine opt-in degrades quickly.

Templates take time

Templates go through review. Approval is usually quick but not instantaneous, and rejections happen — most often for messages that read as promotional in a category declared as transactional, or for placeholders with no example content.

Two practical consequences:

• Submit early. Treat approval as a scheduled task with lead time, not a launch-day formality.
• Design for variables. A template with well-chosen placeholders covers many cases. One hardcoded string covers one, and you will be back in the queue for the next.

A pattern that works

Keep a small set of general templates that open a conversation — an order update, an appointment reminder, a "we have an update on your enquiry" — and let the substance happen in the free-form window their reply opens. Fewer templates to maintain, less time in review, and the conversation is more natural.

The part that gets underestimated

Once WhatsApp works, people reply. Immediately, and at all hours, with the expectation of a fast response that the medium implies and email never did.

Before launching, settle:

• Who monitors the inbox, and during what hours?
• What is the response-time expectation, and is it stated to the customer?
• What happens outside those hours? An honest automated reply setting expectations is far better than silence.
• Where does the conversation live afterwards? If it stays only in WhatsApp, your CRM has a growing blind spot.

That last point is worth planning for early. A channel your customers use heavily and your system of record knows nothing about becomes a problem quietly and then all at once.

Do you need a bot?

Not to start. A shared inbox, a handful of automated replies for the questions you already answer daily, and a fast handoff to a person covers a large share of real deployments.

Automation earns its place when volume genuinely exceeds what people can handle, and by then you will have transcripts telling you exactly which questions to automate. Building the bot first means guessing at those, and the guesses are usually wrong in ways the transcripts would have shown you for free.