SMS Fallback
Guarantee delivery on every message. When a device or network lacks RCS support, we automatically downgrade to SMS with no extra code.
- 100%
- delivery reach
- 0
- extra code
- <1s
- fallback switch
curl -X POST https://api.conversa.in/v1/rcs/messages \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+919000000000",
"content": { "text": "Your OTP is 4821." },
"fallback": { "channel": "sms", "enabled": true }
}'Everything you need to ship SMS Fallback
Automatic downgrade
Non-RCS recipients receive an SMS with no separate request needed.
Capability detection
We check RCS reachability per number before every send.
Unified billing
Track RCS and fallback SMS spend together in one clear report.
Content mapping
Rich content is condensed into a sensible SMS body automatically.
Built for how you use SMS Fallback
- OTP delivery
- Critical alerts
- Universal reach
- Legacy devices
SLA
<1s
fallback switch
Enterprise-grade reliability with 24/7 support, dedicated routing, and transparent status reporting.
Common questions
When does fallback trigger?
Whenever a recipient's device or carrier does not support RCS at send time.
Do I write separate SMS logic?
No — enable fallback once and rich content is mapped to SMS automatically.
More RCS products
Every Conversa product shares the same API, dashboard, and billing.
Ready to launch SMS Fallback?
Get API keys in minutes. Pay only for what you use.