> ## 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.

# Outbound Calls In DialNexa

> Understand DialNexa outbound calls, Plivo and SIP call paths, single-call launch, recipient validation, country codes, outbound agent assignment, dynamic variables, and call review.

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.

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

## 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](/platform/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

<Steps>
  <Step title="Choose the launch surface">
    Use Phone Numbers when validating a specific number, or agent testing when validating a draft or selected agent behavior.
  </Step>

  <Step title="Select country and enter digits">
    Enter numeric local digits and let the UI apply the country code.
  </Step>

  <Step title="Fill required variables">
    Use production-like values for caller name, amount, city, appointment time, plan, or any fields referenced by the prompt.
  </Step>

  <Step title="Make the call">
    Wait for initiation confirmation and avoid launching duplicates while the first request is pending.
  </Step>

  <Step title="Open Call History">
    Review status, end reason, transcript, recording, summary, extracted fields, transfer, and integration actions.
  </Step>
</Steps>

## Outbound Failure Patterns

<AccordionGroup>
  <Accordion title="No outbound agent on number">
    Assign a published outbound agent version in Phone Numbers before starting a call, batch, or workflow call node.
  </Accordion>

  <Accordion title="Wrong script used">
    Check the exact published version assigned to outbound routing. Draft changes do not automatically affect live calls.
  </Accordion>

  <Accordion title="Call did not pick">
    Review status and retry strategy before changing the agent. A no-answer call is not a prompt bug.
  </Accordion>

  <Accordion title="Agent says blank or placeholder values">
    Check dynamic variables and CSV columns. The model can only speak the data it receives.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Phone Numbers" icon="phone" href="/calls/phone-numbers">
    Assign outbound versions.
  </Card>

  <Card title="Batch Calls" icon="list-checks" href="/batch-calls/overview">
    Scale outbound calls to CSV lists.
  </Card>

  <Card title="SIP Trunking" icon="radio" href="/calls/sip-trunking">
    Route through linked SIP credentials.
  </Card>

  <Card title="Testing Agents" icon="phone-call" href="/agents/testing-agents">
    Test a single agent version.
  </Card>
</CardGroup>