Delivery & History
This page covers when a scenario's message is sent, who it goes to, and how to review what was actually delivered.
Dispatch Delay
By default a scenario's SMS is sent immediately when its trigger event fires. The Dispatch delay (minutes) field lets you wait before sending instead.
0(or blank) → send immediately.- Any whole number of minutes → wait that long after the event before sending. For example,
5waits 5 minutes. - Maximum delay is 24 hours (1,440 minutes).
Use a delay for follow-up messaging — for instance, a review request a few hours after Order taken, or a reminder a few minutes after Ready on pad if the order hasn't been collected.
Common delays
Handy conversions for the most common delays:
| Delay | Minutes |
|---|---|
| Immediate | 0 |
| 1 hour | 60 |
| 8 hours | 480 |
| 24 hours | 1440 |
The delay must be a whole number of minutes between 0 and 1,440. The scenario won't save if the value is outside that range.
Custom Receiver
By default the message is sent to the customer's phone number from the order. If you want all messages for a scenario to go to a fixed number instead — for example, a staff notification — set the Another receiver field when creating or editing the scenario.
This overrides the customer number entirely for that scenario.
Message History
Open Message history (button at the top of the Text Messages page) to see the last 100 messages sent for your account.
Each row shows:
- Phone number
- Message text
- Delivery status: Pending, Delivered, or Failed
- Time sent
Delivery statuses
| Status | Meaning |
|---|---|
| Pending | Accepted by the carrier, waiting for delivery confirmation |
| Delivered | Carrier confirmed the message reached the handset |
| Failed | Delivery failed (invalid number, carrier rejection, etc.) |
Delivery status updates arrive asynchronously — a message may show Pending for a few seconds before flipping to Delivered.