Outbound Calls In DialNexa

Place and verify a DialNexa outbound call using a tested agent version, valid recipient number, and assigned Plivo or SIP route.

Outbound calls in DialNexa start from a number that has a published outbound agent version assigned. The call can be launched manually, through a batch campaign, workflow call node, or API request, depending on your setup.

If the recipient number is wrong, the agent can be perfect and still talk to nobody.

Before You Begin

Confirm KYC and outbound readiness, available balance, a valid Plivo or SIP route, a published outbound agent version, and a recipient who has agreed to receive the test call.

Outbound Requirements

Requirement	What to check
Outbound phone number	The selected number must exist, be active, and support outbound calling.
Outbound agent assignment	The number needs an outbound agent id and published version number.
Provider path	Plivo or a linked SIP path handles the call transport. Test the exact path before production.
Recipient format	Country selector and local digits must combine into a valid destination number.
Dynamic variables	Values used by prompt, voicemail, transfer, workflow, or post-call fields must be present.
Account readiness	Unverified workspaces can only call their registered number. See KYC And Outbound Readiness.

Plivo Versus SIP For Outbound

Path	Use it when	Watch for
Plivo outbound	You bought or manage the number through the public DialNexa number flow.	Compliance readiness, active number status, country support, and caller ID behavior.
SIP outbound	You route through linked SIP credentials.	Trunk registration, carrier behavior, audio quality, and transfer bridge behavior.

Place A Single Outbound Call

1. Choose the launch surface

   Use Phone Numbers when validating a specific number, or agent testing when validating a draft or selected agent behavior.

2. Select country and enter digits

   Enter numeric local digits and let the UI apply the country code.

3. Fill required variables

   Use production-like values for caller name, amount, city, appointment time, plan, or any fields referenced by the prompt.

4. Make the call

   Wait for initiation confirmation and avoid launching duplicates while the first request is pending.

5. Open Call History

   Review status, end reason, transcript, recording, summary, extracted fields, transfer, and integration actions.

Outbound Failure Patterns

No outbound agent on number

Assign a published outbound agent version in Phone Numbers before starting a call, batch, or workflow call node.

Wrong script used

Check the exact published version assigned to outbound routing. Draft changes do not automatically affect live calls.

Call did not pick

Review status and retry strategy before changing the agent. A no-answer call is not a prompt bug.

Agent says blank or placeholder values

Check dynamic variables and CSV columns. The model can only speak the data it receives.

Verify The Outbound Call

Open Call History and confirm the direction, route, agent version, final status, end reason, transcript, and recording. A successful request is not enough if the call used the wrong version or produced an unusable conversation.

Related Reading

Phone Numbers

Assign outbound versions.

Batch Calls

Scale outbound calls to CSV lists.

SIP Trunking

Route through linked SIP credentials.

Testing Agents

Test a single agent version.