WhatsApp order status automation
A WhatsApp order status automation answers "where is my order?" with live data from the store's own system. A keyword step catches the question, a webhook sends the message and the customer's phone number to the store backend, and the backend returns the status as the reply. Shipping updates the store sends first go out as approved utility templates.
easyCoexistence connects the WhatsApp Business number your store already uses in the app to Meta's Cloud API through Coexistence.
Time the store backend has to return a reply before the webhook step fails and you are emailed.
The customer's WhatsApp number in international digits, sent with the message so the backend can find orders by phone.
Longest reply sent as one WhatsApp text; anything longer is cut.
Meta's category for order confirmations and shipping notices: non-promotional and specific to the customer's order.
Meta treats a template that pairs an order update with a promotion as marketing.
Meta's fixed throughput for a Coexistence number, the ceiling for a burst of shipping updates.
How does an automated order status reply work?
The status lives in your store system, so the automation's job is to carry the question there and the answer back. A keyword automation catches order questions, its Call my webhook step posts them to your backend, and the backend's answer goes out from your WhatsApp Business number. easyCoexistence holds no order data: the run log keeps the message and the reply for 30 days, and your store remains the source of truth. The same lookup can also be a Call an API step, which calls your store's API directly and keeps its JSON answer for the steps after it.
Which messages should start the lookup?
Order questions are easy to spot by their words, so a keyword automation fits. Start from Send to my system and change its trigger to Has keyword with Contains, or start from Keyword reply and swap its step for Call my webhook. Add the words in each language you sell in, up to 30. Other questions fall through to the rest of your automations, such as an agent on Every message, because keyword automations are checked first and only one automation answers a message.
- English: order, tracking, delivery, shipped, where is my.
- Portuguese: pedido, rastreio, rastreamento, entrega, encomenda.
- Spanish: envío, envio, seguimiento, paquete (pedido and entrega are already listed).
- Symbols: # catches order numbers written as #1042.
What does the store backend receive, and what must it return?
A JSON POST signed in X-EC-Signature with the automation's Signing secret. The fields that matter for a lookup are contact.wa_id, the customer's WhatsApp number in international digits without the plus sign, and message.text, where an order number may appear. Find the most recent orders for that phone, or parse the number from the text, and answer HTTP 200 with a JSON body whose reply field holds the text to send. Keep it plain and short: up to 4,096 characters go out as one message, and markdown headings or links show as raw symbols.
Request (trimmed):
{
"event": "automation.step",
"dry_run": false,
"contact": { "id": "5511987654321", "wa_id": "5511987654321", "name": "Ana Souza" },
"message": { "type": "text", "text": "Hi, where is my order #1042?" },
"history": [ … up to 10 recent messages, oldest first … ]
}
Response, HTTP 200, within 20 seconds:
{ "reply": "Hi Ana! Order #1042 left our warehouse today and should arrive by Friday. Tracking: https://track.example/1042" }What should the backend say when it cannot find the order?
Something useful in each case. Only one automation answers a message, and a step placed after the webhook would also run after a successful reply, so the backend owns the fallback texts too (with a Call an API step instead, a Split into paths step can branch on the answer):
- Order found: the status, the expected date and the tracking link.
- No order for this phone: ask for the order number, or the email used at checkout.
- Several open orders: list them briefly and ask which one.
- A lost or damaged parcel: say a person will reply in this chat, and alert your team.
- A test, with
dry_runtrue: return a sample reply and change nothing. - Backend down or slower than 20 seconds: the step fails, nothing is sent, and an email tells you so you can answer yourself.
How do you send shipping updates before the customer asks?
Proactive updates are messages your business starts, so they go out as approved templates, sent by your store system through the Cloud API when an order changes status. Create them in the utility category, the one Meta uses for order confirmations and shipping notices; a discount or product suggestion in the same template makes it marketing. Your AI can draft and submit them with create_template, using {{1}} for the name and {{2}} for the order number with example values, and check approval with get_template_status. The store then calls the send endpoint from get_api_credentials on its own order events, or posts to the URL of an automation with the trigger Your system calls a URL (the Updates from your system example), which sends the template with the order details from {{vars.webhook.*}}; the Shopify and WooCommerce pages show that wiring. Meta bills template messages per message, by category and country, to your own WhatsApp Business Account.
What happens when a customer answers a shipping update?
Their reply opens a new 24-hour window, and your automations handle it like any incoming message: a keyword reply, the order lookup or the AI assistant. One detail matters. A customer whose chat has no recent history counts as writing for the first time, so a First message automation can greet someone who is only answering your shipping notice; word the welcome so it also reads well after an update. On a Coexistence number, the template your store sent sits in the app's chat thread, so the team sees the context before stepping in.
How to set it up
- Expose an order lookupAdd an HTTPS endpoint, or an n8n workflow, that verifies X-EC-Signature, finds orders by contact.wa_id or the number in message.text and returns {"reply": "..."}.
- Create the automation, switched OffStart from Send to my system, change the trigger to Has keyword, add your order words, paste the URL into Webhook URL, set the switch to Off and click Save.
- Copy the Signing secretSelect the Call my webhook step of the saved automation and copy Signing secret into your endpoint's configuration.
- Test with Run testClick Test and send "where is my order #1042?" in Try it. Your endpoint receives dry_run true and the sample contact 15550000000.
- Switch it On, then add shipping templatesSwitch the automation On and save, then create utility templates for confirmed, shipped and delivered orders, sent by your store.
Common mistakes
- Returning the status under another field name. Only a top-level string named reply is sent; anything else is logged as no reply and the customer hears nothing.
- Matching contact.wa_id against phones typed at checkout as they are. wa_id has the country code and no plus, spaces or dashes; compare digits only.
- Adding a Reply with text step after the webhook as a fallback. It also runs after a successful reply, so the customer gets two messages; return the fallback text from the backend.
- Putting a coupon in the shipping template. Meta treats mixed content as marketing and can recategorize or reject it; keep offers in separate marketing templates.
Its Call my webhook step carries order questions to your backend and sends back the answer, with a signature, a 20-second limit and a failure email, and get_api_credentials gives your store what it needs to send shipping templates. Automations cost nothing extra. 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
Can an AI step answer order questions instead of a keyword?
Yes. An AI agent with a custom tool, a URL with parameters such as the order number and optional headers, can look the order up itself, or the model can sit behind the webhook, for example an n8n AI Agent node with an order lookup tool that returns its text as reply. A Reply with AI step on its own reads only its instructions and the chat, so it has no live order data.
What if the customer sends the order as a photo or an audio message?
A photo arrives as [image] followed by its caption, so a keyword matches only when the caption carries the word, although an AI agent can look at the picture on your key. A voice message is written out on your OpenAI or OpenRouter key and stored as [voice message] followed by the words, which a keyword can match; without such a key it stays [voice message]. Have the AI or a fixed reply ask for the order number as text.
Can the automation send the invoice or a shipping label as a PDF?
Yes, from your backend: send the document through the Cloud API with the number's credentials, within 24 hours of the customer's last message, and return a short reply that says the file is on its way. The webhook reply itself carries text only. A fixed file, such as a price list, can go from the Send a picture or file step.
How many order questions can it handle at once?
Runs are independent, so several customers can ask at the same moment. easyCoexistence spaces sends to at most 10 per second per number, under Meta's 20 per second for Coexistence, and your backend only has to answer a POST within 20 seconds.
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