WhatsApp order confirmations and shipping updates, automatically
Automatic WhatsApp order confirmations are approved utility templates that a store's own system sends through Meta's Cloud API when an order event happens: placed, shipped, out for delivery, delivered. Each template names the specific order and carries no offer, as Meta's utility category requires. A customer's reply opens a 24-hour window in which automated answers can follow.
easyCoexistence connects the WhatsApp Business number your store already uses in the app to Meta's Cloud API through Coexistence and gives your store its credentials, in the dashboard or through get_api_credentials, so confirmations and shipping updates come from the number customers know and show in the app's chat.
Meta's category for messages that confirm, update or cancel an order using specific order details, without promoting or upselling.
Meta categorizes an order update that also carries a promotion as a marketing template.
Default time-to-live of a utility template; it can be set from 30 seconds to 12 hours instead.
Unique people a new business portfolio can message outside a customer service window in a moving 24 hours.
Fixed throughput of a number used in the WhatsApp Business app and the Cloud API at the same time.
Messages sent through the Cloud API on a Coexistence number also appear in the WhatsApp Business app.
Which order messages can go out automatically?
Each moment in an order's life can have its own approved template, sent by the store's system when that moment happens. Meta's utility guidelines list exactly these jobs: confirming an order, sharing a tracking number and delivery date, warning about a backordered item and confirming a refund. Keep one template per event, so each template says one thing and each can be reworded without touching the others. A store that ships the same day may need only three of them.
What does a utility order template look like?
A short body that names the customer and the order, positional variables with example values, and an optional button. The example below is what an AI submits through create_template after the request "create a utility template for shipped orders with a tracking button". The tracking button carries a variable at the end of its URL, filled per order at send time. Write text after the last variable, because Meta rejects a body that ends with one, and leave out discounts, product suggestions and review requests: any of them moves the template to marketing.
{
"connection_id": "<from list_numbers>",
"name": "order_shipped",
"language": "en_US",
"category": "UTILITY",
"components": [
{
"type": "BODY",
"text": "Hi {{1}}, your order #{{2}} has shipped with {{3}}. It should arrive by {{4}}.",
"example": { "body_text": [["Ana", "1042", "DHL", "Friday, May 8"]] }
},
{
"type": "BUTTONS",
"buttons": [
{
"type": "URL",
"text": "Track package",
"url": "https://shop.example.com/track/{{1}}",
"example": ["https://shop.example.com/track/1042"]
}
]
}
]
}How does the store send each update?
Through Meta's Cloud API, from the store's own system, with the number's credentials. In the easyCoexistence dashboard, the number's "Plug in your own system" card shows the Send endpoint and "Reveal access token"; your AI returns the same values with get_api_credentials. The store, or an n8n, Make or Zapier workflow listening to its order events, posts one request per customer and fills the variables from the order record. The tracking button's variable goes in a separate button component, as in this request. Without Graph code, an automation with the trigger Your system calls a URL does the send: the store posts {"to": "+5511987654321", "name": "Ana", "order": "1042"} to the URL shown in the editor with the automation's secret as a Bearer token, and a Send a template step fills the template from {{vars.webhook.name}} and {{vars.webhook.order}}.
POST https://graph.facebook.com/<VERSION>/<PHONE_NUMBER_ID>/messages
Authorization: Bearer <ACCESS_TOKEN>
{
"messaging_product": "whatsapp",
"to": "5511987654321",
"type": "template",
"template": {
"name": "order_shipped",
"language": { "code": "en_US" },
"components": [
{ "type": "body", "parameters": [
{ "type": "text", "text": "Ana" },
{ "type": "text", "text": "1042" },
{ "type": "text", "text": "DHL" },
{ "type": "text", "text": "Friday, May 8" }
]},
{ "type": "button", "sub_type": "url", "index": "0",
"parameters": [{ "type": "text", "text": "1042" }] }
]
}
}Can your AI send an order update instead?
Yes, for the updates a person decides on. With the easyCoexistence connector in ChatGPT or Claude, "tell Ana at 5511987654321 that order 1042 is delayed until Monday, with the order_delayed template" becomes one send_template call to one recipient, and ChatGPT may ask you to confirm before it runs. That suits a late parcel, a manual order or a test of a new template. The routine updates belong in the store's system, because an assistant acts only while someone is chatting with it. Those go from the store's system, or through an automation that your system starts by calling its URL, which can send an approved template to a customer who has not just written to the number.
What happens when a customer replies to an update?
The reply lands in the WhatsApp Business app, next to the template the store sent, and it opens a 24-hour window in which any text can go back. On a number whose messages come through easyCoexistence, it can also start an automation. A Has keyword automation can catch order questions and pass them to your backend with Call my webhook, which is the setup described on the order status page. A quick-reply button in the template, such as "Change address", arrives as a message with the button's text, so a keyword automation set to Is exactly can answer that tap. One detail: a customer with no recent chat history counts as writing for the first time, so word a First message greeting to read well after an order update; a customer whose update went out through an automation your system started already has a chat on our side, so their reply is not a first message.
How do you know an update reached the customer?
Meta reports a sent, delivered, read or failed status for the number's outgoing messages on its webhook. With the number set to Through easyCoexistence and a Forward URL, they reach your system signed per number, inside Meta's original payload; with Send straight to my system, Meta posts them to your endpoint. Mark an update as delivered only after the delivered status arrives, since an accepted request is not a delivery. Time-to-live matters for time-bound updates: Meta keeps retrying a utility template for 30 days by default, so set a few hours on out_for_delivery, and Meta drops the message once that time passes instead of delivering yesterday's news.
How to set it up
- Collect WhatsApp opt-in at checkoutAdd a line near the phone field that names your business and says order updates come by WhatsApp, and save the phone in international format.
- Get the templates approvedAsk your AI to create order_confirmed, order_shipped and order_delivered as UTILITY with create_template, then check get_template_status until each reads APPROVED.
- Copy the credentialsOpen the number in the dashboard, find "Plug in your own system", copy the Send endpoint and click "Reveal access token". Store the token on a server.
- Wire each order event to a sendIn your store or n8n workflow, post the matching template when an order is placed, fulfilled or delivered, with the variables taken from the order.
- Answer the repliesKeep the number on Through easyCoexistence under Where incoming messages go, and add a keyword automation with Call my webhook for order questions, plus a Forward URL to receive delivery statuses.
Common mistakes
- Adding "10% off your next order" to the shipping template. Meta treats mixed content as marketing, so the update is approved, or later recategorized, as a marketing template and billed and limited as one.
- Picking the tracking template in an automation's Send a template step. A URL button with a variable cannot be filled by automations yet; send it from the store's system.
- Leaving out_for_delivery at the 30-day default time-to-live. A phone that comes back online two days later still receives "arriving today"; set a few hours.
- Treating the message ID in Meta's response as proof of delivery. Accepted sends can still fail; wait for the delivered status before you mark the update as sent.
Automations answer the replies, and every number is monitored 24/7, with an email when Meta stops delivering its templates. US$ 9 down to US$ 0.75 per number per month, falling as you add numbers, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Do I need opt-in to send order confirmations on WhatsApp?
Yes. Meta's policy covers any message the business starts: the customer gave you the number and agreed to hear from your business. Since November 2024 that permission can be general rather than specific to WhatsApp, as long as it names the business and follows local law, so a clear line at checkout works.
Does Meta charge for order confirmations?
Meta bills template messages per message, by category and the customer's country, to your own WhatsApp Business Account; Meta's pricing page lists the current rules for your markets. easyCoexistence adds no markup and no per-message fee, and automations cost nothing extra.
Can the confirmation carry the invoice as a PDF?
Yes, from your store's system: a template with a document header receives the PDF link at send time. Automations cannot send a template with header media. The Send a picture or file step sends a PDF you uploaded, the same for everyone, so a per-order invoice goes out from the store or through your AI's send_template call.
What if the customer's phone number is not on WhatsApp?
Meta accepts the request and then reports a failed status, commonly error 131026 for an undeliverable message. Have your system watch for failed statuses and send that customer's update by email or SMS instead, so nobody misses a confirmation because of a typo at checkout.
Keep reading
Ready to get started?
Set up WhatsApp Coexistence in minutes, not months. The app keeps working on the phone.
Start Free TrialVerified on