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

# Integrations Overview

> Connect DialNexa to your CRM, scheduling, support, messaging, billing, and analytics tools. Pick a starting point by business use case and grow your stack from there.

DialNexa connects to hundreds of third-party tools, but most teams only need a focused stack to launch quickly. The right integration is usually the one closest to where your team already writes call outcomes today: the CRM that owns the customer record, the calendar that holds the next meeting, the helpdesk that gets the resulting ticket, or the chat tool where the team gets notified. This page groups the most-used integrations by business use case so you can choose a starting point without scanning the full catalog.

## How DialNexa integrations work

Every DialNexa integration falls into one of three roles in a call workflow:

1. **Source systems** trigger calls or supply context. A CRM stage change, a form submission, a scheduled job, or an inbound webhook tells DialNexa to place a call, and the integration provides the customer data the agent will personalize with.
2. **Destination systems** receive call outcomes. After the call ends, DialNexa writes the structured result (qualified, booked, refused, needs follow-up) back into the system where humans actually work on next steps.
3. **Operational systems** observe call activity in real time. Messaging, alerting, and analytics integrations push notifications, summaries, and metrics to the people who need them.

Most production deployments combine all three roles. The fastest path to value is picking one source system and one destination system first, validating the end-to-end loop, then expanding.

## Recommended starting points

<CardGroup cols={3}>
  <Card title="CRM & lead management" icon="users" href="/integrations/salesforce">
    Route call outcomes, notes, and follow-ups into your CRM.
  </Card>

  <Card title="Common workflows" icon="workflow" href="/tutorials/integration-workflows">
    Combine CRM, scheduling, support, messaging, and reporting tools into complete call workflows.
  </Card>

  <Card title="Scheduling & booking" icon="calendar" href="/integrations/calendly">
    Let AI calls capture availability and book meetings automatically.
  </Card>

  <Card title="Support operations" icon="life-buoy" href="/integrations/zendesk">
    Convert call summaries into tickets and trigger escalations.
  </Card>

  <Card title="Messaging & notifications" icon="message-square" href="/integrations/slack">
    Push live call alerts and post-call summaries to your team.
  </Card>

  <Card title="Billing & payments" icon="credit-card" href="/integrations/stripe">
    Automate payment links, status checks, and collection workflows.
  </Card>

  <Card title="Data & reporting" icon="bar-chart-3" href="/integrations/googlebigquery">
    Sync call events for dashboards, QA, and revenue reporting.
  </Card>
</CardGroup>

## What a good integration page tells you

Each provider page in this section is written to help you decide whether and how to use the integration. Expect to see:

* Where the tool fits in a DialNexa call workflow (source, destination, or operational).
* What customer or operational data DialNexa should capture and pass along.
* High-value workflow patterns that use the integration end-to-end.
* The structured handoff DialNexa writes back, including identity, request, owner, urgency, and links to call evidence.
* Notes on sensitive data, routing for human review, and any compliance considerations.

If the tool you need is not in the recommended cards above, browse the full **Integrations** section in the left navigation. Pages are listed alphabetically by provider name.

## Picking your first integration

Three rules of thumb make first integrations succeed:

1. **Start where the outcome already lives.** Pick the destination system humans on your team already use to track customer follow-ups. Writing call outcomes back into a tool people watch is what makes the automation visible.
2. **Pick one source and one destination first.** Resist the urge to wire up every tool at once. End-to-end visibility on one path beats partial coverage across five.
3. **Decide your review boundary early.** Which call outcomes complete fully automatically? Which create a human-owned task or ticket? That boundary is what keeps automation useful without hiding sensitive exceptions like opt-outs or unusual account states.

## Related pages

* [Common workflows](/tutorials/integration-workflows) for end-to-end patterns that combine multiple integrations.
* [Tutorials overview](/tutorials/overview) for the principles behind picking and launching a workflow.
* [Common use cases](/common-use-cases) for high-level patterns mapped to business outcomes.
* [Dashboard integrations overview](/dashboard-integrations/overview) for the dashboard-native integration experience.