Caller ID name (CNAM) is the text carriers show beside your number. See how the CNAM database works, how to register a name, and how to check yours by API.

Takeaways
Caller ID name (CNAM) is the name of up to 15 characters that the recipient's carrier looks up for your number and shows beside it. The name is not sent with your call.
When your call reaches a customer, their phone shows either your number alone, such as +1 312 555 0100, or the number with a business name above it. That name is your caller ID name (CNAM), a label of up to 15 characters stored against your number. Some carriers call it Caller Name Presentation, or CNAP.
Is CNAM the same as caller ID? No. Caller ID is the number. CNAM is the name your customer's carrier looks up for that number when your call arrives.

In US networks you do not send the name. Your carrier sends only the number, and the receiving carrier queries a name database with it. That is why a registered name shows on one carrier and not another: each terminating carrier decides whether and where to look.
If you block name delivery, your customer's phone shows 'restricted'. If the lookup fails, such as a database timeout, it shows 'not available'. An empty record leaves the bare number.
Caller ID vs. CNAM
| Caller ID (CLID) | CNAM | |
|---|---|---|
| What it carries | Your number | Your name |
| Who supplies it | Your network, in call signaling | Recipient's carrier, by database lookup |
| Length | Full E.164 number | Up to 15 characters |
| Where it works | Worldwide | US and Canada public switched telephone network (PSTN) |
| What the phone does | Matches it against contacts | Displays it if no contact matches |
See the name your numbers carry
One Number Lookup request returns the stored CNAM for any US number, before your customers see it.
The carrier that issued your number writes the name into its CNAM record. Carriers share those records with several CNAM database providers. When your call lands, the recipient's carrier dips a CNAM database or the Line Information Database (LIDB) for the calling number and pays a per-dip fee. The handset then shows a saved contact name first, the CNAM result second, and any spam label on top of both.

There is no single FCC-run database. The 'national caller ID name database' your name lives in is a set of carrier-owned and third-party databases. A CNAM registry provider copies your issuing carrier's record and sells dips to the carriers that terminate your calls. If you dial into Canada, the originating carrier sends the name with the call.
Every dip on one of your calls costs the terminating carrier money. Wholesale dips run about $0.002 to $0.006 each, which comes to $200 to $600 per 100,000 calls, according to Wikipedia's Calling Name Presentation entry. To cut that bill, some carriers skip the dip or serve a cached result from an earlier lookup. That is the first cause of a wrong or blank name on your calls.
Check these three causes in order before you open a ticket:
Incumbent local exchange carriers (ILECs) usually hold the most accurate data because they issued most of the records. A name that is right on an ILEC landline and wrong on a mobile points at that carrier's cache.
A registered CNAM does not stop your calls being labeled spam, and STIR/SHAKEN does not make your name appear. CNAM is a name the recipient's carrier dips, the record a Number Lookup returns. STIR/SHAKEN, the FCC-mandated framework, cryptographically attests the calling number: your originating carrier signs it and the terminating carrier verifies it. 'CNAM authentication' does not exist, because no layer verifies the name.
The three layers side by side
| Layer | What it shows and where it travels | Who acts and the limit |
|---|---|---|
| CNAM | A name label, from a database | Recipient carrier dips. 15 characters |
| STIR/SHAKEN | Number attestation, in the SIP Identity header | Originating carrier signs, terminating verifies. Number only |
| Branded caller ID / RCD | Name, logo, call reason, in SIP signaling | Originating side attaches, supporting handsets render |
STIR/SHAKEN attests your number at one of three levels, described on the FCC call authentication page:
Branded caller ID and Rich Call Data (RCD) carry your name, logo and call reason in SIP signaling, under Alliance for Telecommunications Industry Solutions (ATIS) and SIP Forum specifications, so the name travels with the call instead of being dipped. Your customer sees it only on a handset and carrier that support RCD.
Carriers compare your number against blocklists and call-pattern analytics, and apps such as Verizon Call Filter print the result over whatever the dip returned. High volume, short calls and unanswered dials from your Telnyx phone numbers feed those analytics, so a number shows 'Spam Risk' or 'Scam Likely' with a valid name. Your 10DLC (10-digit long code) brand registration covers texts only and does nothing for a voice label. A ported number keeps its labels, so run a number portability check first. Clear a label through the analytics providers, or through traceback for illegal traffic, the work the Industry Traceback Group does.
You register the name with the carrier that holds the number, and the recipient's carrier displays it after the record propagates. If your pool spans four carriers you file four registrations. For contact center solutions running several hundred thousand dials a day, CNAM belongs in your carrier contract as a per-number attribute.
Which path gets your name displayed?
You get 15 characters including spaces. Your carrier stores the name in uppercase, and it may contain only the letters A-Z, the digits 0-9 and spaces. Punctuation, ampersands and accented letters are stripped or rejected, so you cannot register 'ACME DENTAL & CO.' but 'ACME DENTAL CO' goes through.
If one of your teams registers 'ACME DENTAL' and another 'ACME DNTL', half your numbers look like a different company. Pick one abbreviation and use it on every number in the pool, and match the name customers already know from your website and invoices.

At most providers a CNAM registration or name change is a ticket rather than a self-serve edit. Send three things: the list of numbers, pulled from the list your phone numbers endpoint, the requested name, and proof of business identity, the same evidence your carrier needs for 10DLC brand registration and an Industry Traceback Group traceback.
Propagation takes days and varies by carrier. Before you port a pool, run a number portability check and plan the re-registration, since the record stays with the losing carrier. Telnyx documents the request in the support article caller ID vs CNAM.
Check this list before you file:
Run these three checks in order, cheapest first.

Telnyx Number Lookup, the CNAM checker, returns the stored name or an empty record when none exists. The Number Lookup API reference documents the GET request with the caller-name type. Before a campaign, list your phone numbers and look up each one, as sales and marketing teams do.
Your mobile checks saved contacts first, and its carrier app may swap in a label, so a saved contact or a spam tag can hide a correct CNAM. A landline shows the dipped name directly. Call them on different carriers from a phone with no contact entry for your number.
A name correct on one carrier and blank on another points to a skipped dip or a cached record. An old company name on every carrier points to a stale record at the database owner, so the correction goes to the carrier that holds the number, which a number portability check confirms. A name right on your test calls but wrong on calls your contact center never placed points to spoofing, which the Industry Traceback Group traces to its source. Attach the lookup result to the ticket.
The name your customers see is set on your Telnyx phone numbers and checked with Number Lookup from the account that also handles 10DLC brand registration. The support article Caller ID outbound vs CNAM separates the two records, the caller ID management page covers setting the name, and the CNAM in Canada release note covers calls into Canada, which are handled differently. Telnyx vs Twilio compares the two voice APIs, and the branded calling reference example on GitHub takes branded calling profiles past 15 characters.
Caller ID name (CNAM) FAQ
One Number Lookup request returns the exact name the CNAM database holds for any US number, so you stop guessing what customers see and stop waiting days to test from a colleague's phone.
Run a CNAM lookupRelated articles
2FA vs. MFA

Here’s how to check if your number can be ported

Inference optimization: cut LLM latency and cost

What is call control? Direct, programmable control over every call

GLM 5.3 Flash benchmark: Telnyx vs Modal

The best Vapi alternatives for low latency voice AI in 2026