Bandwidth: branded calling needs reputation and authentication underneath it

Bandwidth argues that branded calling is necessary but not sufficient — that without a number-reputation layer underneath and pre-call authentication alongside, “a logo is just a coat of paint on a shaky foundation.” The post lays out a three-layer “trust stack” — Reputation, Authentication, Presentation — and positions Bandwidth as the carrier that does all three: Number Reputation Management for spam-mislabel monitoring and remediation, an Identity Authentication API (“coming soon”) for pre-call signed-token validation without an SBC, and rich call data presentation on the handset. The framing line: “You can’t out-brand a mislabel.”

The point about mislabeling is real and worth marking. Bandwidth cites 53% of enterprise leaders saying improper spam labels have cut contact rates with customers, and 17% who don’t even know whether their numbers had been mislabeled. That’s the part of the trust problem that lives entirely downstream of attestation: even a fully signed call with an “A” attestation can land on a handset as “Spam Risk” because an analytics engine made a judgment about volume patterns. STIR/SHAKEN doesn’t address it; KYUP doesn’t address it; and branded calling, layered on top, doesn’t override it. The Identity Authentication API — pre-call, network-native, no SBC integration required — is Bandwidth’s pitch for what should fit between attestation and presentation.

The tension to flag: this is also a Bandwidth product post arguing the enterprise needs all three Bandwidth products. The “three-layer stack” is useful conceptual scaffolding, but it conveniently maps onto Bandwidth’s portfolio rather than being a neutral industry taxonomy — and it leaves the foundational layer unnamed. Before reputation, authentication, or presentation can mean anything, somebody has to establish who has the right to use the telephone number in the first place. Bandwidth’s Identity Authentication API gestures at that question by sending a pre-call signed token, but the token still rests on the originating carrier vouching for its customer — which is where STIR/SHAKEN’s attestation already sits. Right-to-use of the calling number is the layer underneath all of these; branded calling without a credible RTU anchor is a logo painted on a number whose rightful owner is itself unverified. First Orion, Hiya, and TNS would each draw the diagram differently, and the unresolved question — who attests to number ownership, and how that authority propagates up through attestation, reputation, and presentation — is exactly what the KYUP FNPRM and the in-network branded calling deployments (Bouygues among them) are starting to push on.