Order status
Tell customers how their order is progressing.
- Staff manually look up every order status enquiry.
Example paths: the agreed action or human review. This diagram does not run on your live data.
- 01Input: Order number.
- 02The order number is checked in the order system; the customer receives the permitted status and date.
- 03Output to verify: Customer reply.
- 04Exceptions go to staff; permitted actions are agreed before launch.
- ✓Customers see only the permitted status of their order; errors go to staff.
- ✓We check repeated processing and connection failures using agreed examples.
An illustration of the logic, not a customer case. Connections and results are agreed before implementation.
What inputs do we need?
We need an example of “Order number”, processing rules and an owner for “Customer reply”. Access is requested after connections are agreed.
What happens if data is missing or an error occurs?
We check “Order found?”. Exceptions go to staff; permitted actions are agreed before launch.
How is the result accepted?
Customers see only the permitted status of their order; errors go to staff.
How long does implementation take?
Scope, price and timing are defined after checking systems, access and exceptions. This page describes a possible workflow, not a ready connection to your data.
Other automations
Document preparation
Draft contracts, acceptance records and letters from approved templates.
View details →HRInitial candidate interviews
Run an initial conversation and prepare a factual summary for the recruiter.
View details →SALESEnquiries from every channel
Bring website, email and messaging enquiries into one sales queue.
View details →