What Meta's rules allow, and what they don't
WhatsApp Business is the most rule-constrained channel we work with, and most implementation failures are policy failures rather than technical ones. Outside a 24-hour service window you can only reach a customer through a pre-approved template, opt-in has to be genuine and recorded, and template approval takes time that belongs in the project plan. Business verification with Meta is a prerequisite, not a formality. We scope the template inventory early, because a conversation design that depends on a message Meta will not approve has to be rebuilt from scratch rather than adjusted.
Where the human gate goes
Messaging feels informal, which makes it the channel where an automation is most likely to be asked something it should not answer alone. Anything touching a price commitment, a medical or legal question, a complaint, or a change to an existing booking stops and transfers to a named person with the conversation history attached. The assistant answers from approved material and collects structured details — dates, reference numbers, contact preferences — so that when a person picks the conversation up, the tedious part is already done and the judgement part is untouched.
Process WhatsApp messages with consent and delivery state
Normalize each inbound webhook into an internal record containing the business account, provider message ID, sender reference, received time, message type and conversation context; this makes the workflow independent of vendor payload formatting. Validate the event, deduplicate by account and provider message ID, check the recorded contact preference before any outbound action, and select only an approved template or an allowed in-window reply under the current platform rules. Keep sensitive requests and uncertain intent in a named human queue. Record send and delivery outcomes separately from the conversation itself, retry only transient failures with a bounded policy, and reconcile unknown send outcomes before retrying to avoid duplicate messages. Restrict the log to the context needed for support, and document who owns template approval, failed-message review and credential revocation.
How to measure the pilot
A pilot is accepted against the current process, not an industry promise. Agree the sample, baseline and owner before launch, then review the same measures after the workflow has handled real cases.