Verified calling — ecosystem roles

Trust flows top-down through the chain; hover or tap any role for its definition, examples and what Gated's service brings it. The second diagram details the terminating side — the MNO's choice between building its own service or adopting Google MaaP.

GSMA scheme owner · root of trust accredits OVC vetter independent accredited issuer ID · NAME · TN sub-types issues credential Brand / enterprise holder · accountable party Onboarding agent sells the service presents credential Aggregator aggregated services brand-only traffic hands off Gated verify & sign number resolution API normalisation signs & routes Verifier · terminating endpoint verifies & brands the call Terminating MNO Google MaaP Terminating operator branded call Consumer called party voice bearer path grants trust holds credential sells & aggregates signs, routes, verifies

Terminating side — the MNO's two options

Gated hands the verified, signed announcement to the MNO, which chooses how to present it to its customers. Both routes end in the same branded call.

Verified announcement handed off by Gated Terminating MNO chooses how to serve or Build own Verified Caller own registry of verified brands MNO correlates & brands Adopt Google MaaP extends A2P messaging relationship Google holds assets · device pulls Customer sees the branded call

The MNO picks build-or-adopt from one Gated integration. For an MNO already on MaaP for A2P messaging, adopting is a simple extension rather than a new build — and for Google, MaaP revenue extends from messaging into voice.

Hover on desktop · tap on touch devices · keyboard: Tab to a role, then it shows on focus