The short answer

CNAM is the name a recipient sees before deciding whether to answer. For outbound voice AI it is one of the few levers that affects answer rate directly, because an unlabelled number reads as a cold call. It is also frequently misunderstood: the calling party does not control what is displayed, and delivery is not guaranteed.

In detail

In the traditional North American model the caller’s carrier publishes a name into a CNAM database, and the recipient’s carrier performs a dip against that database at call time to render the display. Because the dip happens on the terminating side, the calling party controls only what is published — not whether it is looked up, cached, overridden or shown at all.

Delivery is therefore inconsistent by design. Many mobile carriers do not perform traditional CNAM dips, substituting their own analytics-driven labels or the contact name already in the handset. Records can be cached for long periods, so a change may take time to appear. The legacy field is also limited to fifteen characters, which forces abbreviation of most business names.

Branded calling initiatives aim to replace this with something the calling party can actually control — a verified name, logo and call reason delivered to supporting handsets and tied to a verified identity. Adoption is uneven across carriers and devices, so in practice CNAM registration and branded calling are complementary rather than alternatives.

How Rexa handles it

Rexa exposes the CNAM caller-id name configured on a phone number through the numbers API, though it is populated for Telnyx numbers only and returns null for Twilio and Plivo. Number-health monitoring also references CNAM directly: when a number’s answer profile degrades, the platform recommends rotating to a fresh number with CNAM registered.

Providers

Back to the glossary

All 53 glossary terms