SMS queue fallback
Use SMS when the primary message cannot get through
Wait Wherever treats SMS as a deliberate fallback path, keeping the customer journey resilient without sending every event twice.
Live product workflow · Customer and staff views · Queue operations in context
Controlled fallback path
Queue event
Created
Attempted
Delivery result
Failure recorded
SMS
Fallback
A customer has joined correctly, but their WhatsApp ready notification receives a failure result. The system records the failure and attempts the approved SMS message.
Product interface with queue-specific context.
What changes
Fallback with a reason, state, and visible outcome
Staff are not asked to guess whether an update was sent. The delivery sequence stays tied to the visit event.
Event-based messages
Fallback supports the same joined, near-ready, ready, and cancelled journey.
Failure-driven routing
SMS is attempted after an explicit WhatsApp delivery failure.
Transparent variable costs
Rates depend on destination and channel and are shown before activation.
The workflow
From first action to a clear outcome
Every step leaves the customer and staff with an understandable current state and a valid next action.
Prepare the queue event
The customer reaches a notification moment in the queue.
Try WhatsApp first
The primary channel receives the first delivery attempt.
Receive a failure
Fallback waits for an explicit delivery failure rather than a timer guess.
Attempt SMS
The system sends the matching fallback message and records the result.
Delivery-aware design
One customer event, one controlled fallback sequence
The model supports reliable communication without presenting SMS as a separate bulk-messaging product.
Product scope
Clear boundaries for this capability
- No two-way texting
- No marketing campaigns
- No universal per-message price
Continue exploring
Build the surrounding queue journey
Move to the adjacent capability or operating context without losing the product boundary.
FAQ
Questions, answered clearly
The useful details belong in the open, especially where product scope, pricing, or delivery conditions matter.
Can SMS be the primary channel?
The notification flow uses WhatsApp first, with SMS fallback after an explicit failure.
Is messaging included in subscription pricing?
No. Applicable messaging rates are shown separately because destination and channel pricing varies.
Map this capability to your queue
See how sms fallback fits your workflow
We'll map Wait Wherever to your locations, queues, staff workflow, and expected monthly volume so you can see exactly how it fits.