Where KYC Shows Up
KYC state appears where outbound activity could create risk or spend.| Surface | Behavior |
|---|---|
| Phone Numbers page | Workspace owners see a KYC banner with the current state: not requested, pending review, or rejected. |
| KYC modal | Owners can enter the company legal name, upload required documents, accept the terms, and submit for review. |
| Batch Calls | Batch Calls can be disabled until KYC is verified for the workspace. |
| Outbound recipient entry | If the workspace owner is not verified and the selected outbound number is not SIP, the dashboard can limit calls to the registered verification number. |
| Phone number purchase | US number purchase requires completed KYC. India number purchase requires completed KYC plus submitted compliance documentation. |
| Existing compliance reuse | If the owner already has a verified compliance in another workspace, the modal can request manual attachment by the DialNexa team. |
Complete KYC Verification
Open Phone Numbers
Go to Phone Numbers and use the KYC banner action. Owners see Start Verification when KYC has not been requested and Resubmit Documents when a previous submission was rejected.
Enter the company legal name
Use the legal company name that matches the documents you are uploading.
Upload registration proof
Upload the registration certificate, such as COI or Udyam, as a PDF, PNG, or JPG file up to 5 MB.
Upload tax proof
Upload the tax proof requested in the form, such as GST certificate or Business PAN, as a PDF, PNG, or JPG file up to 5 MB.
Terms And Compliance Requirements
The KYC modal includes a scrollable Terms & Compliance Requirements block before submission. The owner must confirm that they have read and agree to those requirements before the request can be submitted. The block explains that the workspace must follow applicable telecom rules, including TRAI and DoT requirements where relevant. It also reminds the owner that outbound calling must be lawful, recipient consent must be handled where required, opt-out requests must be honored, and misuse or non-compliance can lead to suspension or termination of telephony services.Use Existing Compliance
If the owner already has a verified compliance on another workspace, the KYC modal can show an option to use that existing compliance. Select that option, enter the company legal name, accept the terms, and submit the request. This does not instantly verify the current workspace. It creates a pending request so the DialNexa team can manually attach the existing verified compliance.Resubmit After Rejection
When KYC is rejected, the Phone Numbers page shows the rejection reason where available. Use Resubmit Documents to upload corrected files. Resubmission creates a fresh review request and moves the workspace back to pending status.Outbound Behavior Before Verification
Unverified workspaces can still have limited testing behavior, but production outbound readiness is restricted.| Route or feature | What to expect before verification |
|---|---|
| Batch Calls | The feature can stay locked until KYC is verified. |
| Non-SIP outbound number | A workspace owner who is not verified can be limited to the registered verification number in recipient entry. |
| SIP outbound number | SIP-linked outbound numbers do not use the same unverified-owner recipient input lock, but teams should still test routing and follow compliance requirements. |
| US phone number purchase | The country option is blocked until KYC verification is complete. |
| India phone number purchase | The country option is blocked until KYC verification is complete and compliance documentation is submitted. |
Phone Number Purchase Compliance
The Buy Phone Number modal can disable country choices when the workspace is not ready for that region. Hovering a disabled country explains the missing requirement, and the search button stays disabled until the selected country is purchase-ready. The modal also shows an inline warning for the selected country when search is blocked.| Country | Requirement before search |
|---|---|
| United States | Complete workspace KYC verification. |
| India | Submit compliance documentation and complete workspace KYC verification. |
Prepare For Outbound Calls
Assign an outbound agent
Open Phone Numbers and attach a published agent version to the outbound number.
Readiness Problems And Meaning
Batch Calls tab is disabled
Batch Calls tab is disabled
The workspace is not verified for Batch Calls yet. Complete KYC before retrying the campaign upload.
No outbound number appears
No outbound number appears
The workspace may not have an active number with an outbound agent assigned.
Campaign has no eligible route
Campaign has no eligible route
Check the outbound phone number and published agent version.
Recipient input is blocked
Recipient input is blocked
Check whether KYC is verified and whether the selected number is a non-SIP outbound number.
KYC review was rejected
KYC review was rejected
Read the rejection reason, correct the documents, and resubmit from the Phone Numbers page.
Related Reading
Phone Numbers
Assign outbound routing.
Outbound Calls
Place individual outbound calls.
Batch Calls Overview
Launch campaigns when ready.