Skip to content

Commit 6549726

Browse files
authored
Merge pull request #294593 from henikaraa/acs-cnam-process
Acs cnam process and display name
2 parents c6e9a65 + 602232f commit 6549726

File tree

2 files changed

+59
-0
lines changed

2 files changed

+59
-0
lines changed
248 KB
Loading
Lines changed: 59 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,59 @@
1+
---
2+
title: Define your caller identity
3+
4+
titleSuffix: An Azure Communication Services concept document
5+
description: Learn about Communication Services CNAM registration process.
6+
author: henikaraa
7+
manager: ankura
8+
services: azure-communication-services
9+
ms.author: henikaraa
10+
ms.date: 02/13/2025
11+
ms.topic: conceptual
12+
ms.service: azure-communication-services
13+
---
14+
15+
# Define your caller identity
16+
17+
A common challenge faced by businesses is the difficulty of getting their calls answered or even noticed by customers. In many cases, potential customers ignore or block calls from unknown or unfamiliar numbers.
18+
19+
Using an unidentified number can lead to missed opportunities for sales, customer service, and other important interactions. This problem can be especially challenging for businesses that rely heavily on phone-based communication, such as call centers or sales teams.
20+
21+
To address these challenges, Azure Communications Services offers customers the ability to define their caller's name when they place a public switched telephone network (PSTN) call and proposes a new Caller Name Delivery (CNAM) registration process. To avoid their customer calling numbers being flagged as spam, customers should register their PSTN outbound numbers with central registries and to follow best practices described in this article.
22+
23+
## What is Caller Name Delivery (CNAM)
24+
25+
In the US, Caller Name Delivery (CNAM) provides the caller's name or company name in Caller ID, though it can also show as \"restricted\" or \"not available\" due to blocking or technical issues. The terminating carrier retrieves this information through a database lookup (up to eight
26+
providers in the US) using the caller\'s phone number. In Canada, you can add the caller's name using either the client\'s equipment (such as PBX) or the originating carrier, as long as it complies with anti-spoofing and fraud regulations.
27+
28+
![A call flow diagram showing your call registered with a Caller Name Delivery (CNAM) from Azure Communication Services through an originating service provider and terminating service provider to the called device displaying your CNAM.](../media/cnam-call-flow.png)
29+
30+
## How to register
31+
32+
To request a CNAM registration for an Azure Communication Services number, customers need to send an email to `<[email protected]>`, using `"ACS Number Request -- CNAM Registration"` as part of subject line. In the body or the email, provide the following details:
33+
34+
- Customer and Azure account details.
35+
36+
- List a number and the corresponding caller name to register for each number. The customer must own these numbers under the Azure Resource provided. Customer can register only **US local numbers**.
37+
38+
CNAM caller names are limited to 15 characters (including spaces) and support the following special characters:
39+
40+
| Special character | Name |
41+
| --- |:--- |
42+
| **.** | period |
43+
| **,** | comma |
44+
| **&** | ampersand |
45+
| **-** | dash |
46+
| **_** | underscore |
47+
| **'** | single quote (as in Tom's Burgers) |
48+
49+
Once the request is approved by the carrier, it takes **48 hours to be published.**
50+
51+
## Things to consider
52+
53+
- The reliability of CNAM delivery with the call varies depending on the country/region and carriers that handle the call; either as an intermediary or a terminating carrier.
54+
- Inconsistencies in CNAM can be caused when the intermediate or terminating carriers delay refreshing the CNAM information in authoritative databases, such as in the United States. In countries/regions where there are no authoritative databases for CNAM, individual carrier practices can also cause problems with CNAM information arriving intact with the call.
55+
- Azure Communication Services currently doesn't support CNAM registration for countries or regions outside the United States.
56+
- This registration is available only for US local numbers. It doesn't support toll free numbers.
57+
- This service only applies to *outbound* calls for numbers that customer owns.
58+
- CNAM databases aren't always up to date and not consistently updated. There's a potential for misspellings.
59+
- There are multiple CNAM databases across the country and terminating carriers may subscribe to one or more databases.

0 commit comments

Comments
 (0)