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

# Common DialNexa Voice AI Use Cases

> Review common DialNexa Voice AI use cases such as lead qualification, appointment booking, reminders, support intake, surveys, and workflow follow-up.

Common DialNexa Voice AI use cases show how agents, phone numbers, batch calls, workflows, integrations, and monitoring fit into real operating patterns. Use this page to choose the product path that matches the user's outcome before configuring the dashboard.

<Tip>
  The fastest way to build the wrong agent is to make one agent do six unrelated jobs. Give each job a clean home unless the call script truly belongs together.
</Tip>

## Use Case To Product Path

Start with the path that matches the operational goal. For the same scenarios viewed through provider and stack choices, see the [Voice AI Overview](/voice-ai/overview).

| Use case                    | Recommended product path                                                                                        | Main evidence to review                                                 |
| --------------------------- | --------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- |
| Lead qualification          | Single Prompt Agent or Conversational Flow Agent, outbound number, post-call fields, CRM or owner notification. | Qualification result, transcript, sentiment, duration, extracted fields |
| Appointment booking         | Agent function for booking, inbound or outbound number, confirmation message.                                   | Booked slot, function result, call summary                              |
| Payment or renewal reminder | Batch Call with CSV variables, retry settings, call outcome export, follow-up message.                          | Completed calls, did not pick rows, failed rows, retry history          |
| Support intake              | Inbound number, triage prompt, post-call fields, support handoff.                                               | Issue summary, escalation flag, recording                               |
| Multi-step follow-up        | Workflow with call nodes, condition nodes, time nodes, and application nodes.                                   | Lead history, node transitions, application success or failure          |

## Common Integrations By Use Case

| Use case                    | Helpful connections                                                                                                                            | Why                                                                |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| Lead qualification          | [HubSpot](/integrations/hubspot), [Salesforce](/integrations/salesforce), [Slack](/integrations/slack).                                        | Send qualified context to the owner while the call is still fresh. |
| Appointment booking         | [Google Calendar](/integrations/googlecalendar), [Gmail](/integrations/gmail), [Resend](/integrations/resend).                                 | Confirm the booked time in writing.                                |
| Payment or renewal reminder | [Stripe](/integrations/stripe), [Google Sheets](/integrations/googlesheets), [WhatsApp with Wati](/dashboard-integrations/whatsapp-with-wati). | Check payment context, review exceptions, and send follow-ups.     |
| Support intake              | [Zendesk](/integrations/zendesk), [Intercom](/integrations/intercom), [Google Sheets](/integrations/googlesheets).                             | Move issue context to the team that will handle it.                |
| Ecommerce order follow-up   | [Shopify](/integrations/shopify), [Gmail](/integrations/gmail), [Slack](/integrations/slack).                                                  | Combine order context, written updates, and internal alerts.       |

## Reusable Building Blocks

Most use cases are combinations of these product pieces.

<CardGroup cols={2}>
  <Card title="Prompt and welcome message" icon="message-square" href="/agents/prompts-and-welcome-messages">
    Tell the agent what to do, how to speak, and who starts the conversation.
  </Card>

  <Card title="Dynamic variables" icon="braces" href="/agents/dynamic-variables">
    Personalize calls with values such as name, due date, location, plan, or assigned representative.
  </Card>

  <Card title="Post-call analysis" icon="list-checks" href="/agent-settings/post-call-analysis">
    Turn a conversation into structured fields that appear in call details and exports.
  </Card>

  <Card title="Retries" icon="refresh-cw" href="/batch-calls/retries-and-statuses">
    Retry failed or unanswered calls in batch campaigns, then inspect retry chains in Call History.
  </Card>
</CardGroup>

## Pick The Shape Of The Conversation

<Tabs>
  <Tab title="One clear objective">
    Use a Single Prompt Agent for a call that can be handled by one instruction set: qualify, remind, collect feedback, or answer a narrow FAQ.
  </Tab>

  <Tab title="Branching script">
    Use a Conversational Flow Agent when the call needs defined branches, transfer nodes, representative briefing, or an explicit end path.
  </Tab>

  <Tab title="Automation after the call">
    Use a Workflow when the lead should move across nodes, waits, conditions, application messages, and call attempts over time.
  </Tab>
</Tabs>

## Use Case Design Checks

<AccordionGroup>
  <Accordion title="Can the agent succeed without external data?">
    If not, add dynamic variables, functions, integrations, or a knowledge source before testing.
  </Accordion>

  <Accordion title="What is the success field?">
    Create a post-call field that tells operations whether the call achieved its purpose.
  </Accordion>

  <Accordion title="What happens if the person does not answer?">
    Use batch retry rules or workflow routing instead of hoping the first call works.
  </Accordion>

  <Accordion title="What should users audit later?">
    Make sure the expected proof appears in Call History: transcript, recording, summary, extracted fields, transfer data, or export columns.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Single Prompt Agents" icon="sparkles" href="/agents/single-prompt-agents">
    Use one instruction set for one goal.
  </Card>

  <Card title="Conversational Flow Agents" icon="git-branch" href="/agents/conversational-flow-agents">
    Use explicit branches and call paths.
  </Card>

  <Card title="Batch Calls" icon="list-checks" href="/batch-calls/overview">
    Run list-based outbound campaigns.
  </Card>

  <Card title="Workflows" icon="workflow" href="/workflows/overview">
    Automate multi-step follow-up.
  </Card>
</CardGroup>