1. Headline & intro
Google’s big plan to make RCS the successor to SMS has been hitting the same wall for years: spam and fraud, especially in India. Now Google is quietly changing strategy. Instead of treating RCS as a pure over‑the‑top (OTT) service, it’s plugging directly into a carrier’s network‑level defences — starting with Bharti Airtel.
This shift matters far beyond India. It signals that if RCS is ever going to rival WhatsApp or iMessage, Google will have to embrace the very telecom gatekeepers it once tried to route around. In this piece, we’ll look at what Google is really after, why Airtel is playing along, and what it means for Europe and global messaging.
2. The news in brief
According to TechCrunch, Bharti Airtel, India’s second‑largest mobile operator with over 463 million subscribers, has partnered with Google to integrate Airtel’s network‑level spam filtering into Google’s RCS messaging in India.
The integration means business RCS traffic sent via Google’s platform will be checked in real time using Airtel’s systems for spam detection, sender verification and enforcement of users’ do‑not‑disturb preferences. Airtel is calling this a “global first” where an operator’s spam controls are wired directly into an OTT RCS implementation.
The move follows years of complaints about RCS spam in India. In 2022, Google even paused business promotions on RCS in the country after heavy criticism. TechCrunch notes that Airtel claims its AI‑driven defences have already blocked tens of billions of spam calls and billions of spam SMS, with a sharp drop in fraud losses on its network. India is a critical market for Google’s messaging ambitions, but it’s also dominated by WhatsApp, with more than 800 million users.
3. Why this matters
The announcement is framed as a technical integration, but strategically it’s an admission: Google cannot fix RCS spam alone.
For Google, the stakes are existential for RCS. The company has pitched RCS as the modern replacement for SMS — richer media, read receipts, better group chats — and claimed more than a billion daily RCS messages in the U.S. last year. But if users in key growth markets associate RCS with relentless promos and fraud, brands and consumers will simply stay on WhatsApp and other apps.
Business messaging is where the money is. A2P (application‑to‑person) traffic — one‑time passwords, ticket confirmations, banking alerts, marketing — is a multi‑billion‑dollar market historically owned by SMS. RCS is Google’s chance to recapture that value, but only if enterprises can trust the channel and consumers don’t mute it en masse.
For Airtel, this is leverage. Operators once feared RCS as a Trojan horse for Google to take over messaging. Airtel’s public line — that it waited until RCS could be routed through its spam filters — is effectively a demand for control. If RCS becomes an A2P channel, the operator wants to sit in the middle: setting policies, satisfying regulators, and potentially monetising premium business traffic and verification.
Winners and losers?
- Users may finally see fewer fake loan offers, investment scams and shady fintech pitches.
- Large, compliant brands gain a more trusted channel; their legitimate RCS campaigns are less likely to be drowned out by junk.
- Aggressive marketers and grey‑area lead‑gen shops will face higher friction and more blocks.
The immediate implication: if this model works in India — arguably the hardest market for spam — other carriers will insist on similar terms. Google’s vision of a uniform, app‑centric RCS experience may give way to a patchwork of operator‑mediated policies.
4. The bigger picture
This move fits into three overlapping trends.
1. AI as a security layer for communications. Airtel touts AI‑led systems that have blocked tens of billions of spam calls and billions of spam SMS. Extending this to RCS is logical: real‑time classification of senders and content, anomaly detection for fraud campaigns, and dynamic enforcement of user preferences. We’ve seen the same arc in email (Gmail’s spam filters) and in call screening on smartphones. Messaging was always going to follow.
2. The pendulum swing back to carriers. A decade ago, OTT apps like WhatsApp and Telegram made operators look like dumb pipes. With RCS, Google tried to modernise carrier messaging, but still kept much of the logic in its own cloud. By wiring RCS into Airtel’s network‑side controls, Google is acknowledging that telecoms still hold crucial signals: SIM lifecycle, call patterns, historical abuse data, and regulatory obligations that OTT players don’t have.
This is historically familiar. When SMS spam exploded, the most effective countermeasures were often operator‑side filters, not handset apps. RCS is repeating that story in a richer, more complex environment.
3. The prelude to a post‑SMS world. Apple has already committed to supporting RCS in iOS, under pressure from users and regulators. Once RCS becomes truly cross‑platform between Android and iPhone, it will be the default fallback when you text a number. If that default is perceived as unsafe or noisy, users will retreat further into walled gardens like WhatsApp, Signal or iMessage.
So this India pilot is about more than local spam. It’s about making sure the future “green bubble vs blue bubble” experience is at least trustworthy enough that users don’t immediately say: “Just message me on WhatsApp.”
5. The European / regional angle
For Europe, the Google–Airtel model raises two big questions: who controls messaging security, and under which rules?
European operators such as Deutsche Telekom, Orange, Vodafone and Telefónica already run spam filters for SMS and calls. Many also support RCS in some form, often through Google’s platform. But GDPR, the ePrivacy Directive and national telecom laws place tighter limits on how traffic data can be analysed and shared than in many other regions.
Network‑level AI spam filtering for RCS would likely be considered a legitimate security measure, but combining operator intelligence with a U.S. tech giant’s platform will attract regulatory scrutiny. Questions that EU data‑protection authorities will ask include:
- What message metadata is shared between the carrier and Google?
- Is content itself inspected, and if so, how is this justified under GDPR?
- How are do‑not‑disturb and marketing consent choices enforced across borders?
At the same time, the Digital Services Act and consumer‑protection rules are pushing platforms to reduce scam and fraud. Regulators can’t demand fewer scams and then oppose every form of automated filtering. Expect a balancing act: pressure to clean up messaging, but also demands for transparency, auditability and strict data‑minimisation.
For European enterprises, a cleaner RCS channel could be attractive as SMS prices rise and email deliverability worsens. Yet in markets like Germany or Austria, where users are highly privacy‑sensitive and entrenched on WhatsApp and Signal, operators will need to prove that RCS isn’t a surveillance back door disguised as anti‑spam.
6. Looking ahead
Several things are likely over the next 12–24 months.
1. India becomes the reference case. If Airtel and Google can demonstrably cut RCS spam — measured by user complaints, reported fraud and engagement with legitimate campaigns — this playbook will be pitched to other Indian operators and then to global carriers. If it fails, RCS business messaging in India could effectively stall.
2. Carriers will demand a seat at the table. Any operator now evaluating RCS has a precedent: Airtel insisted on routing traffic through its own controls, and Google agreed. Expect similar demands from large groups in Europe, the Middle East and Latin America. RCS could become less of a Google‑run layer and more of a federated ecosystem, with each carrier enforcing slightly different rules.
3. Regulatory templates will emerge. India’s long fight against SMS spam, led by its telecom regulator, has already produced detailed frameworks for sender registration and content categories. Europe will eventually need something similar for rich messaging, especially as the Digital Markets Act pushes gatekeepers to support interoperability. If RCS becomes part of that interoperable backbone, anti‑spam mechanisms cannot be an afterthought.
4. New risks will surface. Network‑level AI filters introduce their own problems: false positives that kill legitimate campaigns, opaque decision‑making, potential discrimination against smaller senders, and concentration of power in a few filtering vendors. For encrypted person‑to‑person RCS chats, there is also a debate to be had: how far should metadata‑based detection go before it collides with privacy expectations and the EU AI Act’s requirements for trustworthy systems?
For users and businesses in Europe, the practical advice is simple: watch what happens in India. The dashboards and case studies Google and Airtel publish — or carefully avoid publishing — will shape how your own operator and regulator think about spam in the post‑SMS era.
7. The bottom line
Google’s partnership with Airtel is less about one country’s spam headache and more about redefining who polices the next generation of messaging. If India’s experiment proves that carrier‑level AI can tame RCS abuse without crushing privacy and legitimate traffic, operators and regulators from Berlin to Barcelona will want their own version. If it fails, it’s another warning that trying to rebuild SMS in 2026 might be the wrong battle. The open question for readers: do you trust your telco and Google to sit in the middle of your messages in the name of security?
