Quick answer. RCS routing starts with a capability check: before sending, the platform asks the RCS backend whether the destination number can receive RCS. If yes, the message is routed over IP through the backend (Jibe/carrier) to the recipient’s RCS client. If no, or if delivery fails, the message is routed instead as SMS or MMS, so it still arrives. For business messages, routing also enforces the agent’s identity and use-case rules along the way.
This capability-aware routing is what lets an “RCS-first with SMS fallback” program work as a single send: the system picks the best channel per recipient automatically. A good provider exposes the delivered-as-RCS-vs-fallback outcome back to you so you can measure and reconcile.
Key facts
- Routing begins with a capability check (RCS-capable?) per destination.
- RCS-capable → IP delivery via Jibe/carrier; otherwise → SMS/MMS fallback.
- Delivery outcome (RCS vs fallback) is reported back for measurement.