Regulatory & ComplianceCompliance

Carrier and Caller ID Regulations

Keep number assignment, DLT identity, carrier routing, and displayed caller information aligned.

8 min readUpdated 25 Sept 20264 guides in this section

The caller identity shown to a recipient must match the approved number, DLT registration, business purpose, and carrier configuration. A correct product configuration is not enough if the underlying number or header mapping is wrong.

Identity chain

  1. 01

    Entity

    The legal business responsible for the calling activity is registered and documented.

  2. 02

    Number

    The commercial number is assigned to the correct entity and approved category.

  3. 03

    DLT header

    The registered header maps to the number and approved call template.

  4. 04

    Carrier route

    The carrier accepts the number and header combination for the intended geography and purpose.

  5. 05

    Agent configuration

    The workspace selects only an approved number for the campaign and agent.

Configuration controls

  • Use allowlists rather than free-form caller-number selection
  • Show the number ownership and status in the assignment interface
  • Block production dialing until required provider approvals are active
  • Keep number changes under change control and re-run test calls
  • Separate test identities from public-facing business numbers

Reputation monitoring

SignalResponse
Immediate disconnect spikePause affected identities and investigate complaints, spoofing, or template mismatch
Sudden answer-rate collapseCheck number reputation, carrier routing, and destination mix
Caller reports a wrong numberPause the identity, verify assignment, and investigate the source list
Provider compliance noticePreserve evidence, correct the registration, and follow the provider process

Incident response

  1. Disable the affected number or campaign immediately.
  2. Preserve assignment records, DLT evidence, templates, logs, and recent changes.
  3. Contact the carrier or compliance owner with the affected identity and timestamp.
  4. Correct the underlying registration or source-data issue.
  5. Run a controlled verification call before restoring traffic.

Need implementation help?

Search the help center or talk with the OP26X telephony team.