Launching Rich Communication Services (RCS) for business messaging is a structured registration and configuration process, not a flip of a feature flag. The launch spans your RCS provider, the RBM network, and every receiver carrier that must register your agent before delivering rich content. This checklist walks the five elements every go-live needs, the operator's sequence — pre-launch, at-launch, post-launch — and the cost, market, and channel-selection decisions that determine where RCS actually earns its place.
The short answer
RCS go-live requires five elements in place: an RCS provider with registered carrier access, an approved business agent with a verified sender profile, registered rich content (template) types, a defined SMS fallback for unsupported destinations, and your tenant's configured consent and channel posture. RCS bills per message like SMS, while WhatsApp bills per conversation category — the decision between them is a channel-selection call by market. A one-day launch is possible; a durable one needs the sequence below.
What RCS for business requires to go live
Five elements hold across providers and markets. Miss one and the launch stalls or silently degrades to SMS.
1. A provider with RCS reach and a registered carrier path. RCS is carrier-delivered, not over-the-top — rich delivery exists only where the destination carriers have registered your agent. Your provider handles registration across receiver networks; where coverage is absent, a fallback is mandatory. Orbit by Devotel runs RCS as one messaging channel on a single account, with the receiver-carrier registration handled by the channel, not by you.
2. An agent — your business's RCS identity. RCS sends through an "agent": the programmatic identity the RBM network presents as your brand, not a raw phone number. Launch requires the agent created in your provider's console, your display name registered, and the brand verified (business verification, not a feature toggle).
3. A verified sender profile recipients trust. The agent needs a display name, brand logo and colors, and verification status — the recipient's trust signal, and the difference between a message that converts and one that reads as spam. The verified sender profile is settled before launch, not after first send.
4. Rich content (template) types registered. Cards, carousels, suggested replies, and suggested actions are structured content types, not free text. In Orbit, template submission and approval are tracked in the channel's template manager — until approval, sends either reject or degrade to plain SMS, often invisible in your message log. Register the content types you intend to use, not every type in the catalog.
5. A defined SMS fallback for RCS-unsupported destinations. RCS reach is still fragmented by carrier and market, even with iOS support broadening it. A fallback strategy — RCS where supported, SMS otherwise, with the downgrade visible in analytics — is part of go-live configuration, not a later refinement. Orbit's channel router evaluates the receiver's channel support at send time and falls back to SMS when RCS is unavailable; the checklist below requires you to define and monitor this explicitly rather than assume it holds.
Compliance note: your consent posture — TCPA quiet-hours windows, GDPR retention, opt-out handling — is configured and owned by your tenant, not by the provider. Orbit exposes the controls; the tenant sets its own posture for its jurisdictions.
Operator's checklist
Pre-launch: agent, identity, templates
- [ ] RCS provider account active; API credentials and sender numbers provisioned.
- [ ] Agent created: display name registered, business verified.
- [ ] Verified sender profile approved: logo, brand colors, verification badge confirmed.
- [ ] Every template you intend to send submitted and approved — first-send failures come from unapproved content types.
- [ ] SMS fallback defined for each destination class (RCS-supported, RCS-unsupported, unknown).
- [ ] Fallback behavior validated on a handset you control.
At-launch: a staged rollout with channel truth
- Stage a small recipient set first — your own numbers in each destination market.
- Watch per-recipient channel selection: RCS vs SMS fallback must be visible, not a blended "delivered" count.
- Keep SMS fallback enabled — disabling it to "force" RCS strands recipients on unsupported networks.
- Stage the rollout by destination country so a market-specific failure surfaces before full traffic hits it.
Post-launch: measure on channel truth, not on blended delivery
- Read rate and rich interaction by destination market, RCS-only — a blended SMS+RCS "delivered" figure hides the fallback rate you need to fix.
- Fallback rate by destination: sustained fallback means the market or handset never registered, and your cost model shifts to SMS fallback for those destinations.
- Template rejection inspection: degraded-to-SMS sends often follow new template submissions; approve the type before scaling volume.
- Treat unrecoverable delivery degradation as a real fallback event: re-verify registration with your provider, not a transient retry — silent fallback degrades ROI invisibly until it is diagnosed.
Cost model: RCS vs SMS, and vs WhatsApp
RCS bills per message, like SMS — rich (carded, carouseled) content follows the same per-message logic with rate differences, while WhatsApp bills per conversation category (marketing, utility, authentication, service) via Meta's pricing. The cost-domain distinction matters: RCS-to-SMS fallback is a same-billing-domain fallback (rate shifts, model unchanged); RCS-to-WhatsApp is a different-domain model shift. Compare against your own destination mix and volume — never a headline rate. On Orbit, RCS fallback to SMS draws on the same account and wallet, so the fallback never strands a message on a billing mismatch. The full comparison is in the RCS vs WhatsApp for business messaging guide.
Selection by market: where RCS earns its place
RCS reach follows receiver market and handset, not your sender's market. The channel wins in markets with carrier RCS support and iOS handsets on RCS-capable carriers; in markets without receiver support, RCS silently falls back to SMS while your analytics still show RCS sent. Verify receiver-side channel support per market before you allocate budget — your own market's support does not guarantee the receiver's. See the RCS glossary entry for the full definition, and evaluate the provider landscape in the Best RCS for Business Providers 2026 guide.
The decision is never RCS alone — channel selection across RCS, SMS, WhatsApp, and email is made per market and per use case, with fallback chains on all of them. SMS remains the destination-universal fallback underneath everything.
Frequently asked questions
Can I launch RCS without SMS fallback?
No — and you should not want to. RCS reach is incomplete by receiver network despite iOS support, and an unsupported recipient without fallback receives nothing. Orbit's channel router falls back to SMS only while fallback is defined; the checklist requires you to define it explicitly. Never disable fallback to "force" RCS.
Should I use RCS or WhatsApp for business messaging?
It is a cost-domain and reach question, not an either/or. RCS bills per message with a sender-verified fallback to SMS; WhatsApp bills per conversation category inside an installed app with a massive base in many markets. The full trade-off is in the RCS vs WhatsApp guide; most businesses use both and select per market.
What does the RCS launch actually require to go live?
Five elements: a provider with receiver-carrier registration, an approved agent with verified sender profile, registered template (rich content) types, a defined SMS fallback, and your tenant's consent posture. The pre-launch checklist above walks each.
How does RCS pricing work vs SMS?
RCS uses the same per-message billing domain as SMS, with rate differences for rich content; fallback to SMS stays in the same billing domain. WhatsApp billing (per conversation category) is a different domain entirely. Compare per your own destination mix.
Is RCS on iPhone yet?
Yes — iOS support has broadened RCS reach well beyond its earlier Android-only footprint. Actual reach still depends on the recipient's carrier and market, which is why fallback remains a launch requirement.
Where do I start an RCS launch on Orbit?
In the dashboard's channel configuration: create the agent, register the verified sender profile, submit templates, and define SMS fallback. The SMS API page covers the messaging API surface RCS and SMS share; the Best RCS for Business Providers 2026 guide compares provider fit if you are still evaluating.
The takeaway
RCS go-live is a chain of registration and configuration steps — provider reach, agent, verified sender, approved templates, defined fallback — not a feature toggle. Run the staged rollout with channel truth (RCS vs fallback visible), measure post-launch on per-market channel selection, and let the cost-domain difference between RCS and WhatsApp drive the channel-selection call per market. The launch is operationally one day; the durable posture above is what makes it stay launched.
Published 23 August 2026.