If you've been asked to "add RCS" to a product, you've probably found that it isn't a single API you sign up for. RCS business messaging is a set of carrier and handset capabilities reached through an aggregator, and each step has its own approvals. This post is for the developer who has to scope the work and wants to avoid a surprise in week three.
We'll be straight about where Ready stands: Ready sends SMS and iMessage (the blue line). It doesn't send RCS. So this isn't a pitch for an RCS product. It's a planning guide, and the planning advice is to build the reliable path first and treat RCS as an upgrade you bolt on later. For the non-technical overview, see our RCS business messaging guide.
What an RCS business API actually is
RCS is a messaging standard on Android phones, with support growing on iPhones. For businesses, it adds things plain SMS can't: a verified sender with a logo, rich cards, buttons, and delivery and read signals. The sender is called an agent, and the agent is registered and approved before it can message anyone.
From the developer side, that gives you four moving parts:
- An agent. The branded sender identity, reviewed by carriers or an intermediary before launch.
- An aggregator or provider. The API you call. You rarely talk to carriers directly.
- A capability check. Before sending, you ask whether the recipient's device and carrier support RCS.
- A fallback. What happens when they don't, which is most of the time you'll worry about.
The capability check is the part people underestimate. You can't assume a given US phone can receive an RCS message from a business today, so every send needs a plan B.
The planning checklist
Before you write any code, get answers to these.
| Question | Why it matters |
|---|---|
| Who approves the agent, and how long does it take? | Launch dates depend on it |
| Does the approval cover each of my customers, or just me? | Platforms need one agent per brand in many setups |
| How does the capability check work, and does it cost anything? | It runs before every send |
| What does fallback to SMS look like in the API? | Silent fallback and explicit fallback behave very differently |
| How are opt-outs shared between RCS and SMS? | A STOP on one channel must hold on the other |
| What are the message types and size limits? | Rich cards have shape rules |
| How is billing structured? | Rich messages and basic ones can price differently |
If you're a platform, the second row is the hardest. A single branded agent for your own product is manageable. An agent for each of your customers resembles carrier registration all over again, with its own review.
Design for the fallback first
Whatever RCS provider you choose, structure your code so the channel is a detail. A sensible shape:
- Your app creates a message for a contact with a body and an optional rich payload.
- A router picks the best channel for that contact.
- If the preferred channel refuses or can't deliver, the router tries the next one.
- Opt-outs and quiet hours are checked before any channel, not inside one.
Number four is where teams slip. Compliance rules attach to the person, not to the channel. A person who texted STOP shouldn't get an RCS message the next day because the opt-out lived inside the SMS code path. We cover the shared-opt-out problem in the RCS fallback and benefits post.
Keep your message content useful as plain text too. A rich card with three buttons has to degrade into a sentence and a link. If the text version is confusing, your fallback is where most of your real traffic will land, and it'll look bad.
The reliable path today: SMS, plus iMessage where it fits
For most US platforms, the dependable channel is registered SMS. It reaches every phone, it's well understood, and registration (10DLC) gives you a defined route for business traffic. On top of that, a blue line sends as iMessage, which shows up blue on iPhones with the business's name and photo.
On Ready, both go through one API. A first send is:
POST https://api.tryready.com/v1/messages
{"to": "+12125550199", "body": "Your order #1042 has shipped.", "consent_attested": true} With from set to your account's own iMessage line, the same endpoint sends through that line. If the contact isn't on iMessage, you get a refusal with fallback: sms, nothing is sent, and you resend without the line as from. That explicit refusal is the kind of behavior to ask any RCS provider about too, because silent fallbacks can double-send or bill you for both attempts.
A few blue line facts for planning: it needs no 10DLC registration, it costs $99 a month per line plus 6 cents a segment, each line can start a limited number of new conversations a day, and campaigns send from regular numbers rather than the blue line. Android recipients get SMS from your regular number. The details are in the iMessage docs, and the iMessage API guide explains how it differs from Apple Messages for Business.
For the regular SMS side, Standard is $0.0075 per segment plus a $0.0045 carrier fee, $0.012 all-in, not counting screening. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.
Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.
A sensible rollout plan
Here's the order we'd build in if the ask is "get ready for RCS."
- Ship registered SMS with per-customer registration, opt-outs and quiet hours handled. This is the baseline everything falls back to.
- Add iMessage where your customers' contacts skew toward iPhones and you want a richer look without a new approval process.
- Abstract the channel in your own code, so a new channel is a new adapter, not a rewrite.
- Pilot RCS with one brand that's worth the agent approval, behind a feature flag, measuring against SMS.
- Decide from your data whether to widen it.
We don't quote delivery or engagement lifts for RCS, because we haven't measured them and published numbers vary by source. Measure yours.
FAQ
Does Ready support RCS?
No. Ready sends SMS and iMessage. If RCS matters to you, plan it as a separate adapter and keep Ready or another registered SMS path as the fallback.
Is RCS replacing SMS?
Not in a way you can plan around today. SMS still reaches every phone, and RCS depends on handset, carrier and agent approval. See SMS vs RCS: what to adopt now.
Do I still need 10DLC if I add RCS?
Yes for your SMS traffic. RCS has its own approvals, but your fallback texts still travel on registered numbers.
Where do I read more on iPhone and Android differences?
iMessage and RCS on Android: compatibility covers who can see what.
Next step
Before you evaluate an RCS provider, get your SMS path in order: registration per customer, shared opt-outs and a router you control. Then the RCS question becomes a small adapter decision. The API quickstart shows a first send, and the iMessage API reference covers the blue line.