RCS Test Numbers: How to Verify RCS Support Before You Send

What People Mean by an "RCS Test Number"

The phrase shows up in two very different situations, and mixing them up wastes time:

• A number you send a test message to, so you can see whether RCS features (typing indicators, read receipts, high-resolution images) actually render on the receiving device. This is a device-and-carrier test.
• Checking whether the numbers on your list support RCS at all, before a campaign. This is a reachability question, and you cannot answer it by sending messages one at a time.

Both matter. The first tells you your own setup works. The second tells you whether the 40,000 numbers you're about to message will get a rich card or a plain SMS fallback. This guide covers the manual test first, then the list-checking workflow.

The Free Manual Test (5 Minutes)

If you just need to confirm RCS works between two phones:

1. Open Google Messages on both devices (Android). On iPhone, RCS arrived with iOS 18 and depends on carrier support.
2. Make sure both numbers have RCS/chat enabled: Google Messages → Settings → RCS chats, and confirm the status says "connected."
3. Send a message between the two numbers.
4. Check the signals: typing indicators, read receipts, and the ability to send a full-size photo without an "SMS" label on the thread.

If the thread shows "SMS" or "Text · via SMS," the message fell back. That fallback is the tell — it means at least one side (a device, a carrier, or a region) doesn't support RCS for that route.

What this test can't tell you: anything about numbers other than the two you tested. Carrier RCS support varies by country and operator, so a clean test in the US says nothing about a list with Brazilian or Indian numbers on it.

Why Per-Number Checks Are Necessary

RCS reachability is a property of the route, not of RCS itself. The same phone number can be RCS-ready on one carrier and SMS-only on another. Three things decide the outcome:

• Carrier enablement. Not every operator has turned on RCS, and rollout pace differs by country. India and much of Europe are well covered; some regional carriers lag.
• Device and OS. Android with Google Messages is the safest bet. Samsung phones ship their own messaging app but support RCS. iPhones gained RCS support in iOS 18, still rolling out across carriers.
• Number state. Ported numbers and VoIP ranges complicate the lookup. A number that looks mobile in the numbering plan may route somewhere RCS was never enabled.

Guessing wrong is expensive in both directions. Send rich cards to non-RCS numbers and you pay for a fallback SMS anyway. Suppress numbers that would have worked and you shrink your own campaign.

Checking a Whole List for RCS Capability

For anything beyond a handful of numbers, a capability lookup beats test messages. The RCS number checker classifies each number against route intelligence and returns one of four states:

The workflow is the same as any list job: export numbers with country codes, run a small pilot (500 rows tells you what your split looks like), then run the full file and export each segment separately. A free test tier covers the pilot, and paid runs price $1.5 per 10K numbers — cheap next to the cost of a mis-targeted send.

A Note for Developers

If you're wiring RCS checks into an application rather than running one-off lists, the same capability signal is available through the API. A check posts a phone list and returns per-number RCS status plus the fallback classification:

POST /api/v1/detect
{
  "product": "rcsValid",
  "country": "US",
  "phones": ["+14155550132", "+442071838750"]
}

Typical use: gate the rich-message composer in a campaign builder, so the UI only offers RCS templates for numbers flagged rcs_enabled, and switches everything else to the SMS template automatically.

Common Gotchas

Testing on two flagship phones in one country. That proves nothing about routes elsewhere. If your list is international, spot-check each major country segment — or just run the capability lookup instead of guessing.

Assuming iPhone = no RCS. Out of date. iOS 18 added RCS, but carrier rollout is gradual, so iPhone numbers can go either way. Another reason per-number checks beat device assumptions.

Treating "unknown" as "no." Unknown rows often pass on retry. Suppressing them silently deletes reachable contacts. Keep a retry bucket, same as with any verification workflow.

Forgetting the fallback is fine. An SMS fallback row isn't dead data — it's a row for the plain-text version of your campaign. The goal is routing, not purity.

FAQ

Is there an official RCS test number from Google or the carriers?

No single canonical test number exists. Google's RCS troubleshooting runs between your own numbers, and carriers run their own internal tests. For campaign purposes, the practical "test" is a capability lookup on your real list.

How do I know if a specific number supports RCS?

Send it a message and look for the SMS fallback label — slow and manual. Or run it through the RCS number checker, which returns the route classification without sending anything.

Does RCS work on iPhone?

Since iOS 18, yes — where the carrier has enabled it. Rollout is ongoing, so some iPhone numbers are RCS-capable and some still fall back to SMS.

What happens if I send an RCS message to a non-RCS number?

It falls back to plain SMS in most setups. You still pay message costs, you just lose the rich layout, delivery receipts, and interactivity. That's exactly the gap the fallback segment exists to manage.

How is this different from checking iMessage?

Different ecosystems, similar lookup logic. iMessage capability is tied to Apple ID registration; RCS is tied to carrier routes. If your list mixes iPhones and Androids, the iMessage vs RCS comparison walks through choosing which check to run.

Related pages

• Messaging App Checker — check which messaging apps a number is registered on
• Phone List Cleaning — fix formats and duplicates before any messaging check
• RCS Number Checker — bulk RCS capability screening with a free test tier
• iMessage vs RCS: which verification to use

Check your list for RCS capability →