Channel Fallback
Use Workflows to build multi-channel delivery pipelines with automatic fallback when the primary channel fails.
How It Works
- Create a workflow with multiple channel steps
- Add delay steps between channels
- Use branch steps to check delivery outcomes
- If the primary channel fails or goes unread, the next channel fires
Example: Push → Email Fallback
Build a workflow that sends push first, then falls back to email if push isn't delivered:
- Push step — Send push notification
- Delay step — Wait 1 hour
- Branch step — Check if push was delivered
- Email step (on "no" branch) — Send email as fallback
Workflow Builder
The easiest way to set up channel fallback is using the visual Workflow Builder in the dashboard. Drag and drop channel steps, delays, and branches to create your delivery pipeline.
Fallback Triggers
- Push: Device token invalid, delivery failed, notification not read
- Email: Bounce, rejected, not opened
- SMS: Undeliverable number, carrier rejection
- In-App: Notification not read within timeframe