Skip to main content

Delivery & History

This page covers when a scenario's message goes out, who it goes to, and how to review what was actually delivered.

Dispatch Delay​

By default, a scenario's SMS goes out the moment its trigger event fires. Want to hold off instead? Use the Dispatch delay (minutes) field.

  • 0 (or blank) sends immediately.
  • Any whole number of minutes waits that long after the event before sending. For example, 5 waits 5 minutes.
  • The maximum delay is 24 hours (1,440 minutes).

Delays are handy for follow-up messaging — say, 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 yet.

Common delays​

Handy conversions for the most common delays:

DelayMinutes
Immediate0
1 hour60
8 hours480
24 hours1440
note

The delay has to be a whole number of minutes between 0 and 1,440. The scenario won't save if the value falls outside that range.


Custom Receiver​

By default, messages go to the customer's phone number on the order. Need all messages for a scenario to go to a fixed number instead — say, a staff notification? Set the Another receiver field when creating or editing the scenario.

This replaces the customer number entirely for that scenario.


Message History​

Open Message history (the 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​

StatusMeaning
PendingAccepted by the carrier, waiting for delivery confirmation
DeliveredCarrier confirmed the message reached the handset
FailedDelivery failed (invalid number, carrier rejection, etc.)

Delivery status updates come in asynchronously, so a message may sit at Pending for a few seconds before flipping to Delivered.