RCS reachability: how do you check which numbers can actually receive RCS before a campaign?
RCS is finally real for most of the market - Apple enabled it in iOS 18, Google has been pushing RCS for years, and carriers/CPaaS platforms now offer it as a standard route. The catch: RCS only works when the recipient's device, OS, and carrier all support it.
That makes planning an RCS campaign different from planning an SMS campaign in one important way. With SMS you mostly care whether the number is a valid, active mobile number. With RCS you also need to know whether that specific line actually supports RCS - otherwise your message silently falls back to SMS or fails to deliver at all.
Four questions worth answering before you route an RCS blast:
1. Syntax/format - is the number even in valid E.164 form? (junk rows fail here first)
2. Line type - is it mobile, or landline/VoIP/premium? RCS targets mobile lines.
3. Portability - MNP moves numbers between carriers; the carrier serving a number today may not be the one that issued it.
4. RCS support/registration - is the line actually provisioned for RCS messaging on its current network?
The first three are the same checks you would run for any SMS campaign. The fourth is RCS-specific, and it is the one that decides whether you build an RCS flow, an SMS flow, or a hybrid with proper fallback.
Practical approach: run the list through a preflight before the campaign - normalize formats, drop landline/VoIP rows, confirm line type, and check the RCS signal per number. Then segment: RCS-capable / SMS-only / invalid, and route each segment through the right channel. A list where most numbers are RCS-capable tells you something very different from a list where only a fraction is.
If you are cleaning or verifying phone datasets before a campaign, you can check the available verification workflows at
- but the key habit is the same regardless of tooling: check channel capability before you pay to send on it.
What do you all use when a customer asks "can we RCS these numbers?" - carrier DB lookups, device fingerprinting, or trial sends?
Replies
No replies yet.
Please login to post a reply.