Skip to main content
DialNexa KYC and outbound readiness determine whether a workspace can use some outbound calling features at scale. In the dashboard, Batch Calls can be locked until KYC is verified, and outbound recipient entry can show account-readiness guidance. DialNexa Phone Numbers page showing a KYC verification required banner for Batch and Outbound Calls.
If Batch Calls are locked, changing the CSV will not help. The gate is account readiness, not comma placement.

​
Where KYC Shows Up

KYC state appears where outbound activity could create risk or spend.
SurfaceBehavior
Sidebar Batch CallsBatch Calls can be disabled with a tooltip explaining that KYC verification is required.
Phone number outbound modalRecipient input can be locked or guided when account readiness is incomplete.
Campaign launchOutbound campaigns should only be started when the workspace is ready.
Operations planningTeams should verify readiness before preparing large recipient files.

​
Prepare For Outbound Calls

1

Complete workspace readiness

Follow the KYC prompt or account guidance available in the dashboard.
2

Assign an outbound agent

Open Phone Numbers and attach a published agent version to the outbound number.
3

Run a single test call

Use the phone number or agent test call before launching a batch.
4

Start with a small campaign

Upload a small CSV, confirm results in Call History, then scale.

​
Readiness Problems And Meaning

The workspace is not verified for that feature yet.
The workspace may not have an active number with an outbound agent assigned.
Check the outbound phone number and published agent version.
Read the account-readiness message before changing call settings.

Phone Numbers

Assign outbound routing.

Outbound Calls

Place individual outbound calls.

Batch Calls Overview

Launch campaigns when ready.