CNAM & Caller ID: Why Your Business Name Doesn’t Show

1. Caller ID is two separate things: the number and the name

What recipients call “caller ID” is actually two independent pieces of data that travel, and get resolved, differently:

This split is the whole story. Your softphone or PBX config field labeled “Caller ID Name” sets a value that, on most North American calls, never leaves your network and is never seen by the recipient. The number propagates; the name you typed locally usually does not. Understanding why means understanding the CNAM dip.

2. The counter-intuitive core: the receiving carrier looks up the name

Here is the fact that trips up nearly everyone: in North America, the calling party does not transmit the display name. Instead, when a call arrives, the terminating (receiving) carrier performs a CNAM dip, a real-time query of the calling number against a CNAM database to fetch the name to show on the handset.

So you don’t “set” what displays. You populate the databases that the recipient’s carrier queries, and then the recipient’s carrier decides whether, and what, to look up. Walk through the flow:

Each dip costs the terminating carrier a small fee per query. That economic reality drives much of the inconsistency below: to control cost, carriers cache results, dip selectively, or skip the dip entirely.

3. Why your business name doesn’t show

When “Acme Plumbing” never appears, it is almost always one of these five causes, and frequently more than one at once:

• No outbound CNAM record is set. If the carrier that owns your number never published a name for it, there is nothing in the database to find. The dip returns empty, and the handset shows the bare number (or a generic city/state derived from the area code). This is the single most common cause for newly provisioned numbers.
• The recipient’s carrier doesn’t dip CNAM. A dip is optional and costs money. Many carriers, especially wireless, historically did not dip CNAM at all, instead showing only the number or a label derived from their own analytics. If the terminating carrier never queries, a perfect record on your end is irrelevant.
• Propagation lag (caching). CNAM records are not instant. After you set or change a record, it typically takes 24–72 hours to propagate across the database providers and for carrier caches to expire. Set it Friday, and it may not be live everywhere until Monday.
• The 15-character limit truncated it. NANP CNAM is capped at 15 characters, including spaces. “Acme Plumbing & Heating” (23 chars) gets cut to “ACME PLUMBING &” or similar, sometimes to something that reads as nonsense. Many systems also force uppercase.
• Spam analytics overrode it. Even with a correct record and a carrier that dips, the terminating carrier’s reputation engine can replace your name with “Spam Likely” or “Scam Likely.” This is a separate system (it cross-links with STIR/SHAKEN attestation, see STIR/SHAKEN explained) and it wins. A flagged call shows the warning, not your brand.

4. Mobile is a different world

Traditional CNAM was built for the landline (PSTN) era, and that is increasingly where it stays. On mobile, the picture is different in ways that matter for any business doing outbound calling:

• Analytics over dips. Rather than paying for a traditional CNAM dip on every inbound call, mobile carriers increasingly lean on their own machine-learning reputation engines and third-party data, Hiya (T-Mobile’s data partner), First Orion (a primary input for AT&T), and others. What you see on a mobile screen is often an analytics-derived label, not a CNAM database value.
• Apps add their own layer. Caller-ID apps and built-in spam filters (Hiya, Truecaller, the carrier’s own dialer) overlay their own name and reputation data, which can diverge entirely from what any CNAM record says.

The modern answer to “get my brand on a mobile screen” is not CNAM at all, it is branded calling, built on Rich Call Data (RCD). RCD is an emerging standard, tied to STIR/SHAKEN, that lets a verified caller cryptographically attach a name, a logo, and a call reason that displays on supported handsets. Instead of hoping the receiving carrier dips a 15-character text record, the caller signs richer display data that travels with the call and is rendered natively. For the full breakdown of the four major branded-calling programs (Hiya, First Orion, TNS, Google Verified Calls), what they cost, and how to actually get registered, see our branded calling pillar.

5. CNAM vs STIR/SHAKEN, different systems, both shape your call

These two are constantly confused, because both affect what the recipient experiences. They are entirely separate systems:

Crucially, they interact: a call can carry a perfectly correct CNAM record and still be labeled “Spam Likely” if its STIR/SHAKEN attestation is weak. The spam label overrides the name. Getting your brand to show reliably means getting both right, the name half (CNAM/RCD) and the trust half (attestation). For the full breakdown of attestation A vs B vs C and why it drives spam labeling, see STIR/SHAKEN explained.

6. What you can actually do

You can’t force a receiving carrier to dip, but you can control everything on your side and stack the odds. In order of impact:

7. How DIDHub helps

DIDHub addresses both halves of how your call appears, and we’re straight about the limits:

• The name half: you can set the outbound CNAM record on numbers provisioned through DIDHub, so the name published against your number reflects your brand, not whatever default the upstream owner left in place.
• The trust half: for US/CA outbound, we sign your calls with STIR/SHAKEN A-attestation by default for numbers allocated through us or ported in via us, the verified-trust signal that keeps the “Spam Likely” override off your call in the first place.
• Branded calling / RCD: as RCD and branded-calling programs mature, DIDHub is positioned to support attaching verified name, logo, and call-reason data, the mobile-first path to your brand on the screen.

Working a specific name-display or spam-label problem on a range of numbers? [email protected] can look at the actual numbers and tell you what’s fixable.

Bottom line

In North America you don’t set what shows, you populate the databases, and the recipient’s carrier decides what to display. So do the three things that are actually in your control: set and maintain your CNAM record (mind the 15-character limit and the 24–72h propagation), fix your STIR/SHAKEN attestation so a spam label doesn’t bury your name, and adopt branded calling / RCD for the mobile screens where traditional CNAM was never going to reach. Get the name half and the trust half right, and your brand shows up where it can, reliably, and without overpromising.

More from the blog