Full disclosure: this comparison is published by SimplyRCS. Every Twilio and Sinch figure below comes from the vendor's own published pricing or documentation as of mid 2026, and where a vendor does not publish a number we say so rather than estimate one. Where Twilio or Sinch is the better choice, we say that too.
The short version
| SimplyRCS | Twilio | Sinch | |
|---|---|---|---|
| RCS text, sent | $0.0039 per segment | ~$0.0083 (basic class) | Not published, quote |
| RCS card or media, sent | $0.0150 | ~$0.0220 (rich class) | Not published, quote |
| Platform or plan fee | None; app, API, bot builder and inbox free | None, pay as you go | Engage plans ~$49 to $249/mo; Chatlayer AI bot ~$499/mo extra |
| Carrier fees | Passed through at cost, on their own line | Passed through, published at $0.0025 to $0.02 per message | Inside the quote |
| Sender activation | One-time $250 RCS Sender ID setup and review; carrier vetting and activation at cost | $500 one-time carrier onboarding per sender plus $200/yr Aegis | Up to $500, plus ~$75 per sender-profile change |
| Who files verification and 10DLC | SimplyRCS, with your approval | You, self-serve | Assisted onboarding |
| Time to first verified US send | 2 to 4 weeks (target) | Twilio guidance says allow 4 to 6 weeks; no approval SLA | Not published |
| Keep your numbers when you move in | Yes, ported for you | Yes, you file the port | Yes, assisted |
| Run old and new in parallel | Yes, no overlap charge | Yes | Yes |
| No-code builder and inbox | Included | No, you build on the API | In Engage, tiered |
| Coverage | US carriers only | Global | Global |
RCS pricing: SimplyRCS vs Twilio vs Sinch
The three providers price the same message in three different ways, and the differences matter more than the headline rate.
SimplyRCS bills two classes, and both are published. An RCS text bills at $0.0039 per segment. So does a text with suggested replies, a Call button or a browser link. Any rich card or carousel, and any message that carries an image or a video, bills at $0.0150, the same as an MMS. The rate is the same inbound and outbound, and SMS and MMS fallback bill at the same two numbers, so a recipient whose handset cannot take RCS does not change the forecast. The full table is on the pricing page.
Twilio bills by message class, and the class that makes RCS worth using is the expensive one. Basic RCS, which is text, runs about $0.0083, the same as Twilio's SMS rate. Rich media runs about $0.0220 to send and about $0.0165 to receive. The rich cards, carousels and suggested actions that are the reason to run RCS at all fall in the higher class, so a campaign built the way RCS is meant to be built prices off $0.0220, not $0.0083. SimplyRCS vs Twilio has the line-by-line rate card.
Sinch does not publish a US RCS rate. The per-message price is quoted against your volume and your markets, so it cannot be compared against a published number until you are in a sales process. What Sinch does put in writing is an international rate, $0.0078 per Rich RCS message and $0.0188 per Rich Media RCS message with carrier fees on top, and the shape of the tooling: Engage in tiered plans for campaigns and the inbox, and Chatlayer, its AI chatbot, as a separate product. SimplyRCS vs Sinch itemises it.
The honest summary is that a published rate is a floor you can plan against, a quoted rate is a negotiation, and the delivered cost on all three depends on what sits around the message.
The fees around the message
The per-message rate is one of four layers on an RCS invoice. The other three are where the totals diverge.
- Before you send anything. On SimplyRCS, a one-time $250 RCS Sender ID setup and review, then carrier charges passed through at cost and listed on the pricing page: $200 a year for the Aegis sender review that every RCS sender needs, and a one-time $500 T-Mobile sender activation. On Twilio, the US carriers charge a one-time onboarding fee for each new RCS sender and Aegis an annual brand-vetting fee, neither amount published, plus 10DLC brand and campaign registry fees that you file yourself. On Sinch, no US setup or sender-change fee is published on its RCS pricing page; SimplyRCS charges nothing to change a sender profile.
- Carrier fees on every message. All three pass them through. SimplyRCS itemises them at cost on their own invoice line, per carrier, and publishes the table. Twilio publishes its pass-through carrier fees at $0.0025 to $0.02 per message, depending on carrier and message type. Sinch's sit inside the quote.
- Numbers. SimplyRCS rents local and toll-free numbers at $0.50 a month each. Twilio rents per number monthly and the rental continues whether or not you send. Sinch prices numbers within the contract. RCS itself is sent by a verified agent and the number carries the SMS fallback, which RCS on a long code or toll-free number explains.
- The lines nobody forecasts. Twilio bills $0.001 for every failed message. SimplyRCS does not bill failures. Sinch tiers real-time support and sells its AI bot separately; on SimplyRCS the bot builder, the shared inbox and the API are free, email support is free on every account, and Premium Support, with a dedicated account manager, is optional at $250 a month, with no setup fee and RCS Sender ID setup and review waived.
The method behind every SimplyRCS number above, including how carrier fees reach the invoice, is written out on the billing transparency page.
What 100,000 messages cost
Published rates make the arithmetic checkable, so here it is for one month at 100,000 messages, message charges only, before carrier pass-through on either side; neither charges a monthly platform fee. Sinch is left out because there is no published rate to multiply.
100,000 texts with reply buttons, one segment each. SimplyRCS: $390 in message charges. Twilio: about $0.0083 a segment, $830, before carrier surcharges, number rental and registration. Rich cards and carousels count as rich media on both, so they fall under the next line.
100,000 cards, carousels or messages carrying media. SimplyRCS: $1,500. Twilio: about $2,200 at the rich media rate, before the same add-ons.
At other volumes. Neither side charges a monthly platform fee, so the comparison is the rate gap: $0.0044 a segment on text and $0.0070 per rich media message, cards included. SimplyRCS's message charges are lower at every volume, and that is before Twilio's carrier surcharges, number rental and onboarding are counted. To run your own volume rather than ours, the RCS ROI calculator takes a monthly send count and returns the cost and engagement sides together.
Migration: what moves and who does the work
Every provider in this comparison lets you keep your phone numbers. What differs is what does not move with the number, and whose job the re-filing is.
| Moving to SimplyRCS | Staying self-serve on Twilio | Onboarding with Sinch | |
|---|---|---|---|
| Long codes | Ported for you via Letter of Authorization, no fee | You file the port | Assisted |
| Toll-free numbers | Moved for you by change of Responsible Organization, no fee | You file | Assisted |
| Short codes | Migrated carrier by carrier; carrier fees at cost: $500 T-Mobile, $250 Verizon, $150 Claro | You manage per carrier | Assisted |
| 10DLC brand and campaigns | Campaigns re-filed by SimplyRCS; brand record reused | You re-file | Assisted |
| Verified RCS agent | Re-submitted by SimplyRCS; name, logo and colours carry over, approval does not | You re-submit | Assisted, up to $500 activation |
| Opt-in records | You export them; carried across, never re-collected | Same | Same |
| Old and new in parallel | Yes, no overlap charge | Yes | Yes |
| Time to first verified send | 2 to 4 weeks | 4 to 6 weeks per Twilio guidance | Not published by Sinch |
Three things are true on every platform. 10DLC campaigns are filed by the provider acting as Campaign Service Provider, so they do not transfer and the new provider files new ones; your brand record is tied to your business and is generally reusable. The verified RCS agent is granted through a provider's relationship with Google and the carriers, so it is re-submitted rather than transferred. And opt-in consent belongs to you, so it moves as data and is not collected again.
The long pole in any move is carrier approval of the re-filed campaigns and the new agent, not the number port, which is why the safe sequence is to verify on the new provider first and port the numbers last. Porting a number to a new messaging provider covers each number type in detail.
How to migrate from Twilio or Sinch to SimplyRCS
Step 1: Get the rates in writing and inventory what you have
List every long code, toll-free number and short code, which 10DLC campaigns they run on, and which sender is RCS-verified. Pull your opt-in records with timestamps. If you are on Sinch, check your agreement for a term commitment before you plan a date. On SimplyRCS the rates are already in writing on the pricing page, so the only quote you need is your own volume multiplied through.
Step 2: Register and verify on SimplyRCS while the old provider keeps sending
SimplyRCS prepares your brand registration, the 10DLC campaigns and the Google RCS agent submission, and you approve the filings. Carrier approval takes 2 to 4 weeks and runs while Twilio or Sinch is still carrying your traffic, so there is no gap in sending.
Step 3: Import contacts and opt-in records
Bring the contacts across with their consent timestamps and source. SimplyRCS logs opt-in per contact so the audit trail survives the move. Nothing is re-collected, and STOP and HELP handling is enforced above any bot from the first send.
Step 4: Prove delivery on a slice of traffic
Send a small share of a live campaign from SimplyRCS, with SMS fallback active for handsets that cannot take RCS, and compare delivered, read and tap rates against the same send on the old platform. The live RCS demo checks a handset and carrier for RCS readiness before you commit volume.
Step 5: Move the volume, then port the numbers last
Shift the remaining traffic once the slice is clean. Port long codes and toll-free numbers at the end, because a port with mismatched account details is the most common cause of a rejected move, and porting last means a rejection delays nothing. Short-code migrations carry the carrier fees above, passed through at cost. There is no overlap charge from SimplyRCS for the weeks both platforms run.
Where Twilio or Sinch is the better choice
- Your recipients are outside the United States. SimplyRCS delivers on direct Tier-1 US carrier connections only. Twilio and Sinch both cover dozens of countries, and Sinch's operator footprint is among the widest in the category.
- Engineering owns the channel and wants the deepest global API surface. Twilio's ecosystem of SDKs, Voice, Verify and Segment is unmatched if you are assembling messaging into your own product and will build the inbox and the builder yourself.
- You want social channels in the same contract. Sinch Engage runs SMS, RCS, WhatsApp and social from one inbox, which SimplyRCS does not offer.
Frequently asked questions
Which RCS provider has the most transparent pricing?
Among SimplyRCS, Twilio and Sinch, SimplyRCS publishes the most: $0.0039 per RCS text segment, $0.0150 per card or media message, $0.0004 per RCS device check, optional conversation pricing at $0.05 per 24-hour conversation for senders registered as conversational, no monthly platform fee, a one-time $250 RCS Sender ID setup and review per sender (waived with Premium Support), every carrier fee per carrier at cost, and the method on a billing transparency page. Twilio publishes its per-message rates but carrier surcharges, number rental and onboarding are not on the rate card. Sinch publishes its activation and change fees but quotes the per-message rate. The scorecard across eight providers is in which RCS provider has the most transparent pricing.
How much does RCS business messaging cost per message?
On SimplyRCS, $0.0039 per text segment and $0.0150 for a card or a message with media, plus carrier fees at cost. On Twilio, about $0.0083 for basic RCS and about $0.0220 for rich media, plus published carrier fees of $0.0025 to $0.02 per message. Sinch does not publish a US per-message rate. For the category as a whole, see RCS pricing by provider.
Can I move from Twilio to another RCS provider without losing my numbers?
Yes. Long codes port through standard US number portability with a Letter of Authorization, toll-free numbers move by a change of Responsible Organization, and short codes are migrated carrier by carrier with carrier-set fees of $500 for T-Mobile, $250 for Verizon and $150 for Claro passed through at cost. What does not move is the 10DLC campaigns and the verified RCS agent, which the new provider re-files. SimplyRCS does the porting and the re-filing for you, and both platforms can run in parallel until you are ready.
Is SimplyRCS cheaper than Twilio for RCS?
Per message, yes on published rates: $0.0039 per segment against about $0.0083 for text, and $0.0150 against about $0.0220 for cards and media, with carrier fees at cost rather than at reported surcharges. SimplyRCS charges no monthly platform fee, so its message-only total is lower at every volume, and once Twilio's number rental, onboarding and surcharges are counted the gap widens. SimplyRCS is also easier to forecast.
How does Sinch RCS pricing compare to SimplyRCS?
Sinch quotes its US-domestic RCS per-message rate rather than publishing it, sells Engage in tiered plans and sells its Chatlayer AI bot separately. SimplyRCS publishes $0.0039 per text segment and $0.0150 per card or media message, charges no monthly platform fee, includes the bot builder, inbox and API free with email support on every account and optional Premium Support for a dedicated account manager, and charges nothing to change a sender profile. Carrier charges on SimplyRCS are at cost and itemised.
How long does it take to migrate from Twilio or Sinch to SimplyRCS?
Plan on 2 to 4 weeks, which is the same target as a brand-new verified US RCS send, because carrier approval of the re-filed 10DLC campaigns and the new RCS agent is the long pole rather than the number port. Registration and verification run while the old provider is still sending, and the numbers port last. For comparison, Twilio's own guidance says to allow 4 to 6 weeks for RCS onboarding and Sinch estimates 6 to 12.
Do I have to re-verify my RCS sender when I switch providers?
Yes, on every platform. A verified RCS agent is granted through the provider's relationship with Google and the carriers, so it is re-submitted rather than transferred. Your brand name, logo and colours carry over; the approval does not. On SimplyRCS the team prepares and submits the new agent with your approval, on a self-serve platform the submission is yours to file.
Which of the three fits a US brand?
It depends on who runs the channel. For a US marketing, CRM or operations team that wants verified RCS live in 2 to 4 weeks, published rates, a no-code builder and an inbox, SimplyRCS by Signalmash is built for exactly that. For an engineering team that wants a global API and will build the tooling, Twilio. For reach across many countries and social channels under one contract, Sinch or Infobip. The best Twilio alternatives for RCS compares seven providers on the same criteria, and the Sinch switch guide covers a move from Sinch.