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

# Slack Voice AI Integration Guide

> Connect DialNexa voice AI with Slack to route urgent call outcomes, assign callbacks, post concise summaries, and keep alerts actionable.

The **Slack voice AI integration** brings time-sensitive call outcomes to the team that can act on them. It should create focused, owned notifications, not a stream of full transcripts or low-value call alerts.

<Warning>
  A catalog page describes a possible workflow. It does not confirm that a native Slack connector is enabled in your workspace. Check **Integrations** in the DialNexa dashboard first. If Slack is not listed, use a custom function, agent webhook, or external automation service.
</Warning>

## When to use the Slack voice AI integration

Use Slack when:

* Sales, support, operations, or on-call teams coordinate work in Slack.
* Specific call outcomes need an immediate owner or callback.
* The alert can link to the system of record for full details.
* Channel routing rules prevent customer data from reaching broad audiences.

<Tip>
  **Best first workflow:** Post only qualified leads or urgent escalations to one monitored channel with the caller, reason, owner, deadline, and record link.
</Tip>

## Before you begin

Prepare the following:

* A published DialNexa agent that has already passed a basic test call.
* Access to the DialNexa workspace **Integrations** page.
* A Slack account with permission to read or update the required records.
* One test record that does not affect a live customer.
* A list of actions that can run automatically and actions that require human review.

## Choose how to connect Slack

| Connection method                                   | Use it when                                             | Important limit                                                             |
| --------------------------------------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------- |
| Workspace connector                                 | Slack appears in your DialNexa **Integrations** page    | Available actions and authentication depend on your workspace               |
| [Custom function](/docs/agent-settings/custom-functions) | The agent needs Slack data during the live conversation | Keep the request fast and return only the fields the agent needs            |
| [Agent webhook](/docs/api-access/agent-webhooks)         | Slack should receive a result after the call            | Your endpoint must authenticate, retry safely, and prevent duplicate writes |
| External automation                                 | The workflow spans Slack and several other systems      | Monitor the external workflow separately from the DialNexa call             |

## Build the Slack voice AI workflow

1. Define the exact event that starts the action, such as a confirmed booking, qualified lead, support escalation, or completed call.
2. Choose the connection method from the table above.
3. Map caller identity, the DialNexa call ID, the verified outcome, and the destination record ID.
4. Add a condition so uncertain, sensitive, destructive, or high-value changes go to a human-owned queue.
5. Store the destination record URL or ID with the call result so your team can trace the handoff.
6. Test success, no-match, duplicate, permission-error, and timeout cases before using live traffic.

## Data to map between DialNexa and Slack

* DialNexa call ID, call direction, status, and final outcome
* Caller name, phone number, email, and matched customer or account ID
* Structured fields collected during the call, including consent where required
* Short operational summary, requested next step, owner, and due date
* Transcript or recording link only when your privacy policy allows it
* Slack record ID, record URL, update timestamp, and integration result

## High-value Slack voice AI workflows

| Call outcome                       | Slack result                                    | Human control                                   |
| ---------------------------------- | ----------------------------------------------- | ----------------------------------------------- |
| Qualified lead needs fast response | Post to the sales channel and mention the owner | Avoid broad channel mentions by default         |
| Customer needs an urgent callback  | Post reason, priority, and deadline             | Make one person or queue responsible            |
| Repeated issue appears             | Notify the support or operations channel        | Link to evidence instead of posting transcripts |
| Routine call completes             | Keep it in the system of record                 | Do not create low-value Slack noise             |

## Verify the Slack integration

Run a test call and confirm that:

1. The message reaches the intended private or public channel for that data type.
2. It states the outcome, owner, deadline, and source-record link without posting the transcript.
3. Mentions are limited to people who must act.
4. The DialNexa call ID prevents duplicate alerts.
5. Routine calls remain out of Slack and failed urgent alerts use a monitored fallback.

## Troubleshoot Slack integration issues

| Problem                             | What to check                                                                                                                                     |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Slack is not shown in the dashboard | Use a custom function, webhook, or external automation service, or [request the integration](/docs/dashboard-integrations/requesting-new-integrations) |
| Authentication fails                | Reconnect the account and verify scopes, workspace ownership, and token expiry                                                                    |
| Message reaches the wrong channel   | Map each approved outcome to one channel ID and review channel access                                                                             |
| Duplicate alerts appear             | Use the DialNexa call ID as an idempotency key and make retries safe                                                                              |
| The live call becomes slow          | Move nonessential writes to a post-call webhook and keep live lookups small                                                                       |

## Related pages

* [DialNexa integrations overview](/docs/integrations/overview)
* [Connect dashboard integrations](/docs/dashboard-integrations/connecting-integrations)
* [Use integrations in agents](/docs/dashboard-integrations/using-integrations-in-agents)
* [Use integrations in workflows](/docs/dashboard-integrations/using-integrations-in-workflows)
* [Integration workflow tutorials](/docs/tutorials/integration-workflows)