COD orders need a quick yes before the driver leaves.
Cash-on-delivery orders cost time and petrol if a customer isn't home. This demo shows a confirmation sequence with reschedule, address-mismatch and silent-customer branches.
What triggers this workflow
Order webhook from the storefront or order-management system fires with the customer's contact, item, amount and slot.
Source: Storefront / OMS webhook
Workflow steps
- Twenty CRMCaptureOrder details land in Twenty CRM as a COD Order record.
- Twilio + n8nConfirmSMS sent with order, slot and amount; customer replies YES / NO.
- n8nBranchConfirm / reschedule / wrong-address / silent — each leads to a different next step.
- ChatwootNotifyWrong-address branch flags dispatch; silent branch holds the slot for 2 hours.
Tools used
Human handoff
Wrong-address orders go to a person
If the customer's reply doesn't match the recorded delivery address, the workflow pauses dispatch and pages the dispatcher with the conversation attached.
- Address mismatch flagged by the customer's reply
- Customer reports a damaged or wrong item
- Two failed confirmations on the same order
Try it in your browser
Edit the sample inputs, choose a branch, and see what the workflow produces. The sandbox runs offline — no accounts touched, no messages sent.
Try it in your browser
Edit the inputs, pick a branch, and see what the workflow produces. Runs entirely in your browser — no messages are sent, no accounts are touched.
1. Trigger
New COD order ORD-22841: Mixed hardware pack. Amount on delivery: $85.40. Window: Tuesday 1–4pm.
2. Confirmation path
Hi Hannah, Bayside Building Supplies here. Confirming order ORD-22841 for Tuesday 1–4pm. $85.40 cash on delivery. Reply YES to lock in or NO to reschedule.
- Order
- ORD-22841
- Status
- Awaiting customer reply
- Window
- Tuesday 1–4pm
- Amount
- $85.40
Sample data only. Numbers, names and messages are placeholders for illustration. Wire the live workflow separately using the setup notes below.
n8n workflow template
n8n template — LGM 08 Dispatcher (SIMULATED, inactive). Ships with active: false — no live integrations are wired. See the setup section below for the wiring checklist, and download the JSON to inspect or import it.
Setup for production
Wiring it for production
Live deployment needs the order source, SMS sender and a dispatcher inbox.
- Configure the order webhook from the storefront or OMS.
- Add the SMS sender and a stop-keyword handler.
- Set the silent-customer window in the n8n workflow (default 2 hours).
- Wire the wrong-address branch to a Chatwoot dispatcher inbox.
Production prerequisites
- Order source with a reliable webhook
- SMS sender with Australian delivery enabled
- Dispatcher on call during delivery windows
Nothing here runs by default. Configuration has to be in place before any live send, booking or contact write.
Questions
What happens if the customer never replies?
The slot is held for the agreed window (default 2 hours) and then released. The order is tagged 'no response' for reporting. A re-engagement can run later with consent.
Can the customer reply from a different number?
Only if the reply comes from the same number that received the confirmation. Otherwise it's a fresh lead, not a confirmation — the workflow ignores it.
More demos you can run in your browser
Cash-on-Delivery Confirmation across the platform
Want this cash-on-delivery confirmation workflow running on your stack?
Pick the demo you're curious about or describe your own. We'll come back with what a real deployment looks like for your business — the workflow, the prerequisites, the people involved.