> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# DialNexa KYC And Outbound Readiness

> Understand DialNexa KYC and outbound readiness, including why Batch Calls may be locked and how KYC affects recipient entry and campaign launch.

DialNexa KYC and outbound readiness determine whether a workspace can use outbound calling features such as Batch Calls, outbound recipient entry, and phone number purchase flows. The Phone Numbers page shows every workspace member the current KYC state and the action needed to submit, resubmit, or request reuse of an existing verified compliance.

![DialNexa Phone Numbers page showing a KYC verification required banner for Batch and Outbound Calls.](https://mintcdn.com/dialnexa/0efoAN-6So4r-6NC/images/documentation/screenshots/kyc-banner.png?fit=max\&auto=format\&n=0efoAN-6So4r-6NC\&q=85\&s=579003753221064c36ec15b2c5c9f857)

> [!WARNING]
>
> If a batch refuses most of your recipients before KYC is verified, changing the CSV will not help. Until KYC is verified, a batch on a non-SIP number can only call the workspace owner's registered phone number; verification is what lifts the limit.

## DialNexa KYC And Outbound Readiness Checks

KYC state appears where outbound activity could create risk or spend.

| Surface | Behavior |
| - | - |
| Phone Numbers page | Every workspace member sees a KYC banner with the current state: not requested, pending review, or rejected. |
| KYC modal | Workspace members can enter the company legal name, upload required documents, accept the terms, and submit for review. |
| Batch Calls | Batch Calls stays available. Until KYC is verified, a batch on a non-SIP number can only call the workspace owner's registered phone number; other recipients are refused. |
| 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 | For Plivo, US number purchase requires completed KYC. India number purchase also requires a compliance ID attached to the workspace by DialNexa. Vobiz uses its separate verification. |
| Existing compliance reuse | If the owner already has a verified compliance in another workspace, the modal can request manual attachment by the DialNexa team. |

## Provider-Specific KYC

Open **Workspace settings > Telephony > KYC** to review each provider separately. Plivo verifies the uploaded company documents. Vobiz verifies business PAN and GST details. Approval for one provider does not verify the other. If Plivo KYC is verified and Vobiz KYC is incomplete, pending, or needs an update, **Phone Numbers** shows the Vobiz banner with its status and any available action. Verified Vobiz KYC also satisfies the workspace’s outbound-recipient verification check; number purchase still follows the selected provider’s own requirements.

![DialNexa Telephony KYC tab showing Plivo verified and Vobiz incomplete with a Complete KYC action.](https://mintcdn.com/dialnexa/vwQQR1ZbzSdywJOy/images/documentation/screenshots/workspace-telephony-kyc.png?fit=max\&auto=format\&n=vwQQR1ZbzSdywJOy\&q=85\&s=0f96c64f47302ba491e85976928e5b07)

For Plivo, choose **Complete KYC**, or **Resubmit documents** after rejection, and follow the document flow below. The Phone Numbers page also offers the relevant verification action.

For Vobiz, choose **Complete KYC** on its card. Select the business type and enter the business PAN and GST number requested by the form. The GST number must belong to that PAN, and the PAN must match the selected registered-business type. Submit only accurate business information, then check the provider’s verification status.

A failed Vobiz submission does not replace the Plivo verification state. Correct the business details or follow the displayed provider message, use **Resubmit details**, then check the status again before trying to use a Vobiz number.

## Complete Plivo KYC Verification

**1. Open Phone Numbers**

Go to Phone Numbers and use the KYC banner action. Members see **Start Verification** when KYC has not been requested and **Resubmit Documents** when a previous submission was rejected.

**2. Enter the company legal name**

Use the legal company name that matches the documents you are uploading.

**3. Upload registration proof**

Upload the registration certificate, such as COI or Udyam, as a PDF, PNG, or JPG file up to 5 MB.

**4. 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.

**5. Accept the terms and submit**

Read the **Terms & Compliance Requirements** block, accept the checkbox, and submit. After submission, the status moves to pending review. DialNexa emails the owner when review is approved or rejected.

Pending review usually completes within 1 business day. While review is pending, the banner explains that the team is verifying the documents and that the owner will receive an email after approval.

## Terms And Compliance Requirements

The KYC modal includes a scrollable **Terms & Compliance Requirements** block before submission. The submitting member 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 | A batch on a non-SIP number can call only the workspace owner’s registered phone number until the relevant verification is complete. |
| 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 DialNexa has attached the workspace's compliance ID. |

## After KYC Approval: Replace The Default Number

The KYC dialog warns that approval removes the shared default number from the workspace. Plan to purchase your own phone number for calling after approval. Check **Phone Numbers**, assign the required published agent version, and verify the route before starting a batch.

The notice also appears when resubmitting KYC or requesting reuse of an existing compliance. Approval does not automatically buy a replacement number.

## Phone Number Purchase Compliance

For Plivo numbers, 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 | Complete workspace KYC verification and have DialNexa attach the Indian compliance ID. |

If a user cannot search for numbers, check the selected country first. A blocked US search usually means KYC is not complete. A blocked India search can mean KYC is incomplete, the workspace has no attached Indian compliance ID, or both. A verified workspace without that ID sees **IN numbers need a compliance ID**. Contact support to attach it; do not resubmit KYC when the workspace is already verified. US number purchase and verified outbound calling remain available.

## Prepare For Outbound Calls

**1. Verify KYC first**

Complete KYC before preparing production campaigns or buying new outbound numbers.

**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

> [accordion] Batch upload refuses recipients
>
> Until KYC is verified, a batch on a non-SIP number can only call the workspace owner's registered phone number. Complete KYC, or use a SIP number, before uploading other recipients.

> [accordion] No outbound number appears
>
> The workspace may not have an active number with an outbound agent assigned.

> [accordion] Campaign has no eligible route
>
> Check the outbound phone number and published agent version.

> [accordion] Recipient input is blocked
>
> Check whether KYC is verified and whether the selected number is a non-SIP outbound number.

> [accordion] KYC review was rejected
>
> Read the rejection reason, correct the documents, and resubmit from the Phone Numbers page.

## Related Reading

> [card] [Phone Numbers](https://dialnexa.com/docs/calls/phone-numbers.md)
>
> Assign outbound routing.

> [card] [Outbound Calls](https://dialnexa.com/docs/calls/outbound-calls.md)
>
> Place individual outbound calls.

> [card] [Batch Calls Overview](https://dialnexa.com/docs/batch-calls/overview.md)
>
> Launch campaigns when ready.

> [card] [KYC Video Tutorial](https://dialnexa.com/docs/tutorials/platform-videos/complete-kyc.md)
>
> Watch the account verification walkthrough.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.