Move from channel-based messaging to intelligent messaging orchestration—start single-channel today, add fallback tomorrow, and scale without rewrites.
Most teams begin with a single channel—typically SMS, WhatsApp, or RCS—and build workflows around it. As requirements evolve, you need faster OTPs, richer engagement, higher reliability, and smarter cost controls. That’s when multi-channel integrations and DIY fallback logic start to add complexity. EnableX Unified Messaging API gives you a single endpoint across SMS, WhatsApp, and RCS—while still letting you use just one channel until you’re ready to expand. Explore the API.
Key advantages: One endpoint, unified message ID, single webhook, built-in fallback, and smart routing modes (order, budget, priority).
Why migrate to Unified Messaging?
- Eliminate integration sprawl: move from multiple endpoints, payloads, and webhooks to one.
- Keep it simple: continue with a single channel exactly as you do today; no behavior change required.
- Future-ready: enable fallback or smart routing later with a small payload change—no new infrastructure.
Why moving to RCS inside an omnichannel strategy matters.
Step 1 — Replace your Send endpoint
Example: Migrating from SMS Send API → Unified Messaging
Before — SMS API
POST /sms/v1/messages
{
"from": "ENXOTP",
"to": "+919999999999",
"data": {
"text": "Your OTP is 1234"
}
}
After — Unified Messaging API (single-channel SMS)
POST /messaging/v1/messages
{
"to": "+919999999999",
"channels": ["sms"],
"preference": "order",
"sms": {
"from": "ENXOTP",
"data": {
"text": "Your OTP is 1234"
}
}
}That’s it—you’re on Unified Messaging with no behavior changes and no routing changes.
Step 2 — Migrate WhatsApp Messaging
Template message example
Before — WhatsApp Messages API
{
"to": "+919999999999",
"type": "template",
"template": {
"language": { "code": "en" },
"name": "order_update"
}
}After — Unified Messaging (single-channel WhatsApp)
{
"to": "+919999999999",
"channels": ["whatsapp"],
"whatsapp": {
"type": "template",
"template": {
"language": { "code": "en" },
"name": "order_update"
}
}
}
Step 3 — Migrate RCS Messaging
Before — RCS API
POST /rcs/v1/messages
{
"phone": "+919999999999",
"type": "text",
"agent": "brand_agent",
"fallback_text": "Order confirmed"
}After — Unified Messaging (single-channel RCS)
{
"to": "+919999999999",
"channels": ["rcs"],
"rcs": {
"type": "text",
"agent": "brand_agent",
"fallback_text": "Order confirmed"
}
}
Prefer single channel? Keep it that way.
Unified Messaging lets you continue with “channels”: [“sms”] or “channels”: [“whatsapp”] and gain unified tracking plus a single webhook—no change in behavior.
Step 4 — Add automatic fallback later (one small change)
Turn on failover from WhatsApp → SMS
From
"channels": ["whatsapp"]To
"channels": ["whatsapp", "sms"]Unified Messaging will try WhatsApp first and automatically fallback to SMS if needed—no retry scripts or monitoring code required.
Step 5 — Enable Smart Routing
Choose routing modes that fit your use case: order, budget, or priority. For OTPs and critical alerts, priority selects the most reliable, fast-performing channel.
Unsupported keys & payload differences
Unified Messaging stays close to original channel payloads, but some channel‑specific keys are intentionally excluded to maintain a consistent model. Review the “Unsupported objects/keys” section before migrating.
Docs: Unified Messaging API • SMS API • WhatsApp API • RCS API
Migration Checklist
Planning a shift from SMS to RCS? Start with this readiness guide: 8 questions to ask before you shift.
- Change endpoint to /messaging/v1/messages (from channel-specific endpoints).
- Wrap payload: add channels and the channel object (sms / whatsapp / rcs).
- Store unified message_id for tracking.
- Update webhook to a single Unified Messaging webhook (replace multiple channel webhooks).
Start migrating today
Move from channel-based messaging to intelligent orchestration—at your own pace.
