You connect your store or shipping provider to your flow with an HTTP request. When a customer asks about their order, the flow looks up the status by phone number or order number and sends the current state along with the tracking link. Proactive works too: on a status change, your system sends a utility template to the customer.
Why this works
- For online stores, order questions are often the largest category of incoming messages
- The answer is already in a system — no person needs to get involved
- Reporting proactively heads off the question entirely
- A tracking link in WhatsApp gets opened more often than one in email
The flow, step by step
Ready-to-use message copy
Take these and adjust them to your own tone of voice. The flow fills in the variables in double curly braces for you.
| Message | Text |
|---|---|
| Status question | “Your order {{orderNumber}} is {{status}}. Expected delivery: {{date}}. Track it here: {{trackingLink}}” |
| Shipping notification (utility template) | “Good news! Your order {{orderNumber}} is on its way. Track your package: {{trackingLink}}” |
What you need
- An Easy Flow Builder subscription at €50 per month
- A WhatsApp Business API number through Meta onboarding
- For conversations you start: an approved message template
- Optional: an API integration with your own system
Frequently asked questions
Can I send a message myself when a status changes?
Yes, with an approved utility template. Utility messages concern an ongoing transaction and may be sent outside the 24-hour window, provided the customer has given opt-in.
Does this work with my store?
If your online store has an API or a webhook, yes. Shopify, WooCommerce, and Lightspeed are the most-used integrations; through Make or Zapier almost any other system works as well.
What if the customer doesn't know their order number?
Then the flow looks it up by phone number. If that turns up more than one order, you show them in a list message and let the customer pick.