What is branded calling?

Branded calling (also called branded call display or branded caller ID) is the practice of showing a verified business identity on the called party's screen when a business places an outbound call: the company name, frequently a logo, and sometimes a stated call reason such as "Delivery update." The goal is to answer the question a bare number cannot: who is actually calling, verified by someone other than the caller.

The problem it addresses is measurable: unknown numbers go unanswered, and legitimate business calls are lost in the same silence as Robocalls. Branded calling raises answer confidence by attaching an identity that was vetted before the call and verified during it.

Why CNAM cannot do this

CNAM is the North American caller-name mechanism, and its limits are structural. The payload is classically 15 characters of text, with no logo and no call reason. The name is not transmitted with the call; the terminating carrier must choose to dip a database, and many mobile terminations do not dip at all, which is why CNAM display on smartphones is patchy. Nothing authenticates the string: a CNAM record is an unauthenticated database entry keyed to a number, and a spoofed number pulls the spoofed party's name.

• 15 characters, text only: no logo, no call reason, no rich layout.
• Terminating-carrier dip: display depends on whether the far end queries, and which bureau it queries.
• Patchy mobile support: many wireless terminations skip CNAM, so the channel where answer rates matter most is the one CNAM covers worst.
• No verification: the name is not cryptographically bound to the caller or the call.

The technology: Rich Call Data in STIR/SHAKEN

Branded calling's standards layer is Rich Call Data (RCD): caller name, logo, and call-reason information carried in the STIR/SHAKEN authentication path. IETF RFC 9795 defines the "rcd" PASSporT, an extension of the PASSporT token that STIR/SHAKEN already signs. The RCD claims either embed the display data or reference it (a logo by URL with an integrity hash), and the whole assertion is signed at origination by a party with the right to make it.

1. At origination, the signing provider builds an rcd PASSporT alongside (or within) the SHAKEN PASSporT: calling number, called number, and the rich display claims.
2. The token travels in SIP Identity headers with the call.
3. At termination, the carrier verifies the signature and the integrity of any referenced content, then decides what to render on the handset.
4. The handset displays the verified name, logo, and reason, subject to device and OS support.

The key property is end-to-end integrity: the display data is signed where the identity is known and verified where it is rendered, instead of being looked up out-of-band from a database anyone can populate. Because it rides the same PASSporT machinery as attestation, it inherits the SHAKEN certificate ecosystem and its governance.

The commercial layer today

In practice, branded calling in 2026 is delivered through commercial programs, not raw RFC plumbing. Vendors such as First Orion, Hiya, and TNS run branded-display programs in partnership with carriers: the business enrolls, the vendor vets the brand and its right to the numbers, and the display is delivered through the vendor's on-device or in-network integration with each participating carrier. CTIA launched the Branded Calling ID (BCID) initiative in 2024 as an industry framework for vetted, signed rich call data across carriers, aiming to standardize the vetting and exchange that the vendor programs had been doing bilaterally.

Vetting is the point of the commercial layer. A signature proves who signed; it does not prove the brand is legitimate. Programs therefore verify the business entity, its brand assets, and its authority over the calling numbers before anything is displayed. That vetting step is what separates branded calling from simply writing a name into a header.

Prerequisites in practice

• Clean Why calls get labeled Spam Likely: a number already labeled "Spam Likely" will not benefit from branding, and programs screen reputation before enrollment.
• A-level attestation: the originating provider should fully attest the calling numbers under STIR/SHAKEN. Branding on top of weak or absent attestation is either unavailable or unconvincing.
• Registered, vetted brand: legal entity verification, brand-to-number authorization, and approved display assets (name, logo, call reasons).
• Consistent calling practices: the numbers enrolled should be the numbers actually presented on outbound traffic, with a working callback path.

What it does and does not fix

Branded calling raises answer confidence on the calls it covers: the recipient sees a verified identity instead of an unknown number. It does not, by itself, stop spoofing. An attacker can still present an unbranded number, and a recipient who does not know to expect a brand has no signal that a plain call claiming to be that brand is fake. Branding also does not clean a bad reputation, substitute for consent, or override carrier analytics: a branded program can suspend a brand whose calls generate complaints.

Adoption status

Coverage is partial and rolling out per carrier. Display support is Android-first: native iOS support for third-party branded display has been limited, so iPhone coverage depends on carrier-level integrations and has lagged. A business enrolling today should expect branding on a meaningful but incomplete share of terminations, verify actual display per carrier and device, and treat coverage claims as time-sensitive.

CNAM vs branded calling