Set up CNAM

Before you start

Make sure you have the following:

Access to the RiskOS™ Dashboard with the CNAM enrichment enabled.

• Your account owner or administrator can enable this for you. If you're unsure who to contact, reach out to support for assistance.

A basic understanding of RiskOS™ workflows and components.

• If this is your first time working with workflows, review the Workflow overview to understand inputs, enrichments, routing logic, and decisions.

How Caller ID Name works

Caller ID Name is an enrichment available in RiskOS™. It checks an input phone number against telecom-managed databases and returns the registered caller name.

Caller ID Name helps you:

• Verify identity consistency
• Detect mismatches between user-provided information and carrier records
• Create auditable signals for fraud detection and investigation

Caller ID Name returns the following fields:

• callerName: Registered name associated with the phone number
• callerType: Classification of the caller (for example, individual or business)
• countryCode: ISO 3166-1 alpha-2 country code
• phoneNumber: Phone number queried, including country code
• valid: Indicates whether the phone number is recognized as valid

How Caller ID Name fits into a workflow

In RiskOS™, workflows are built by connecting reusable components. Caller ID Name is added as an Enrichment step.

Once the enrichment runs, its outputs are available to downstream workflow components, including:

• Conditions
• Decision rules
• Rule score cards
• Manual review steps
• Final decisions

For more detail on these components, see What are RiskOS™ Workflows?.

Execution flow in RiskOS™

Caller ID Name runs synchronously as part of a RiskOS™ workflow. There is no user handoff or pause in execution.

Input

CNAM

Routing logic

Decision

At a high level, the execution flow looks like this:

1. Input

You call the Evaluation API with a phone number and supporting identity data.

2. CNAM enrichment

RiskOS™ queries telecom-managed databases and returns the registered caller name and related metadata.

3. Routing logic

The workflow evaluates Caller ID Name outputs (for example, name match or mismatch).

4. Decision

The workflow returns a final outcome (for example, Accept, Review, or Reject).

Workflow components used by Caller ID Name

Caller ID Name uses a subset of standard RiskOS™ workflow components.

Configure Caller ID Name

Add Caller ID Name to a workflow

1. In the RiskOS™ Dashboard, go to Workflows and create a new workflow or open an existing one.
2. On the workflow canvas, select the plus (+) icon.
3. Add an Enrichment step.
4. Select CNAM.

📘

Note:

We recommend adding CNAM after phone verification but before final risk decisioning.

Configure inputs and routing

Caller ID Name requires a phone number in valid E.164 format. Additional identity attributes (such as name) are optional but recommended for routing and matching logic.

Common routing patterns include:

• Name mismatch: Route to manual review or higher-risk path
• Name match: Strengthen confidence in identity

Routing strategies should align with your organization’s fraud policy and risk tolerance.

Save and publish

Once your workflow is configured, publish it to go live.

Workflow testing checklist

Use this checklist to confirm accuracy, resilience, and completeness before going live.

Input validation:

• Phone numbers are provided in valid E.164 format.
• U.S. phone numbers are confirmed for CNAM lookup.
• User-provided identity attributes (such as name) are passed where available.

Routing and decisioning:

• Mismatched caller name and user-provided name are detected.
• No CNAM record returned is handled explicitly in routing logic.
• Workflow routing reflects your intended risk strategy.

Operational readiness:

• CNAM outputs are accessible to relevant teams for review and auditing.
• Fallback paths are defined when CNAM data is unavailable or incomplete.