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

# Workflow Versus Batch Call In DialNexa

> Compare DialNexa workflows and batch calls so users choose the right outbound automation model for campaigns, lead paths, retries, and integrations.

A DialNexa batch call is a list-based outbound campaign. A DialNexa workflow is a node-based automation that can call, wait, branch, run application actions, and store lead history. Choose based on whether you need a list run or a multi-step path.

<Tip>
  If your plan fits in a CSV plus retry rules, use Batch Calls. If it needs a map, use Workflows.
</Tip>

## Batch Calls And Workflows Compared

The difference is execution shape.

| Need                                | Batch Calls                                 | Workflows                                    |
| ----------------------------------- | ------------------------------------------- | -------------------------------------------- |
| Call many recipients once           | Excellent fit.                              | Possible, but often more setup.              |
| Retry unanswered calls              | Built into campaign retry settings.         | Requires workflow routing design.            |
| Wait before follow-up               | Limited to retry interval.                  | Use Time nodes with minutes, hours, or days. |
| Branch on outcomes                  | Mostly through exports and follow-up lists. | Use call outputs and Condition nodes.        |
| Send WhatsApp or email after a call | Not the core purpose.                       | Use Application nodes.                       |
| Debug one lead path                 | Use call logs and retry history.            | Use lead history graph and call logs.        |

## Choose Based On The Shape

<Tabs>
  <Tab title="Use Batch Calls">
    You have a recipient list, one agent, a clear campaign name, a schedule, and retry rules.
  </Tab>

  <Tab title="Use Workflows">
    A lead should move through calls, waits, conditions, application actions, converted state, or dropped state.
  </Tab>

  <Tab title="Use Both">
    Run a batch to collect first outcomes, then move selected leads into a workflow for longer follow-up.
  </Tab>
</Tabs>

## Decision Questions

<AccordionGroup>
  <Accordion title="Do I need node-level history?">
    Use workflows when you need to know exactly which path a lead followed.
  </Accordion>

  <Accordion title="Do I need only recipient status exports?">
    Batch Calls are simpler and faster for that.
  </Accordion>

  <Accordion title="Do I need integration actions between calls?">
    Use workflow Application nodes.
  </Accordion>

  <Accordion title="Do I need a campaign draft and CSV preview?">
    Use Batch Calls.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Batch Calls Overview" icon="list-checks" href="/batch-calls/overview">
    Use list-based outbound campaigns.
  </Card>

  <Card title="Workflow Builder Concepts" icon="workflow" href="/workflows/builder-concepts">
    Understand nodes and edges.
  </Card>

  <Card title="Lead History" icon="route" href="/workflows/lead-history-and-debugging">
    Debug lead paths.
  </Card>
</CardGroup>