Sending a WhatsApp message after every cash-on-delivery order looks simple: a recap, a “reply YES to confirm”, and the team calls whoever stays silent. Automating it is another matter. Meta decides which messages a business may send and when, charges for most of them, rates every number on how customers react, and can cut the reach of a sender that too many people block. A flow that ignores those rules loses customers twice: once when the message never arrives or reads like spam, and again when the number gets limited in the middle of a sales peak. This guide walks through an automated confirmation flow end to end, from the choice of tool to the moment a person takes over, using Meta’s own documentation.
The Business app or the Business Platform
WhatsApp offers businesses two products, and they do not automate the same things.
The WhatsApp Business app runs on a phone. Its automation stops at a few helpers: a greeting that can automatically send a custom welcome message to new customers, away messages that respond automatically outside business hours, quick replies that act as shortcuts for messages you send often, and labels to organize and filter important customer conversations. With Meta Verified, a business can link up to ten devices and agents to one account. Every confirmation is still typed or pasted by a person and read by a person. That works for a few orders a day; the app will not react on its own to an order placed on the store at midnight.
The WhatsApp Business Platform is the API version, used directly through the Cloud API or through a provider. Meta lists among its uses the ability to send order confirmations and shipment updates and to route conversations to a live agent only when one is needed. Here the store or the order tool sends the message itself the moment the order is created, reads the customer’s answer and updates the order. That is what “automatic confirmation” means in practice, and the rest of this guide is about the Platform.
The choice comes down to volume and to how many people share the work. A seller confirming a handful of orders by hand can stay on the app. As soon as orders arrive faster than one person can answer, or several agents work the same queue, the Platform’s rules are the ones to learn. See our page on the WhatsApp Business integration.
Message templates: the first message needs approval
The first confirmation message goes to a customer who has not written to you. On the Platform, message templates are the only type of message that can be sent outside a customer service window. A template is a text written in advance, with variables for the name, the product, the price and the city, submitted to Meta and reviewed before use. It must have the APPROVED status before it can be sent, and the review can take up to 24 hours. Write and submit your templates well before a campaign starts, in every language your customers use: Meta does not translate templates, so a French version and an Arabic version are two separate templates.
Every template gets a category, and the category sets both the price and how strictly the content is checked. For an order confirmation the right one is utility. Meta describes utility templates as messages typically sent in response to a user action or request, such as an order confirmation. Its categorisation rules place order management among utility uses: confirming, updating or cancelling an order, with the order’s details in the body of the message.
The trap is the extra line. These messages must not include a promotion, a recommendation, an upsell or a cross-sell, and a template that mixes the two, such as an order update with a promotion, counts as marketing. Meta does not wait for a complaint: a utility template created with marketing content is automatically reclassified as a marketing template. A line like “Confirm now and get a discount on your next order” therefore turns a transactional message into a promotional one, which costs more and is received worse.
A sound confirmation template says only what the customer needs to check: who is writing (the store name), the product and its variant, the total to pay in cash including delivery, the city and address on file, and what happens next. For example: “Hello {{1}}, this is {{2}}. We have received your order: {{3}}, total {{4}} payable on delivery, to {{5}}. Please confirm so we can ship it.” The buttons come next.
The 24-hour window and what each message now costs
Once the customer answers, a different set of rules applies. Each message from the customer opens or resets a 24-hour customer service window, during which the business can reply freely without a template: text, an image, a location request. Outside it, only approved templates can go out. The WhatsApp Business Messaging Policy puts it plainly: outside the 24-hour customer service window, you may only send messages via approved Message Templates.
The money side changed on 1 October 2026. The pricing page of Meta’s developer documentation announces the billing of previously free messages: service messages, free since November 2024, and utility messages sent in reply to users within an open customer service window, free since July 2025. Each business phone number now gets a monthly allowance of 1,000 free service messages, and Meta bills beyond that. Some of WhatsApp’s commercial pages still describe the earlier rules, so build your cost model from the developer documentation and check it again before each budget.
Rates depend on the message category and on the country code of the recipient’s number; Morocco has its own line on the rate card. One exception favours sellers who advertise: when a customer writes first from a click-to-WhatsApp ad on the Android or iOS app, Meta opens a free entry point window that can stay open for up to seven days, during which marketing, utility, authentication and service messages are not charged.
The practical consequence is to count messages per confirmed order: the template, the reply that follows, any reminder. A flow that sends five messages where two would do costs more and annoys more people.
Confirm, change, cancel: designing the buttons
A confirmation that asks the customer to type “YES” collects typos, voice notes and silence. Buttons remove the ambiguity. Inside the service window, the Cloud API’s interactive messages let a business send up to three predefined replies for the customer to choose from; each tap sends the business a webhook describing the choice, so the order can update itself. Utility templates can carry quick-reply buttons as well (up to ten buttons), which means the very first message can already offer the choice.
Three buttons fit the job:
- Confirm: the order moves to “confirmed” and goes to packing. Answer with one short line repeating the total and the expected delivery window, nothing more.
- Change: the customer wants another size, colour, quantity or address. The tap opens the service window, so the follow-up can be free-form: ask what changes, record it, and send the corrected recap with the same three buttons.
- Cancel: record it, release the stock, and ask once, without pushing, for the reason (price, delay, ordered by mistake, never ordered). That reason is worth more to your ad buying than any confirmation rate.
Labels are short: each button’s text must be unique and at most 20 characters long. Write them in the customer’s language (“Confirmer”, “تأكيد”, “Confirmar”) and test them on a phone before submitting the template. “Change” is the button that saves sales: a customer who cannot fix a wrong size in two taps tends to cancel, or ignores the message and then refuses the parcel.
When the customer does not answer
Silence is the most common outcome, and the costliest to mishandle. Three facts frame the follow-up. First, a customer who has not replied has not opened a service window, so any reminder must again be an approved template. Second, every delivered template is billed. Third, every unwanted message is a chance to be blocked or reported.
A rule set that works:
- Send the confirmation template as soon as the order is created, while the buyer still has the product in mind.
- If nothing comes back after a few hours, send one reminder template, worded differently, at a time the customer is likely to look at the phone: in the evening if the order came in the evening.
- If the reminder goes unanswered, move the order to the phone queue. A call reaches people who do not read WhatsApp, whose phone storage is full, or whose number has no WhatsApp account at all.
- Set a cutoff in advance, a number of attempts and a deadline, after which the order is cancelled as unreachable and the stock released.
Keep separate statuses for “no reply on WhatsApp”, “no answer by phone”, “wrong number” and “not on WhatsApp”. When a product or a campaign piles up in the first one, the problem is often the message itself: too long, sent at the wrong hour, or from a number customers do not recognise. Our guide to raising the confirmation rate covers the phone side.
Handing over to a person
Automation is allowed, but not as a dead end. The WhatsApp Business Messaging Policy states that a business may use automation when responding during the 24-hour window, but must also have available prompt, clear, and direct escalation paths, and it lists them: in-chat transfer to a human agent, a phone number, email, web support, a store visit or a support form.
In COD confirmation, a person should take over when:
- the customer asks something the flow cannot answer: fabric, sizing, delivery to a workplace;
- the customer replies twice in a row with free text or voice notes instead of tapping a button;
- the address cannot be matched to a city or neighbourhood the carrier serves;
- the tone turns angry, or the customer says they never ordered;
- the order is out of the ordinary: a large quantity, a high amount, a buyer who refused a parcel before.
The handover must carry the context. The agent who picks up sees the order, the messages already exchanged and the button pressed, so the customer never has to repeat themselves. And it should happen inside the window where possible: an agent who replies after the 24 hours have passed is back to templates.
Opt-in and opt-out
WhatsApp’s rule on contact is short: a business may write to someone only if that person gave it their number and it has received opt-in permission confirming that they wish to receive subsequent messages or calls. Meta’s opt-in guide adds that the request must make clear that the person agrees to receive messages and must clearly name the business they are agreeing to hear from. Consent can be collected by text message, on a website, by phone or on paper.
For a COD store the natural place is the order form: a line under the phone field saying that the store will send the order confirmation and delivery updates on WhatsApp to that number. Meta recommends asking separately for each category of message, because it reduces the risk of your business being blocked for sending unsolicited messages. In practice, keep confirmation and promotions apart: agreeing to an order confirmation is not agreeing to next week’s offers. In Morocco, law 09-08 on personal data protection adds its own requirements for marketing messages.
Opt-out is not optional either. The policy requires businesses to respect all requests, on or off WhatsApp, to block, discontinue or otherwise opt out. When a customer writes “stop” or says it on the phone, the number goes on a do-not-message list, and the next order from that number is confirmed by phone.
Quality rating, blocks and messaging limits
Every number and every template on the Platform is rated on how customers react. Users can block or report businesses, and Meta’s systems may limit the amount of messages a business can send based on that feedback. The opt-in guide is blunter still: Meta’s systems impose limits on businesses whose quality stays low for an extended period.
Templates are judged one by one. A template that collects negative feedback or a low read rate drops to medium, then low quality, and can be paused because of repeated negative feedback or a low read rate; a paused template cannot be sent. For a confirmation flow, this means a single badly worded reminder can stop the whole queue overnight. Keep a second approved version of each template ready.
Volume is capped too. Messaging limits count the unique customers a business can reach outside a service window over a rolling 24 hours, and newly created business portfolios start at 250. The limit rises to 2,000 once the business is verified, or after it sends 2,000 delivered messages outside service windows over a rolling 30 days using high-quality templates, and then climbs automatically while quality stays high. A seller who launches a big campaign on a fresh number can hit the 250 ceiling on the first day, and every order beyond it waits for the phone team.
The habits that protect the rating are the ones that keep customers: write only to people who ordered, say who you are in the first line, keep it short, never slip in a promotion, stop at the cutoff, and honour every “stop”.
Where an AI agent helps, and where it does not
Buttons cover the clean cases. The rest, such as “is it the black one I chose?”, “can you deliver to my office tomorrow?”, a voice note in Darija or a new address typed across three messages, is where a conversational AI agent earns its place. Inside the service window it can read free text, answer questions about the order, collect a corrected address and switch the order to confirmed, changed or cancelled, at any hour.
That is no reason to drop people. The escalation rule applies to AI agents as much as to simple bots, and an agent that guesses an address or invents a delivery date costs more than a slow reply. Give it a narrow brief: the order details, the delivery zones and timings, the returns policy, and a clear instruction to hand over when unsure.
Cost is part of the decision. Meta now sells its own agent on the Platform and bills it by tokens: USD 2.00 per million tokens, with a typical message using between 20,000 and 25,000 tokens, about four to five US cents per message by Meta’s own estimate. Third-party agents are priced differently, but that order of magnitude is a useful benchmark against an agent’s time on the phone. See our page on the AI agent.
Confirming on WhatsApp with Cashod
Cashod can confirm orders over WhatsApp, including with an AI agent: see automatic confirmation. Cashod also includes a call center where agents confirm COD orders by phone, the natural next step for customers who do not reply on WhatsApp.
Whatever the tool, the flow stays the same: an approved utility template sent right after the order, three buttons, one reminder, then a call; a person within reach at every step; consent asked for clearly and every “stop” honoured; and a constant eye on quality, because a blocked number confirms nothing.
