A brand selling into Brazil usually hits the same wall around its second year of messaging. SMS still delivers, but click-through has flattened and every promotional text competes with fraud messages that have taught Brazilians to distrust unknown senders. WhatsApp converts, but its per-message fees make every campaign a budget discussion. Meanwhile, most of that brand's customers carry Android phones with RCS already switched on, and nobody has tested it.
That gap is what makes RCS in Brazil worth a serious look right now. Brazil was the first market where every major carrier launched RCS Business Messaging together, and iPhone support is live on two of the three operators with the third in testing. This article covers how carriers and coverage for RCS in Brazil actually work, where RCS beats SMS on this market, and how to launch without losing the reach SMS gives you today.
Three structural facts shape RCS in Brazil, and none of them apply to the markets most RCS guides are written about. First, Brazil is Android country: Android holds 75.45% of mobile OS usage against 24.54% for iOS (StatCounter, 2026). In the US the ratio is reversed, which is why so much RCS commentary obsesses over Apple.
Second, the carriers moved early and together. Oi turned on RCS in January 2019, Vivo and Claro followed that year, and in August 2020 all four launched Rich Business Messaging commercially with Google, the first coordinated launch of its kind (TELETIME, 2020). All of them run on Google's Jibe platform, so there is one technical standard rather than a patchwork of carrier-specific setups.
Third, the commercial channel is already mature. Google's Brazil team has described the country as the largest RCS market in the world by revenue, second only to India in volume, with around 4.7 billion RCS messages per month (Mobile Time, 2025). By mid-2026 roughly 1,000 companies, mostly large enterprises such as Casas Bahia, iFood and Bradesco, were using the channel (Mobile Time, 2026). The channel is familiar to the recipient, which is not true of RCS in most European markets.
The one thing that does look like the rest of Latin America is WhatsApp. It is the default conversational app for the country, and any RCS Brazil strategy has to be built around that fact rather than against it. RCS Business Messaging, the A2P version of the protocol, wins where a brand needs verified identity, rich content and read-level reporting in the native inbox. Consent rules are the same on both channels: Google requires informed opt-in for promotional RCS and an easy opt-out, so RCS is not a way around consent the brand does not have. Nor does it replace WhatsApp for two-way customer service.
Brazil's mobile market is concentrated in three operators, and that concentration is what makes RCS coverage in Brazil predictable. Vivo leads with 37.9% market share, Claro holds 33.2% and TIM 22.4% of a base of 276.4 million mobile accesses (Anatel, 2026). In 5,452 municipalities these three carriers hold between 90% and 100% of the mobile market. Here is where each stood on RCS at the time of writing.
| Carrier | Mobile market share (Anatel, Q2 2026) | RCS on Android | RCS on iPhone |
|---|---|---|---|
| Vivo (Telefônica) | 37.9% | Live since 2019; business RCS since August 2020 | Supported on compatible iPhones since iOS 26 (September 2025) |
| Claro (América Móvil) | 33.2% | Live since 2019; business RCS since August 2020 | In testing: enabled in the iOS 27 beta (August 2026); general availability to be confirmed |
| TIM | 22.4% | Live since 2020; business RCS since August 2020 | Supported on compatible iPhones since iOS 26.2 (late 2025) |
Vivo and TIM support RCS on compatible iPhones. Claro began testing support in the iOS 27 beta in August 2026, and general availability should be confirmed before you plan an iPhone-heavy campaign on that network (iHelp BR, 2026). In device terms, Google's Brazil team put the RCS-enabled base at 145 million active users in mid-2026, up 10 million from the end of 2025 (Mobile Time, 2026).
Two caveats keep that number honest. Carrier market share is not RCS reach: whether a contact can receive RCS depends on the handset, OS version, carrier and user settings, and only a capability check on your own base gives the real figure. And RCS on Android needs version 8 or later with an active data connection, so older entry-level handsets fall outside it. That is why we treat any RCS Brazil campaign as an RCS-plus-SMS campaign, never an RCS-only one.
The RCS versus SMS question in Brazil is less about media and more about trust. Brazilians have spent years being targeted by SMS scams, the so-called golpes, and the default response to an unrecognised text is deletion. RCS in Brazil changes the trust signal at the protocol level. A message arrives from a verified sender profile with the brand's name, logo and a verification badge, the "selo azul" that Google and the carriers built into the Brazilian launch specifically as an anti-fraud measure (Telesíntese, 2020).
Here is how the two channels compare for a brand operating on the Brazilian market.
| Criterion | SMS in Brazil | RCS in Brazil |
|---|---|---|
| Reach | Every active mobile line, including feature phones | Android 8+ with data, plus iPhone on Vivo and TIM (Claro in testing) |
| Sender identity | Short code or alphanumeric ID; easy to spoof | Verified brand agent with name, logo and badge |
| Content | 160 characters of text, links only | Images, carousels, buttons, suggested replies, PDFs |
| Delivery visibility | Delivered or not delivered (DLR) | Delivered, read, clicked, replied |
| Consumer data cost | None | None; carriers committed at launch not to charge subscribers for RCS traffic |
| Best fit | OTP, alerts, fallback, older handsets | Promotions, billing, order tracking, two-way flows |
Read and click visibility is the operational difference most teams underestimate. With SMS you know a message was delivered; with RCS you know whether it was read and which button was tapped. In our experience working with retail and fintech clients in Latin America, this reporting alone changes how teams budget: they move from "SMS is cheap, so we send more" to "RCS tells us what worked, so we send less."
The honest tradeoff is per-message cost. An RCS message costs more than a plain A2P SMS, and that gap only pays back on messages that need a click, a reply or a visual. So the practical answer for RCS vs SMS in Brazil is "RCS where the message earns it, SMS everywhere else", the same logic we set out in our RCS vs SMS channel guide.
The RCS use cases that work in Brazil map onto local payment and shopping habits, not the generic "send a product image" demo. The clearest public benchmark is Casas Bahia, which used RCS to push its Carnê Digital instalment product and reported 1.6x more conversions and 6.2x higher ROI than another conversational channel, plus an 8% increase in orders and a 17% rise in sales revenue (Google RCS for Business, 2025). Leroy Merlin Brasil reported a 220% ROI on its first RCS campaign, with 66% of users choosing buttons and suggestion chips over typed replies, according to its solution provider (IT Forum, 2026). Both sold something that needs a guided flow rather than a link.
Collections and billing is the standout beyond retail. Brazil runs on boletos and Pix, and a rich card with the invoice amount, a "copy Pix code" button and a "view boleto" PDF removes the two steps where people drop out of a payment reminder: finding the code and switching apps. An SMS can only carry a link, which is exactly what Brazilians have learned not to tap.
Order tracking and appointments work on the same principle: a "reschedule delivery" button instead of a tracking code pasted into a text, or a clinic confirmation where one tap replaces a phone call. What our clients have found is that sequencing matters more than creative: promotional and billing flows earn the RCS cost, while OTPs and plain confirmations stay on SMS. Splitting traffic that way, rather than migrating everything at once, is the pattern we recommend by default.
Launching RCS in Brazil has three moving parts: an approved agent, knowing which numbers can receive RCS, and deciding what happens when they cannot. Get the third wrong and the campaign quietly loses a slice of its audience.
The RCS agent is the brand's verified identity on the channel. It is created through a Google-authorised partner with the brand's name, logo, description and use case, and approved before it can send to Brazilian numbers. Approval time depends on the launch model: a Google-managed launch can complete within a few business days once requirements are met, while carrier-managed reviews take longer. Keep the use-case description honest either way: agents registered for transactional traffic and then used for promotions get flagged.
Before every send, an RCS capability check tells the platform whether a given number can receive RCS right now. The result depends on the handset, OS version, carrier and whether the user has data, and a number that passed last week can fail today because RCS was switched off in settings. This check is what makes cascade routing possible: the platform tries RCS first and falls back to SMS within the same send, with the SMS version of the message pre-written rather than auto-truncated.
Here is the contrast we see in practice. A brand that sends RCS-only to a 500,000-contact base in Brazil reaches the RCS-capable share, silently drops the rest, then reads the campaign as underperforming. With an RCS-to-Bulk SMS cascade the same brand reaches the whole base and reports rich engagement and standard delivery separately. At BSG, we built SMS fallback into cascade routing for RCS from day one for this reason; the setup is described on the RCS for Business page.
Compliance is the last piece. Brazil's LGPD governs consent for marketing messages, and Google's RCS policies add the same requirements: documented opt-in, a clear sender identity and an easy opt-out, which RCS handles natively through a suggested reply. If you are still building the internal case for RCS in Brazil, our guide to building a business case for RCS walks through the cost and conversion assumptions to put in front of finance.
If you already run SMS or WhatsApp campaigns in Brazil and want to see what a verified RCS agent with SMS fallback does to your read and click rates, we have run this setup for retail, fintech and logistics clients across Latin America. We can register the agent, run a capability check on a sample of your base to show your real RCS reach in Brazil, and configure the RCS-to-SMS cascade so the first campaign is measured against your current numbers. Talk to our team and we will start from your existing contact list, not a demo.
Partly. Vivo and TIM support RCS on compatible iPhones, Vivo since iOS 26 in September 2025 and TIM since iOS 26.2. Claro began testing support in the iOS 27 beta in August 2026, so general availability on that network should be confirmed before launch. Coverage also depends on an updated iOS and RCS being switched on in settings.
Vivo, Claro and TIM all support RCS Business Messaging on Android and have done so since the joint commercial launch with Google in August 2020. Oi, which was part of that launch, no longer sells mobile plans. Together the three carriers hold over 90% of the Brazilian mobile market, but actual RCS reach for a given base still has to be measured with a capability check.
It depends on the setup. Meta charges per delivered business message, with rates varying by message category and market, while RCS commercial terms depend on the provider, traffic type and campaign setup. Google has positioned RCS in Brazil as a lower-cost option for outbound campaigns, but the right comparison is cost per conversion, not cost per message.