MaaP (Messaging as a Platform)

What MaaP actually is

Messaging as a Platform, or MaaP, is the layer that mobile carriers run to turn their RCS network into something businesses can actually build on. It is a programmable platform sitting on top of the carrier's IMS messaging core, exposing APIs that brands and aggregators use to send rich messages, manage agent identity, and host conversational logic.

If RCS is the protocol and RBM is Google's brand-verification program, MaaP is the carrier-side engine that makes the whole system work for commercial traffic.

What MaaP handles

A MaaP platform typically owns:

• Capability detection (does this number support RCS right now)
• Routing of RCS messages between brands and subscribers
• Brand and agent identity management on the carrier side
• Chatbot directory and discovery within the carrier's messaging app
• Compliance enforcement, rate limiting, and abuse prevention
• Analytics and delivery reporting back to the brand

Why MaaP matters for brands

Brands rarely interact with MaaP directly. They go through a CPaaS or aggregator partner that holds MaaP connections to multiple carriers. But the existence and quality of MaaP determines what is actually possible: which features render, how fast messages deliver, and which carriers a campaign can reach.

In the U.S., the major carriers operate or partner on MaaP infrastructure, and that infrastructure is what allows verified RBM agents to deliver rich messages reliably to subscribers.

The post-app angle

The vision behind MaaP, articulated for years by GSMA and the operator community, is that the messaging app becomes a runtime for services, the same way a browser became a runtime for the web. MaaP is the substrate that makes that possible. A consumer searches for a brand inside the messages app, taps a result, and starts a conversation with that brand's agent without installing anything. That is the post-app world MaaP is built for.