Back to Blog

The 2019 Walls Still Standing: Why RCS Enterprise Adoption Is a Go-To-Market Problem

· Jenny

The 2019 Walls Still Standing: Why RCS Enterprise Adoption Is a Go-To-Market Problem

Published: April 8, 2026

RCS has more momentum than ever.

GSMA UP 4.0 shipped. iOS supports cross-platform E2E encryption. Google ships RCS API updates monthly. Infobip shows 3x RCS growth. Bandwidth reports 26% of brands already on RCS, with twice that preparing to follow.

Yet MobileSquared's MWC26 debrief (March 2026) — based on 40+ conversations with the RCS ecosystem — slashed enterprise traffic projections. Not because the technology failed. Because the same walls brands hit in 2019 are still standing in 2026.

The RCS industry solved the technology problem. It never solved the go-to-market problem.

What the MWC26 Data Actually Said

Let's be specific about what the field research revealed:

Geographic inconsistency:

  • France showing strong RCS growth
  • UK, Germany, Spain, Mexico, Brazil, India — "anything but spectacular"
  • US enterprises remain SMS-primary, RCS funded from experimental budgets
  • World Cup 2026 RCS boost failed to materialize as catalyst

Market barriers unchanged:

  • Onboarding remains the #1 cited barrier — same as 2019
  • CRM integration complexity cited as second barrier — same as 2019
  • Pricing inconsistency across markets remains unresolved
  • Germany has better RCS pricing alignment than UK or US

The uncomfortable implication: CPaaS investment outpaced enterprise deployment infrastructure. Vendors built the tools. Enterprises haven't adopted at the same pace.

The Four Walls That Never Came Down

Wall 1: Onboarding Fragmentation

Every carrier runs a different RCS approval workflow. There's no industry standard. A brand launching in the UK, Germany, and US faces:

  • Three different approval processes
  • Three different timeline expectations
  • Three different document requirements
  • 60-90 day onboarding as the norm, not the exception

Google's verification document API (April 6, 2026) helps for Google-managed launches. But carrier-managed launches — still a significant portion of enterprise deployments — remain opaque.

Contrast this with A2P 10DLC: standardized carrier registration dramatically reduced SMS onboarding friction. RCS needs the same. It doesn't have it yet.

Wall 2: CRM Integration Complexity

RCS requires deeper CRM integration than SMS:

  • Rich media handling (images, video, carousel cards)
  • Fallback orchestration (what happens when RCS isn't available)
  • Two-way conversation state management
  • Analytics and attribution that don't exist for SMS

Most enterprise CRM teams haven't been briefed on RCS capabilities. IT sees RCS as a marketing campaign. Marketing sees it as an IT project. Neither owns the integration.

Wall 3: Pricing Inconsistency

Google aligned billable events (basic, single, P2A) with domestic SMS pricing — in theory. In practice:

  • Germany has clearer RCS pricing structure
  • UK and US remain murky
  • India TRAI directives add compliance complexity
  • Finance teams can't benchmark RCS ROI against SMS without consistent pricing

Enterprises can't build multi-market budget models when unit economics vary significantly by geography.

Wall 4: Organizational Misalignment

The most underappreciated barrier:

  • Marketing, IT, and Finance each have veto power over RCS adoption
  • None have the full picture to make the decision alone
  • RCS requires cross-functional alignment that most enterprise operating models don't incentivize
  • The brands winning: treat RCS as infrastructure, not as a campaign

What SMS's Own History Predicts About RCS

The A2P 10DLC trajectory tells the RCS story:

2018-2020: SMS A2P faced identical go-to-market barriers. Carriers, brands, and aggregators blamed each other. Growth was slow. Adoption was fragmented.

The inflection point came when:

  • Standardized registration reduced friction (10DLC)
  • ROI data became available (benchmarks for performance)
  • Early adopters published case studies (proof it works)

RCS is tracking similarly — but the timeline is compressed because AI agent integration is accelerating RCS's urgency. The difference is the pace, not the pattern.

What RCS can learn from 10DLC:

  • Single registration portal for multi-carrier approval
  • Published benchmark pricing by market
  • Case study libraries from early adopters
  • IT-Marketing-Finance alignment frameworks

The Brands Actually Winning — And Why

France:

  • Strong carrier support and investment
  • Clearer pricing alignment than other markets
  • Cross-sector RCS adoption (retail, finance, telco)
  • World Cup 2026 drove significant RCS engagement at scale

Germany:

  • Better RCS pricing strategy than UK/US
  • Enterprise financial services leading adoption
  • Regulatory environment conducive to verified messaging

What separates winning markets from stalled ones:

  • Carrier leadership and investment
  • Cross-functional enterprise working groups (not just Marketing)
  • Published success stories that Finance and IT can benchmark

The AI Agent Layer Changes the Stakes

Here's what's new: AI agents on RCS create a new category of enterprise urgency.

IT teams now have a reason to care: AI agent deployment requires infrastructure, not just campaign management.

Finance teams have a new ROI lever: Agentic communication reduces operational cost per interaction.

But the go-to-market problem remains: Who's owning the RCS AI agent initiative? Marketing? IT? Neither? The organizational walls don't shift just because the technology gets more exciting.

The risk: Enterprises that treat AI agent RCS as another IT project will hit the same 2019 walls.

The opportunity: Enterprises that build cross-functional RCS AI task forces — with Marketing, IT, and Finance at the table from day one — will move faster than competitors.

The Organizational Infrastructure Your RCS Program Actually Needs

Here's a framework for assessing your organization's RCS readiness:

Marketing readiness:

  • Campaign ROI measurement framework in place
  • CRM integration requirements documented
  • Content creation pipeline for rich media

IT readiness:

  • API integration with chosen CPaaS platform
  • Fallback orchestration and error handling
  • Compliance logging infrastructure

Finance readiness:

  • Pricing model understood and benchmarked
  • ROI projection against SMS and alternative channels
  • Budget allocated for multi-year RCS infrastructure

Cross-functional:

  • Named RCS program owner with authority across Marketing, IT, and Finance
  • Go-to-market timeline agreed across all three functions
  • Success metrics defined and shared

The CPaaS layer is ready. The RCS industry is ready. The question your organization needs to answer is: are you treating RCS as infrastructure — or as a campaign?

Research sources: MobileSquared MWC26 debrief (March 2026), Bandwidth State of Messaging 2026 (26% brands on RCS), Infobip Messaging Trends 2026 (3x growth, 628B interactions), GSMA Universal Profile 4.0, Google RCS API April 2026 releases, India TRAI 2025 directives.