Skip to main content
Back to blog

RCS Pricing in 2026: From Carrier Enablement to Per-Message Verified-Agent Billing, Explained

Google Jibe and the GSMA-tier carriers activated per-message RCS billing on the verified-agent path in late 2025, making RCS cost like SMS premium on delivered traffic. This explainer covers what changed, what template mix does to the bill, and which tenant-owned controls decide what you actually pay.

Orbit Editorial Team

Quick answer: Through late 2025, the monetizable layer of RCS (GSMA RBM — the verified business sender) moved from carrier-enablement paperwork to per-message billing. The hosts of that layer — Google Jibe on the aggregator side and the carrier validators on the direct side — now price each verified-agent message on delivery, at rates that land beside SMS premium rather than "rich SMS for free." The template-center surface still routes under your own agent's tenant, but what a message bills at depends on whether the sub-brand you send as is verified (authentic RCS) or promotional-but-unverified, and aggregators increasingly pass the per-message rate card through instead of flat bundles. For a CPaaS buyer, "RCS" now means a per-message verified-agent line item — and that is exactly the register this post prices.

What changed

RCS Business Messaging (RBM) only became a billable lane when the vendors that host the verification layer turned monetization on. Before late 2025, carrier onboarding was mostly a one-time enablement fee buried in the aggregator contract, and per-message cost looked like premium SMS with flat bundle pricing. Three boundary changes flipped it into a per-message autoscaling model:

  • Verified-agent path monetized. The GSMA's Universal Profile verification framework attaches a verified agent (brand, logo, legal entity) to a sender. Google Jibe operates the hosted registration most Western traffic rides; carriers run their own validator registries beside it. Billing activates on that verified-agent path: a delivered message against a verified agent draws a per-message fee at the host's rate card, the same way SMS premium bills on delivery.
  • Per-message authentic RCS bills like SMS premium. Where the verified agent is active and the recipient is RCS-capable, delivery bills per message at the premium-SMS-class rate on the host side. "Authentic" is the term the lane uses for verified-agent traffic, distinguishing it from unverified attempts that never attain the verified banner.
  • Template-center presence routes under the agent's own tenant. The template library (the group of approved message bodies you reuse) still resolves against the agent registration your tenant owns — it is not re-homed to the aggregator. What changed is that templates now bill per message at send, so the library's existence is an enablement fact while its traffic is a per-message expense, exactly the split Meta runs on WhatsApp.

The published rate card lives with the RBM host (Jibe on the aggregator side, the carrier validator on direct-carrier connections), and Orbit passes RCS carrier and aggregator fees through at zero platform markup, so the shift lands on the host side of the bill, not on ours.

What it means for your bill

Three moves decide spend under per-message verified-agent billing:

  1. Verified vs promotional pricing diverges. A promotional traffic class that never completes verified-agent registration falls back to the unverified lane — degraded rich features at worst, a per-message rate one tier apart at best. Registering the verified agent per sub-brand keeps promotional volume from silently drifting onto the cheaper-but-unverified (or blocked) path, exactly the discipline the carrier-sweep explainer names from the enforcement side.
  2. Fallback mix is a pricing decision now. When the capability check returns not-capable, the chain falls to SMS premium — carrier-billed on its own per-message rate. A recipient segment at 60% RCS capability pays RCS verified-agent rates for the 60% and SMS premium for the 40%, so the effective blended rate is a capability-weighted mix, not one channel's sticker. The channel fallback matrix gives the per-channel failure shapes; the RCS-to-SMS variant is the one your invoice actually meets.
  3. Bypass aggregators vs direct-carrier-billing. The bypass lane — connecting a direct carrier validator instead of riding Jibe — only pays when the direct carrier's per-message rate undercuts the aggregator's passed-through card at your volume. The direct-carrier-billing conversation-payments post prices the sibling operator-billed rail on the same channels; the RCS decision is the same shape: compare the host-side per-message rate against your per-market capability mix, then route.

Tenant-owned controls in Orbit

The pricing model is the RBM host's; which message classes run verified, and when a not-capable recipient falls through, is your call. Orbit exposes the levers and the enforcement points; the posture stays tenant-owned.

  • RCS channel configuration. The verified agent, sender profile, and per-recipient capability check live under Channels → RCS — the marketing surface that names the shipped channel, and the dashboard lane where the sender profile and capability probes are set. The RCS channel docs cover the end-to-end agent + capability lifecycle.
  • Template categories. RCS templates are grouped by declared use — transactional vs promotional — under the tenant's template library, and a promotional body sent on a transactional declaration is the drift the carrier sweep re-opens. Keeping each body on its declared category is now a direct cost control: per-message billing turns a mis-tagged template from a review finding into a per-send charge.
  • Fallback matrix. The channel fallback matrix post walks the organization-level fallback chain (RCS → SMS is the common pair) and the capability-cache behavior that triggers it — the chain decides what pays SMS premium and what pays verified-RCS per recipient.

Where Orbit's zero-markup pass-through applies

Orbit's platform charge is the same on every channel: the host's own rate card passes through at zero platform markup at the messaging layer. For RCS that means the per-message fee the RBM host bills — Jibe on the aggregator path, the carrier validator on a direct connection — reconciles into your invoice at cost. The aggregate platform charge (workspace, seats, and the surfaces above) is carried separately and never scales with RCS volume. This mirrors the WhatsApp pricing-shift disclaimer verbatim in posture: Meta owns that rate card, the RBM hosts own this one, and Orbit owns neither.

Frequently asked questions

What changed in RCS pricing?

The RBM hosts (Google Jibe on the aggregator side, carrier validators on the direct side) activated per-message billing on the verified-agent path in late 2025. Delivered verified-agent traffic now bills per message at rates in the SMS-premium class, replacing the flat carrier-enablement bundles most sender programs were priced on before.

Does a verified agent cost money per message?

Yes, on the host side. A message delivered against a verified agent draws the host's per-message rate at delivery; the verification registration itself is the enablement step, not the billing event. What the verified banner buys is the right lane — the per-message rate applies to traffic that attains it.

How does the SMS fallback affect my RCS spend?

The capability check short-circuits non-RCS recipients into SMS, which bills at SMS premium on the carrier side. In a market with partial RCS coverage, your blended per-message cost is the capability-weighted average of verified-RCS per-message and SMS premium — the fallback is a pricing term, not only a deliverability term, because both sides bill.

Is bypassing the aggregator cheaper than riding Jibe?

Only when the direct carrier validator's per-message rate undercuts the aggregator's passed-through card at your volume and per-market capability mix. The same direct-vs-aggregator arithmetic runs on the operator-billed sibling rail; route on the per-message comparison, not on the branding preference.

What does Orbit charge on top of RCS carrier and aggregator fees?

Nothing at the messaging layer: Orbit passes RCS carrier and aggregator fees through at zero platform markup. The template-category, fallback-chain, and capability-check controls above are tenant-owned settings on the platform, not billable add-ons.

Resources

Published 30 September 2026.

Keep reading

RCS Pricing in 2026: From Carrier Enablement to Per-Message Verified-Agent Billing, Explained — Orbit by Devotel