> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Slack

> Connect a Slack workspace so people can mention @OpenCX for AI answers in threads, and get handoff notifications in a Slack channel you choose.

Connect a Slack workspace to OpenCX for two separate jobs: people in your Slack workspace can mention **@OpenCX** in a channel and get an AI answer in the thread, and OpenCX can post a notification to a Slack channel whenever a session is handed off to your team. You can use either one without the other.

> [!NOTE]
>
> **[Channels → Slack](https://platform.open.cx/channels/slack)** in your OpenCX dashboard. Viewing the page needs the **Channels settings** read permission. Connecting, changing settings and removing the bot need the write permission.

## Mentions and notifications are different

| | AI answers to mentions | Handoff notifications |
| - | - | - |
| Who writes in Slack | People in your Slack workspace | OpenCX |
| What it creates | A session in the inbox for each thread | Nothing new; the post links to the existing session |
| Which sessions | Threads where **@OpenCX** was mentioned | Every handoff, whichever channel the session came from |
| Controlled by | **Respond to mentions** | **Notification channel** and **Notify assignee on handoff** |

Slack is for your own team, not for customers outside your workspace. In **Settings → Autopilot**, the Slack row can't be changed and notes: "Right now Slack is only available for your internal team members, not for shared channels."

## Connect your workspace

**1. Start the connection**

Go to **[Channels → Slack](https://platform.open.cx/channels/slack)** and click **Connect**. Slack asks you to approve the OpenCX app for your workspace. You may need permission to install apps in that workspace.

**2. Approve the app**

Accept every permission Slack lists. You return to the Slack page, which shows **Connected to** and your workspace name.

**3. Invite the bot to channels**

In Slack, invite **@OpenCX** to each public or private channel where people should be able to ask it questions, and to the channel you want notifications in. Back in OpenCX, click **Refresh** under **Active channels** to see the updated list.

**Active channels** lists every channel the bot is in, with its visibility. To take the bot out of a channel, use **Remove bot from #channel** on that row; the bot leaves the channel in Slack.

OpenCX connects to one Slack workspace at a time. To switch workspaces, click **Disconnect** and connect again. Disconnecting clears the notification channel and both switches, which return to their defaults when you reconnect.

## How the AI answers in Slack

With **Respond to mentions** on, which is the default after connecting, the AI answers:

* A message that mentions **@OpenCX** in a channel where the bot is present. The answer goes in that message's thread.
* Follow-up messages in a thread where the AI already has a session, without another mention.

While it works, OpenCX adds 👀 to the message and posts *Thinking...* in the thread. Both disappear when the answer arrives. Answers come from the same knowledge and actions the AI uses on your other channels.

OpenCX ignores message edits and deletions, messages that share a file, messages with no text, and messages from [blocked contacts](https://platform.open.cx/settings/autopilot). Messages from other Slack apps and workflows get an answer only when each one mentions **@OpenCX**, even inside an existing thread.

Turning **Respond to mentions** off stops the bot from reading messages at all: no answers, no new sessions, and follow-ups in existing threads are not added to their sessions. Handoff notifications keep working.

## Slack sessions in the inbox

Each Slack thread is one session in the [inbox](https://platform.open.cx/inbox). Its contact is the Slack user whose message opened the session, created from their Slack profile name, email and photo.

When a teammate replies from the inbox, the reply is posted in the same thread. It shows the teammate's Slack name and photo when their OpenCX email matches a Slack account in the workspace, and their OpenCX name and avatar otherwise. If the teammate has a customer-facing alias, or **Show agents' first names only** is on in [workspace settings](https://docs.open.cx/ticketing/workspace-settings.md), Slack shows that name instead.

Once a session is handed off or assigned to a teammate, the AI stops answering in its thread and your team takes over from the inbox. If Slack is turned on in **Settings → CSAT**, the [satisfaction survey](https://docs.open.cx/resources/csat.md) is posted in the thread with a rating link.

### Resolve a session from Slack

React with ✅ (`:white_check_mark:` or `:heavy_check_mark:`) to the top message of the thread. If the session is open, OpenCX resolves it and replies **Session resolved by @name** in the thread.

* If the Slack email of the person who reacted matches a teammate who could close the session from the inbox, the resolution is recorded as that teammate's and your workspace's close rules apply. When required fields are missing, the session stays open and the thread says what is missing.
* Otherwise, OpenCX resolves the session on its own.

The same reaction also works on a thread that a workflow's **Send Slack Message** step posted with a **Ticket Number**, for 72 hours after it was posted.

## Get handoff notifications

Under **Notification settings**, pick a **Notification channel**. The list shows the channels the bot is in, plus **Off (no notifications)**. From then on, every handoff posts a card to that channel with:

* **Organization**, **Assigned To** (or **Unassigned**), **Sentiment** and **Summary**.
* **Priority**: **High** when the customer's sentiment is angry, **Medium** otherwise.
* A **View in Dashboard** link and, for sessions that came from Slack, **Open Thread in Slack**.

The notification channel is internal. Replies in its threads never reach the customer; your team answers from the inbox. Mentioning **@OpenCX** there starts a new Slack session, the same as in any channel.

### Notify the assigned teammate

**Notify assignee on handoff** is on by default. While it is on, OpenCX:

* Sends the handoff card as a direct message to the teammate assigned at handoff, if there is one.
* Mentions that teammate in the Slack thread when the session came from Slack: "This conversation has been assigned to you."
* Sends a direct message whenever a session is reassigned to a teammate: "A conversation has been assigned to you."

OpenCX finds each teammate in Slack by their OpenCX email. A teammate without a Slack account on that email gets no message.

You can change this switch only while a notification channel is selected. Choosing **Off (no notifications)** stops the channel posts only: direct messages keep following the switch's last value.

## Troubleshooting

| Symptom | Likely cause | Fix |
| - | - | - |
| **Slack connection failed** after approving | The install was declined, a permission wasn't accepted, or you can't install apps in the workspace | Check with your Slack admin, then click **Try again** and accept every permission. |
| The bot doesn't answer a mention | **Respond to mentions** is off, the bot isn't in the channel, or the message shares a file | Turn the switch on, invite **@OpenCX** to the channel, or send the question as text. |
| **Notification channel** shows **Choose a channel** | The bot was removed from the saved channel, so notifications can't be posted | Invite **@OpenCX** back to that channel, or pick another one. |
| None of the above | — | Contact OpenCX support with the channel name and the time of the message. |

***

## Related Documentation

> [card] [Human Handoff](https://docs.open.cx/handoff/introduction.md)
>
> When and how the AI hands sessions to your team.

> [card] [Handoff Settings](https://docs.open.cx/handoff/settings.md)
>
> Transfer behavior, office hours and data collection.

> [card] [Autopilot Settings](https://docs.open.cx/safety/autopilot-settings.md)
>
> Per-channel AI switches and blocked contacts.

> [card] [CSAT Surveys](https://docs.open.cx/resources/csat.md)
>
> Ask for a rating when a session closes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.