The Platform PM

Overview

Field Guide

Phone numbers, messaging and voice

How a business gets a number or sender approved, provisioned and enabled to send messages and make voice calls in the US, Canada and beyond, who can say no along the way, and who pays when it fails.

Last updated October 2026

01

Overview

5 min read · Chapter 1 of 10

The parties and the two flows. Before anything is sent, the platform takes the business's identity and consent evidence to a gatekeeper (a registry, Meta or Google), and the approval reaches the carriers. Only then do messages flow, and each carrier still filters every one. On WhatsApp, Meta plays both roles.

A phone number is an address a business rents from a carrier. Behind every sender here is the same question: how does a business prove who it is before a carrier, Meta or Google lets it reach someone's phone?

A few years ago it didn't have to. You bought a number through an API and texted that afternoon. Today almost every route to a phone sits behind a registry. US carriers have blocked unregistered 10DLC traffic since February 2025 and unverified toll-free since January 2024. Singapore labels unregistered brand senders "Likely-SCAM", Australia labels them "Unverified" and Spain blocks them. So most of what a platform does here is identity checks and approvals, and the numbers come attached.

I think about the business in four layers:

  • Numbering. Who holds which numbers, and where calls and texts route. In the US and Canada that's the NANP (North American Numbering Plan: +1, ten digits): NANPA hands number blocks to carriers, the NPAC (the national porting database) tracks every ported number, and platforms usually sit at the end of a resale chain.
  • Messaging trust. Whether a business may send A2P traffic (application-to-person, meaning automated). In the US: The Campaign Registry for 10DLC, Somos for toll-free and a CTIA-run registry for short codes, all under each carrier's own filters and fees. Abroad: national sender registries, more and more of them required by regulators.
  • Caller identity. Whether a call shows up signed, named, labelled "Spam Likely" or blocked.
  • Rich channels. WhatsApp (an app over mobile data, independent of carriers) and RCS (the carriers' rich messaging, with Google running the business hub) swap the bare number for a verified brand, under Meta's or Google's rules.

The platform's job: take a customer's use case and country, pick the sender, collect the identity and consent evidence each gatekeeper wants, get it through every approval and keep a dozen outside states in sync. Then decide who eats the bill when a message is blocked, a number is hijacked or an OTP (one-time passcode) form gets pumped: bots trigger texts to numbers whose carrier splits the revenue with the fraudster. I think most of the hard product calls are there.

What makes it hard:

  1. The truth lives elsewhere. Registries, carriers, Meta and Google own the records; your database mirrors them.
  2. State is per carrier. In one country, an RCS agent can be live on one network and pending on the next.
  3. Carriers and industry bodies write the rules that block you day to day, more than laws do.
  4. Money moves on every message. Prices are set by memo: each US text carries a carrier fee of a few tenths of a cent, and all three big US carriers changed theirs in 2026. WhatsApp started charging for service replies on October 1, 2026.

The main players

The diagram shows roles and a few names. These are the companies I'd want to recognize in week one, in no particular order.

Carriers, US and Canada

What they do
Deliver every text and call to their own subscribers
Main players
AT&T, Verizon, T-Mobile; Bell, Rogers, Telus
What they control
Filtering, throughput, carrier fees, suspension

Carrier groups abroad

What they do
The same job, plus approving brand sender IDs one by one
Main players
América Movil, Vodafone, Reliance Jio
What they control
Termination prices and sender approvals in their countries

Platforms (CPaaS)

What they do
Sell businesses the numbers, senders and APIs they send through
Main players
Twilio, Sinch, Infobip, Bandwidth, Vonage
What they control
The customer, onboarding and routing

Fast-growing challengers

What they do
Developer platforms and WhatsApp specialists
Main players
Telnyx, Plivo, Gupshup, 360dialog
What they control
Price pressure on the big platforms; WhatsApp access for smaller software firms

Aggregators and hubs

What they do
Connect platforms to hundreds of carriers; review US campaigns
Main players
Syniverse, Vibes, Proximus Global (BICS), Tata Communications
What they control
Whether a campaign reaches the carriers; wholesale routes and prices

Registries and numbering

What they do
Keep the records for senders, numbers and porting
Main players
The Campaign Registry, Somos, iconectiv, CTIA's Short Code Registry
What they control
Whether a sender exists and where a number routes

Caller-ID trust

What they do
Label, brand or block calls on the carriers' behalf
Main players
Hiya, TNS, First Orion
What they control
What a call shows: a name, a logo or "Spam Likely"

Rich channels

What they do
Own WhatsApp, run business RCS, show RCS on iPhones
Main players
Meta, Google, Apple
What they control
Approvals, templates and WhatsApp prices; RCS launches; iPhone display

How they make money:

  • Layer: Carriers

    Charges for: per business text

    Ballpark (list): A third to a half of a cent per US text, on top of phone plans

  • Layer: Platforms and challengers

    Charges for: per message, plus rent

    Ballpark (list): About 1.3 cents per US text all-in (Twilio); $1-2 a month per number

  • Layer: Aggregators and hubs

    Charges for: a wholesale cut

    Ballpark (list): A slice of each message, plus $10-20 per US campaign review

  • Layer: Registries

    Charges for: per registration

    Ballpark (list): A few dollars per brand, up to $500-1,000 a month per short code

  • Layer: Caller-ID trust

    Charges for: per label or call

    Ballpark (list): Carriers pay for labels; branded calls about 12 cents each (Twilio)

  • Layer: WhatsApp (Meta)

    Charges for: per message

    Ballpark (list): Under a cent to about five cents, by country and category

  • Layer: RCS (Google, Apple)

    Charges for: carrier rates

    Ballpark (list): Google and Apple don't charge; US carriers ask roughly half a cent to a cent and a half

So a good part of what a business pays flows down the chain to carriers and registries, and the platform keeps the gap: almost a third of Bandwidth's revenue is carrier fees passed straight through. The bottlenecks have been changing hands, with Koch buying iconectiv in 2025 and The Campaign Registry coming with Tata Communications' purchase of Kaleyra in 2023. Meta is the clear gainer, as its non-ad revenue, mostly WhatsApp messaging, grew almost three-quarters in a year.

As of October 2026. Players change through acquisitions and new channels, so check it before relying on it.

Say a clinic chain sends appointment reminders through a platform like Twilio or Bandwidth. First the platform registers the clinic's brand and campaign at The Campaign Registry, and an aggregator like Syniverse reviews the campaign and passes it to each carrier. Then each reminder goes from the platform to the aggregator to the patient's carrier, say Verizon, which filters it, delivers it and bills its fee back up the chain. If the clinic also calls patients, the carrier's analytics partner decides whether the call shows its name or "Spam Likely". So one reminder passes through four or five companies, and the clinic has a contract with only one of them.