Check an order
template.
The Check an order template is a ready-made Dazza workflow for “where is my order?” questions. Dazza sends order number and email to your own system, once the customer has proved who they are, and answers with what your system replies. Every detail, check and message can be changed.
The questions
it answers.
Dazza uses it when the customer asks where their order is, when it will arrive, or about an order’s status. You can change that sentence, and Dazza follows the new one.
“Where’s my order?”
“When will order 2048 arrive?”
“Has my order shipped yet?”
“My tracking hasn’t updated in three days.”
“Can I have the tracking link?”
What it asks for.
Nothing more.
Dazza asks only for what’s missing, never for what it’s already been told, and checks emails, numbers and dates as it goes. Add, remove or reorder details, up to 10.
| DETAIL | TYPE | REQUIRED | CHOICES OR HELP |
|---|---|---|---|
| Order number | Short text | Required | — |
| Required | Check it matches the order before sharing details |
Where the job
goes next.
This template uses Call your system. Switch to another way to finish, or add decisions that choose between them.
Send to your team
The request lands in the Team queue of your inbox with every detail, and your team gets an email.
SWITCH TO IT ANY TIMEShare a link
Dazza shows a button to a page, such as your booking page or a form, with details filled into the address.
SWITCH TO IT ANY TIMECall your system
Dazza sends a signed request to your system and answers from the reply. Scale and above.
AS IT COMESPOST https://your-system.example/dazza
content-type: application/json
x-dazza-event: action.run
x-dazza-timestamp: 1793097720
x-dazza-signature: sha256=9f2c…
{
"event": "action.run",
"action": {
"id": "act_…",
"name": "Check an order"
},
"run": {
"id": "run_…",
"test": false
},
"inputs": {
"order_number": "2048",
"email": "jamie@example.com"
},
"conversation": {
"id": "cnv_…",
"pageUrl": "https://yourbusiness.com/…"
},
"customer": {
"email": "jamie@example.com",
"name": "Jamie",
"verified": {
"email": "jamie@example.com",
"via": "code",
"userId": null
}
},
"sentAt": "2026-10-27T10:42:00.000Z"
}{
"message": "Order 2048 left our warehouse yesterday with DPD and is due on Thursday between 9am and 1pm. Tracking: https://track.example/2048"
}The checks,
out of the box.
Every check runs in code before the workflow does, so none of them rely on the AI behaving. Change any of them per workflow.
| Check | As it comes |
|---|---|
| Customer confirms first | Off. It runs as soon as the details are complete. |
| Customer verifies their email first | On. The customer proves who they are with an email code or your site’s signed login before it runs. Growth and above. |
| Team approves before it goes ahead | Off. Turn it on to have your team approve or decline each one in the inbox (Growth and above). |
| Starts in | Test, so it only runs in your preview until you set it to Live. |
| Email and messaging apps | Used as it comes, since it needs no button. It runs once the customer is verified, such as a sender whose domain passes DMARC. |
| Plan | Scale and above. |
Who it suits.
How to adapt it.
The groups are a guide, not a rule. Any business can use any template, renamed to fit.
Who it suits
- Online stores with their own order system or API
- Stores that use Make or n8n
- B2B suppliers whose buyers ask about order status
Tips for adapting it
- Check that the verified email matches the order before you reply. Dazza sends it as
customer.verified.email. - Reply with the status, carrier, tracking link and expected date, plus a
message. Dazza explains it in your tone. - Put what Dazza should do about problems in your reply, such as “offer the team if it’s marked lost”.
- Zapier’s Catch Hook always replies with the same short receipt, so it can’t hand order details back. For lookups through Zapier, connect Zapier’s MCP server in Connections instead. Make (with a Webhook response module), n8n (with a Respond to Webhook node) and your own API can reply with data.
Does it work with Shopify?
Yes, but you don’t need this template for it. Connect your shop in Connections (Growth and above) and Dazza looks up and tracks orders itself, when the order number and the email the customer ordered with both match. Use this template for other order systems. See Connect Shopify.
Why does the customer have to verify?
So one customer can’t read another’s order by typing their order number. Dazza asks for a code sent to their email, or trusts your site’s signed login, before it calls your system.
What if the order isn’t found?
Reply with a message that says so, such as “We can’t find that order for this email”. Dazza passes it on and offers the team.