Learn / Who is legally the carrier
In most white-label arrangements: yours.
As far as federal and state regulators are concerned, the carrier is whoever actually sells the phone service to the end customer. In a typical white-label deal, that's you, not your vendor.
Everything else follows. The licensing, the filings, the robocall and E911 obligations, and the taxes and fees (calculated on retail, not wholesale amounts) all land on you.
Vertical SaaS and vertical AI platforms usually find this out the hard way. A letter from the state public utility commission asking why you aren't registered. A discovery that telecom tax has been collected on the wholesale invoice when it owed on the retail amount. Or a question from an acquirer's counsel, mid-diligence, that nobody in the room can answer.
It's exacting work that has to be right, and nobody will give you credit for it. Not your customers, not your investors.
These labels get used interchangeably in sales conversations, and they aren't the same thing at all.
White-label describes whose brand is on the portal. You get the platform, the admin experience, the provisioning, the devices, all wearing your logo. It's a statement about the product.
Carrier of record describes who the various regulators consider to be the phone company. It's a statement about liability.
You can have the first without the second, and most platforms do. The difference is whether you're offering an exciting new product or picking up a compliance nightmare.
Selling phone service in the US comes with a set of obligations that have nothing to do with software. Broadly:
These are categories, not the full list, which changes often enough that anything we published today would be stale in months. That churn is the point: this isn't a project that finishes.
This is the one nobody arrives prepared for. Telecom taxes and fees are generally calculated on the retail amount you bill your customer, not the wholesale amount your supplier bills you.
So a platform that resells at three times cost and budgets its tax exposure against the supplier invoice has under-modeled the liability by roughly the same multiple. It's a quiet error, it compounds monthly, and nobody notices until someone goes looking.
Resale exemptions, contribution certification, and state and local variation all complicate the detail, which is why that first sentence says "generally" rather than "always."
CPaaS, SIP trunks, and white-label platforms are all wholesale arrangements. None of them changes who the regulator considers to be selling phone service to the end customer.
The regulatory regime doesn't care that Twilio or Telnyx or a white-label platform sits upstream of you, in the same way a restaurant's food safety obligations don't transfer to its wholesaler. Read your agreement for this specific point rather than assuming it.
It helps to think of the options as rungs rather than alternatives. Every step up hands more of the work to the vendor, and the regulatory layer is the last thing to go.
Note where the regulatory row sits. All four of these will get you a working phone product. Only one of them takes that row with it.
Ask them in writing. The answers are either immediate and specific, or they aren't answers.
We don't sell a white-label-only version, so there's no cheaper tier where the filings quietly become yours. When you put embedded phones in front of your customers, we're the carrier underneath.
That part is our job, permanently.
What doesn't move is everything that matters commercially. You own the customer, you set the pricing, and it's your experience.
This guide describes how these arrangements generally work. It isn't legal advice, and every platform's situation differs. If you'd like to talk to someone who actually practices in this area, we're happy to make an introduction.
Bring an engineer, and bring whoever signs contracts. The regulatory question is usually the one that decides this, and it's better asked early.