# Branded calling and CNAM delivery

Canonical: https://warmtransfer.net/knowledge/branded-calling-cnam

Last verified: 2026-09-24

Branded calling and calling party name (CNAM) delivery convey identity, imagery, and call context across telecommunications networks[^6]. These mechanisms rely on database lookups, SIP signaling headers, and cryptographic extensions defined in standard specifications[^36][^39].

## Standards and Protocol Architecture

Rich Call Data (RCD) is standardized under RFC 9795, published on the Standards Track in July 2025 by C. Wendt and J. Peterson as a PASSporT extension[^36]. RFC 9795 defines a JSON Web Token (JWT) claim named `rcd`, which holds an object containing one or more key-value pairs of caller details[^29]. Within the `rcd` claim, the `nam` key carries the display name, is mandatory, and is populated with an empty string if no name is present[^32]. Optional `rcd` keys include `apn` (alternate presentation number), `icn` (HTTPS URL of an image), `jcd` (inline jCard), and `jcl` (HTTPS URL of a jCard)[^33]. The `jcd` and `jcl` keys are mutually exclusive, requiring a jCard to be represented either inline or by URL reference, but not both[^25].

When the `rcd` claim references external URIs, RFC 9795 requires an `rcdi` claim containing cryptographic digests addressed by JSON pointer; implementations must support SHA-256, SHA-384, and SHA-512[^35]. An optional `crn` claim provides a single string indicating the call reason[^16]. If a PASSporT header specifies the `ppt` value `rcd`, it must carry at least 1 `rcd` or `crn` claim[^28]. An authentication service can send `rcd` in its own PASSporT using a distinct Identity header or append `rcd` claims to another extension token like `shaken`, where verifiers lacking `rcd` support ignore the added fields[^30]. By default, an authentication service sets `nam` from the SIP `From` display-name; if the resulting `nam` value diverges from that display-name, it must format the token as a full PASSporT rather than a compact form[^26]. UAS treatment of an incoming `rcd` claim follows local implementation policy, as RFC 9795 does not mandate rendering[^34].

RFC 9796, published in July 2025 as the companion standard to RFC 9795, defines SIP `Call-Info` parameters for RCD[^37]. It introduces the `jcard` purpose token to deliver rich call data as a jCard and supplies guidance on applying the `icon` purpose token[^12]. RFC 9796 also establishes a `call-reason` parameter for alerting displays, recommending a length of no more than 64 characters[^11]. Under RFC 9796, the STIR framework and `rcd` PASSporTs should protect the authenticity and integrity of `Call-Info` elements[^13]. In carrier networks, ATIS-1000094 outlines SHAKEN procedures for calling name, call reason, and logos or images across authentication, verification, and transport[^1].

## Regulatory Framework and Ecosystems

In the United States, 47 CFR 64.1600 establishes that information regarding call origination includes calling name, extending caller-ID rules to cover name as well as telephone number[^14]. Under 47 CFR 64.1601(e), telemarketers must pass CPN or ANI along with their name when available through their carrier, and are barred from blocking caller identification details[^15]. Under 47 CFR 64.1604(a), transmitting inaccurate or misleading caller ID information with intent to defraud, cause harm, or wrongfully obtain value is prohibited across both voice and text messaging[^47]. On 7 October 2025, the FCC issued a fact sheet and draft Call Branding FNPRM (FCC-CIRC2510-07) titled *Improving Verification and Presentation of Caller Identification Information* under CG Dockets 17-59, 02-278, 25-307, and WC Docket 17-97[^18].

CTIA outlines Branded Calling ID (BCID) as an industry Rich Call Data framework that passes name, call reason, and logos to mobile devices on STIR/SHAKEN-signed calls[^6]. BCID roles divide operational responsibilities:
- **Onboarding Agent**: Acts as the enterprise entry point, gathering business information for Vetting Agents while providing billing, reporting, and customer support[^5].
- **Vetting Agent**: Confirms the enterprise's identity and checks that it holds the legal right to present the specified display name, call reason, and logo[^10].
- **Signing Agent**: Signs the Rich Call Data PASSporT cryptographically, verifying that the call has completed vetting[^7].
- **Terminating Service Provider**: Serves the mobile subscriber receiving the call and can collect revenue on confirmed delivery[^8].

BCID offers Confirmed Call Delivery, charging enterprises only when delivery of rich call data is confirmed[^4]. CTIA announced the integration of BCID into Verizon's wireless network on 15 September 2025, following earlier implementation by T-Mobile[^9].

## Platform Implementations

Carrier database architectures and enterprise platform rules governing display formatting and transport across vendors are not covered by the sources below.

### Microsoft Teams

Microsoft Teams defines caller ID as two distinct components: calling line ID (CLID) for the number, and calling party name (CNAM) for the name[^38]. Outbound calling party names can be set up to 200 characters in Teams caller ID policies, though downstream telecommunications systems may enforce smaller bounds[^42]. Teams sends the configured calling party name only when calling as a Teams user presenting their own assigned number or a resource account number; setting the call to Anonymous suppresses both name and number[^43]. Microsoft notes that terminating delivery of outbound CNAM ultimately depends on PSTN carrier support[^44]. For Direct Routing, Teams transmits the modified number and CNAM within the SIP `From` header, while `P-Asserted-Identity` preserves the true calling user when `ForwardPai` is enabled on the SBC[^40].

For inbound PSTN calls, Teams chooses the displayed caller ID in the order of the called user's People contacts, then Outlook and Entra ID contacts, then the incoming calling party name, then the calling line ID[^41]. If Teams flags an inbound call as potential spam, it presents the caller ID as Spam likely, which administrators can disable via user calling policies[^45]. Microsoft does not support originating CNAM for Teams calls outside the United States[^46]. Microsoft attributes broken or inconsistent CNAM to downstream carriers delaying updates to authoritative US CNAM databases, and notes it has little recourse when carriers change, omit or truncate CLID[^39].

### Twilio

Twilio separation of traditional CNAM storage from branded calling features is not covered by the sources below.

| Feature | Display Name Limit | Additional Media / Parameters | Regional & Network Scope |
|:--- |:--- |:--- |:--- |
| CNAM | Up to 15 characters, leading letter only, alphanumeric with periods, commas, spaces[^50] | None[^50] | US only; displays by default on landlines, but most US mobile carriers require the recipient to opt in[^51] |
| Basic Branded Calling | Business name only[^48] | None[^48] | Public beta; available in the US, Canada, Germany, and the UK[^48] |
| Enhanced Branded Calling | Up to 35 characters[^53] | 256x256 32-bit BMP logo; call reason up to 64 characters (35 or fewer recommended)[^53] | US only; generally available on mobile endpoints via T-Mobile and Verizon[^49][^48] |

Twilio CNAM updates take 48-72 hours to propagate across third-party US databases, and actual display hinges on whether the recipient carrier queries those specific repositories[^52]. Because branded calling operates exclusively on mobile networks, Twilio advises using CNAM for landline targets[^49]. Enhanced Branded Calling requires an approved primary Business Profile with an EIN, a signed Letter of Authorization, and STIR/SHAKEN support on the telephone numbers[^55]. Registration review requires up to 7 days, telephone number provisioning takes 24-48 hours, and provisioned brand information appears on mobile devices after approximately 2 additional hours[^56]. End-user rendering varies by endpoint: Android 14 or later devices from Samsung and Motorola display name, logo, and call reason; iPhones present name and logo; and MVNO users receive only the display name[^54].

### Webex Calling

Webex Calling restricts its Caller ID configurations and call indication options to subscriber sites located in the United States and Canada[^57].

## Applicability

Applies to: CTIA Branded Calling ID, IETF STIR PASSporT, Microsoft Teams Phone, IETF SIP Call-Info, ATIS-1000094, FCC 47 CFR Part 64 Subpart P, FCC Truth in Caller ID rules, FCC caller ID authentication rules, Microsoft Teams Phone Direct Routing, Twilio Programmable Voice CNAM, Twilio Branded Calling, Twilio Enhanced Branded Calling, and Cisco Webex Calling. Deployments: multi-tenant and carrier-network. Sources checked 2026-09-24. Webex Calling features for call indication and Caller ID settings apply only to deployments in the United States and Canada[^57]. Microsoft Teams outbound CNAM origination is limited to users in the United States[^46]. Twilio Enhanced Branded Calling is restricted to mobile traffic on T-Mobile and Verizon within the United States[^49][^48]. ATIS-1000094 applies to SHAKEN carrier network deployments under versions v001 and v002[^1]. Standards-track protocol rules for RCD and companion SIP `Call-Info` parameters are defined under RFC 9795 and RFC 9796[^36][^37].

## What remains uncertain

Webex Calling outbound CNAM and branded calling (BCID or RCD) support is not covered by the sources below. AT&T participation in CTIA BCID versus TransUnion proprietary display is not covered by the sources below. Apple iOS branded calling display (Business Connect) and its relation to BCID is not covered by the sources below. CUBE and SBC handling of Identity headers carrying `rcd` claims is not covered by the sources below. Contact center outbound campaign branded calling is not covered by the sources below. Teams Operator Connect and Calling Plan per-operator CNAM delivery behaviour is not covered by the sources below. Handset treatment when verstat and BCID brand data disagree is not covered by the sources below. Canada branded caller ID and CRTC position is not covered by the sources below.

## Sources

[^1]: ATIS-1000094 is the SHAKEN specification for Calling Name and Rich Call Data Handling Procedures; it covers authentication, verification and transport of calling name, logos and other images, and call reason. Source: [ATIS 1000094: SHAKEN: Calling Name and Rich Call Data Handling Procedures (store listing)](https://store.accuristech.com/standards/atis-1000094?product_id=2218511), listing title and abstract. Checked 2026-09-24.
[^2]: The FCC call-branding draft says ATIS-1000094 v002 was finalized in July 2025 (disputed). Source: [FCC Fact Sheet and draft: Call Branding FNPRM, Improving Verification and Presentation of Caller Identification Information (FCC-CIRC2510-07)](https://docs.fcc.gov/public/attachments/DOC-415059A1.txt), draft FNPRM paragraphs 12-13 (RCD standards discussion). Checked 2026-09-24.
[^3]: The Accuris listing says ATIS-1000094 v002, the current version, was published in June 2025 (disputed). Source: [ATIS 1000094: SHAKEN: Calling Name and Rich Call Data Handling Procedures (store listing)](https://store.accuristech.com/standards/atis-1000094?product_id=2218511), listing note on current version. Checked 2026-09-24.
[^4]: BCID advertises Confirmed Call Delivery: the business receives confirmation that its rich call data was delivered and pays only for confirmed deliveries. Source: [Branded Calling ID home](https://brandedcallingid.com/), Confirmed Call Delivery section. Checked 2026-09-24.
[^5]: In BCID an Onboarding Agent is the point of entry for enterprises: it collects and passes customer information to approved Vetting Agents and handles billing, reporting and support. Source: [Authorized Partners - Branded Calling ID](https://brandedcallingid.com/authorized-partners/), Onboarding Agent role definition. Checked 2026-09-24.
[^6]: CTIA describes Branded Calling ID as an industry-led, standards-based Rich Call Data ecosystem that delivers the caller's name, logo and call reason to smartphones on STIR/SHAKEN-signed calls. Source: [Branded Calling ID home](https://brandedcallingid.com/), home page hero and technology sections. Checked 2026-09-24.
[^7]: In BCID a Signing Agent generates the cryptographic signature on the Rich Call Data PASSporT, confirming the call was vetted and validated. Source: [Authorized Partners - Branded Calling ID](https://brandedcallingid.com/authorized-partners/), Signing Agent role definition. Checked 2026-09-24.
[^8]: BCID defines Terminating Service Providers as network operators whose mobile users receive branded calls and who can earn revenue on confirmed delivery. Source: [Authorized Partners - Branded Calling ID](https://brandedcallingid.com/authorized-partners/), Terminating Service Provider role definition. Checked 2026-09-24.
[^9]: CTIA announced on 15 September 2025 that Branded Calling ID was integrating on Verizon's wireless network, after earlier adoption by T-Mobile. Source: [New Consumer Tool, Branded Calling ID to launch on Verizon's Network](https://www.prnewswire.com/news-releases/new-consumer-tool-branded-calling-id-to-launch-on-verizons-network-302556438.html), release dateline and opening paragraphs. Checked 2026-09-24.
[^10]: In BCID a Vetting Agent is the third party that validates that an enterprise caller is who it claims to be and has the right to use the display name, logo and call reason. Source: [Authorized Partners - Branded Calling ID](https://brandedcallingid.com/authorized-partners/), Vetting Agent role definition. Checked 2026-09-24.
[^11]: RFC 9796 defines a call-reason parameter for a short display message during alerting and recommends that the message be no longer than 64 characters. Source: [RFC 9796: SIP Call-Info Parameters for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9796.html), Section 6 (call-reason parameter). Checked 2026-09-24.
[^12]: RFC 9796 defines a jcard purpose token for the SIP Call-Info header to carry rich call data as a jCard and gives guidance on using the existing icon purpose. Source: [RFC 9796: SIP Call-Info Parameters for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9796.html), Section 5 (jcard purpose); Section 4.5 (icon). Checked 2026-09-24.
[^13]: RFC 9796 says the STIR security framework, including the rcd PASSporT, should be used to protect the integrity and authenticity of Call-Info rich call data. Source: [RFC 9796: SIP Call-Info Parameters for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9796.html), Section 13.2 (security considerations). Checked 2026-09-24.
[^14]: 47 CFR 64.1600 defines information regarding the origination of a call to include the name, so caller-ID rules that refer to it reach calling name as well as number. Source: [47 CFR 64.1600 - Definitions](https://www.law.cornell.edu/cfr/text/47/64.1600), 47 CFR 64.1600(g)(3); see also (c) caller identification information. Checked 2026-09-24.
[^15]: 47 CFR 64.1601(e) requires telemarketers to transmit CPN or ANI and, when their carrier makes it available, the telemarketer's name, and bars them from blocking caller identification information. Source: [47 CFR 64.1601 - Delivery requirements and privacy restrictions](https://www.law.cornell.edu/cfr/text/47/64.1601), 47 CFR 64.1601(e). Checked 2026-09-24.
[^16]: RFC 9795 defines an optional crn claim that carries a single string describing the reason for the call. Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), Section 7 (crn claim). Checked 2026-09-24.
[^17]: The draft FNPRM says legacy CNAM databases remain the only widespread source of caller name information but are reportedly not reliably accurate and are open to manipulation. Source: [FCC Fact Sheet and draft: Call Branding FNPRM, Improving Verification and Presentation of Caller Identification Information (FCC-CIRC2510-07)](https://docs.fcc.gov/public/attachments/DOC-415059A1.txt), draft FNPRM paragraphs 8 and 14. Checked 2026-09-24.
[^18]: On 7 October 2025 the FCC released a fact sheet and public draft (FCC-CIRC2510-07) of a Call Branding FNPRM titled Improving Verification and Presentation of Caller Identification Information, in CG Dockets 17-59, 02-278 and 25-307 and WC Docket 17-97. Source: [FCC Fact Sheet and draft: Call Branding FNPRM, Improving Verification and Presentation of Caller Identification Information (FCC-CIRC2510-07)](https://docs.fcc.gov/public/attachments/DOC-415059A1.txt), cover page and caption. Checked 2026-09-24.
[^19]: The draft FNPRM proposes a verified name, personal or business, as the minimum caller identity to present, with logo and call reason beyond that minimum. Source: [FCC Fact Sheet and draft: Call Branding FNPRM, Improving Verification and Presentation of Caller Identification Information (FCC-CIRC2510-07)](https://docs.fcc.gov/public/attachments/DOC-415059A1.txt), draft FNPRM paragraph 35. Checked 2026-09-24.
[^20]: The draft FNPRM proposes that terminating providers must send verified caller identity information to the handset whenever they send an indication that the call received A-level attestation. Source: [FCC Fact Sheet and draft: Call Branding FNPRM, Improving Verification and Presentation of Caller Identification Information (FCC-CIRC2510-07)](https://docs.fcc.gov/public/attachments/DOC-415059A1.txt), draft FNPRM paragraph 30. Checked 2026-09-24.
[^21]: The draft FNPRM sets no concrete compliance deadline for RCD caller-name presentation; it asks how quickly providers could implement RCD and whether smaller or rural providers should be exempt. Source: [FCC Fact Sheet and draft: Call Branding FNPRM, Improving Verification and Presentation of Caller Identification Information (FCC-CIRC2510-07)](https://docs.fcc.gov/public/attachments/DOC-415059A1.txt), draft FNPRM paragraphs 52 and 61. Checked 2026-09-24.
[^22]: The draft FNPRM notes that RCD works only on IP networks and asks what to do about the non-IP gap, including whether to require other solutions that work on non-IP networks. Source: [FCC Fact Sheet and draft: Call Branding FNPRM, Improving Verification and Presentation of Caller Identification Information (FCC-CIRC2510-07)](https://docs.fcc.gov/public/attachments/DOC-415059A1.txt), draft FNPRM paragraph 62. Checked 2026-09-24.
[^23]: The draft FNPRM proposes that originating providers employ reasonable measures to verify the accuracy of the caller identity information they transmit, and asks what counts as reasonable. Source: [FCC Fact Sheet and draft: Call Branding FNPRM, Improving Verification and Presentation of Caller Identification Information (FCC-CIRC2510-07)](https://docs.fcc.gov/public/attachments/DOC-415059A1.txt), draft FNPRM paragraphs 43-44. Checked 2026-09-24.
[^24]: The draft FNPRM describes RCD as building on STIR/SHAKEN to carry name, photo, logo, email, location, title and call reason, and cites RFC 9795, RFC 9796 and ATIS-1000094 v002 as the RCD standards. Source: [FCC Fact Sheet and draft: Call Branding FNPRM, Improving Verification and Presentation of Caller Identification Information (FCC-CIRC2510-07)](https://docs.fcc.gov/public/attachments/DOC-415059A1.txt), draft FNPRM paragraphs 12-13. Checked 2026-09-24.
[^25]: RFC 9795 makes the jcd and jcl keys mutually exclusive, so a jCard is either inline or referenced by URL but not both. Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), Section 5.1 (jcd and jcl keys). Checked 2026-09-24.
[^26]: Under RFC 9795 the authentication service takes nam from the SIP From display-name by default; if the nam it generates differs from that display-name it must use the full PASSporT form rather than the compact form. Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), Section 12.1 (authentication service behaviour). Checked 2026-09-24.
[^27]: The evidence in this packet does not show that any US rule requiring RCD caller-name transmission or display was in force on 2026-09-24; the latest primary material read is a proposal (inferred). Source: [FCC Fact Sheet and draft: Call Branding FNPRM, Improving Verification and Presentation of Caller Identification Information (FCC-CIRC2510-07)](https://docs.fcc.gov/public/attachments/DOC-415059A1.txt), document type (FNPRM draft) and paragraph 30. Checked 2026-09-24.
[^28]: Under RFC 9795 a PASSporT whose header carries ppt rcd must contain at least one rcd or crn claim. Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), Section 8 (PASSporT rcd extension type). Checked 2026-09-24.
[^29]: RFC 9795 defines a JWT claim named rcd whose value is a JSON object holding one or more key-value pairs of caller information. Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), Section 5.1 (rcd claim). Checked 2026-09-24.
[^30]: RFC 9795 lets an authentication service either send rcd in its own PASSporT with a separate Identity header or add rcd claims directly to another extension PASSporT such as shaken; verifiers that support only the base extension ignore the extra claims. Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), Section 13 (using rcd with other PASSporT extensions). Checked 2026-09-24.
[^31]: A TransNexus RCD explainer lists inf, a URL for a caller-information web page, as a default rcd key, but RFC 9795 Section 5.1 does not list inf (disputed). Source: [Rich Call Data and STIR/SHAKEN](https://transnexus.com/whitepapers/rich-call-data/), Core RCD Structure field list. Checked 2026-09-24.
[^32]: In RFC 9795 the nam key of the rcd claim is mandatory and carries the display name, set to an empty string when there is no name. Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), Section 5.1.1 (nam key). Checked 2026-09-24.
[^33]: RFC 9795 lists the optional rcd keys as apn (alternate presentation number), icn (HTTPS URL of an image), jcd (inline jCard) and jcl (HTTPS URL of a jCard). Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), Section 5.1 (rcd claim keys). Checked 2026-09-24.
[^34]: RFC 9795 leaves the UAS's handling of a received rcd claim largely to implementation policy and does not make rendering mandatory. Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), Section 12.2 (verification service behaviour). Checked 2026-09-24.
[^35]: RFC 9795 defines an rcdi claim of cryptographic digests addressed by JSON pointer; it is required when the rcd claim contains URI references, and SHA-256, SHA-384 and SHA-512 must be supported. Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), Section 6 (rcdi claim). Checked 2026-09-24.
[^36]: RFC 9795, the PASSporT extension for Rich Call Data, was published in July 2025 on the Standards Track, authored by C. Wendt and J. Peterson. Source: [RFC 9795: Personal Assertion Token (PASSporT) Extension for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9795.html), document header and Status of This Memo. Checked 2026-09-24.
[^37]: RFC 9796, SIP Call-Info Parameters for Rich Call Data, was published in July 2025 on the Standards Track as the companion to RFC 9795. Source: [RFC 9796: SIP Call-Info Parameters for Rich Call Data](https://www.rfc-editor.org/rfc/rfc9796.html), document header; Section 1.3. Checked 2026-09-24.
[^38]: Microsoft Teams documentation defines caller ID as two user-facing pieces: calling line ID (CLID), the number, and calling party name (CNAM), the name. Source: [Manage caller ID for users - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/caller-id-policies), opening section (Caller ID consists of two user-facing pieces). Checked 2026-09-24.
[^39]: Microsoft attributes inconsistent CNAM to intermediate or terminating carriers that are slow to refresh the authoritative CNAM databases, as in the United States, and says Microsoft has little recourse when carriers change, omit or truncate CLID. Source: [More about Calling Line ID and Calling Party Name - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/more-about-calling-line-id-and-calling-party-name), second and third paragraphs. Checked 2026-09-24.
[^40]: For Teams Direct Routing the substituted number and the CNAM are sent in the SIP From header; if the SBC is configured with ForwardPai true, the P-Asserted-Identity header carries the real calling user. Source: [Manage caller ID for users - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/caller-id-policies), Outbound calling line ID (Direct Routing paragraph). Checked 2026-09-24.
[^41]: For inbound PSTN calls Teams chooses the displayed caller ID in this order: the called user's People contacts, then Outlook and Entra ID contacts, then the call's calling party name, then its calling line ID. Source: [Manage caller ID for users - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/caller-id-policies), Inbound caller ID behavior. Checked 2026-09-24.
[^42]: A Teams caller ID policy's Calling Party Name can be up to 200 characters, but Microsoft notes that downstream systems might support fewer. Source: [Manage caller ID for users - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/caller-id-policies), Outbound calling party name. Checked 2026-09-24.
[^43]: Teams sends the configured calling party name only when the caller ID is set to the user's number or a resource account's number and the caller is a Teams user; the Anonymous setting removes both number and name. Source: [Manage caller ID for users - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/caller-id-policies), Outbound calling party name; Outbound calling line ID. Checked 2026-09-24.
[^44]: Microsoft states that although Teams supports calling party name on outbound calls, delivering CNAM to the called party still depends on PSTN operators. Source: [Manage caller ID for users - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/caller-id-policies), Outbound calling party name, Note. Checked 2026-09-24.
[^45]: When Teams detects that an inbound call is possibly spam it presents the caller ID as Spam likely, and this can be turned off in the user's calling policy. Source: [Manage caller ID for users - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/caller-id-policies), Spam calls. Checked 2026-09-24.
[^46]: Microsoft does not currently support originating CNAM information for Teams calls outside the United States. Source: [More about Calling Line ID and Calling Party Name - Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/more-about-calling-line-id-and-calling-party-name), final paragraph. Checked 2026-09-24.
[^47]: 47 CFR 64.1604(a) prohibits knowingly transmitting misleading or inaccurate caller identification information with intent to defraud, cause harm or wrongfully obtain anything of value, for both voice and text messaging. Source: [47 CFR 64.1604 - Prohibition on transmission of inaccurate or misleading caller identification information](https://www.law.cornell.edu/cfr/text/47/64.1604), 47 CFR 64.1604(a); exemptions at (b). Checked 2026-09-24.
[^48]: Twilio Basic Branded Calling shows only the business name and is in public beta, and also reaches Canada, Germany and the UK; Enhanced Branded Calling adds logo and call reason, is generally available, and is US-only. Source: [Branded Calling overview](https://www.twilio.com/docs/voice/branded-calling), Basic vs Enhanced and geographic availability sections. Checked 2026-09-24.
[^49]: Twilio Branded Calling works only on mobile devices, on T-Mobile and Verizon in the US, and Twilio recommends CNAM for landline recipients. Source: [Branded Calling overview](https://www.twilio.com/docs/voice/branded-calling), carrier support and CNAM alternative sections. Checked 2026-09-24.
[^50]: Twilio's CNAM display name can be at most 15 characters, must begin with a letter, and may contain only letters, numbers, periods, commas and spaces. Source: [Brand your calls using CNAM](https://www.twilio.com/docs/voice/brand-your-calls-using-cnam), display name requirements section. Checked 2026-09-24.
[^51]: Twilio says CNAM displays by default on landlines, but most US mobile carriers require the recipient to opt in, so an unenabled mobile phone will not show a correctly set CNAM. Source: [Brand your calls using CNAM](https://www.twilio.com/docs/voice/brand-your-calls-using-cnam), display on device types section. Checked 2026-09-24.
[^52]: After approval, a Twilio CNAM display name can take 48-72 hours to propagate to US carriers, and display depends on which CNAM databases the recipient's carrier subscribes to. Source: [Brand your calls using CNAM](https://www.twilio.com/docs/voice/brand-your-calls-using-cnam), propagation and carrier dependency sections. Checked 2026-09-24.
[^53]: Twilio Enhanced Branded Calling allows a display name of up to 35 characters, requires a 256x256 32-bit BMP logo, and caps call reason at 64 characters, recommending 35 or fewer. Source: [US Enhanced Branded Calling](https://www.twilio.com/docs/voice/branded-calling/us-enhanced), display specifications section. Checked 2026-09-24.
[^54]: Twilio says Samsung and Motorola phones on Android 14 or later show name, logo and call reason for Enhanced Branded Calling, iPhones show name and logo only, and MVNO subscribers see the display name only. Source: [US Enhanced Branded Calling](https://www.twilio.com/docs/voice/branded-calling/us-enhanced), supported carriers and devices section. Checked 2026-09-24.
[^55]: Twilio US Enhanced Branded Calling requires SHAKEN/STIR on the phone numbers, a signed Letter of Authorization, and an approved primary Business Profile with an EIN. Source: [US Enhanced Branded Calling](https://www.twilio.com/docs/voice/branded-calling/us-enhanced), requirements section. Checked 2026-09-24.
[^56]: Twilio says Enhanced Branded Calling registration review takes up to seven days, number assignment 24-48 hours, and branded information may take about two more hours to appear on devices. Source: [US Enhanced Branded Calling](https://www.twilio.com/docs/voice/branded-calling/us-enhanced), activation and delivery timeline section. Checked 2026-09-24.
[^57]: Webex Calling's call indication features and Caller ID settings apply only to locations in the United States and Canada. Source: [Secure Calling and Spam mitigation](https://help.webex.com/en-us/article/8j6te9/Secure-Calling-and-Spam-mitigation), region applicability note. Checked 2026-09-24.
[^58]: Webex Calling shows Potential Fraud when verstat is TN-Validation-Failed, and Possible Spam when verstat is No-TN-Validation, missing, or TN-Validation-Passed with C attestation. Source: [Secure Calling and Spam mitigation](https://help.webex.com/en-us/article/8j6te9/Secure-Calling-and-Spam-mitigation), verstat to call indication table. Checked 2026-09-24.