---
lang: en
---

# Slack and Discord

Cactus's Slack and Discord bots answer questions about a product in those chats, and post a handoff card in an escalation channel when a person is needed. A linked teammate can claim, reply to, resolve or reopen the card from the chat.

> Verified against the product on 2026-11-20

## Connect Slack or Discord

Connect a Slack workspace on the Slack page of [Deploy](https://app.heycactus.ai/deploy/slack). Connect sends you to Slack to approve the app, and Slack brings you back to the page.

The app asks Slack for permission to post messages, read channels and direct messages, and read each user's email address.

A team has one Slack workspace connected. Connecting a new one replaces the old, and a workspace that belongs to another Cactus team is refused.

If Slack is not set up on the deployment, Connect answers that Slack isn’t available yet.

Once connected, the page reads “Connected to” the workspace's name. It reads “Joined” when the person who connected was also added to every channel Connect set up.

Connect a Discord server on the Discord page of [Deploy](https://app.heycactus.ai/deploy/discord). Until the server is connected, Cactus answers in it that the server isn’t connected to Cactus.

Escalations go to a channel the team picks on the same page: an “Escalation channel” in Slack and a “Discord escalation channel” in Discord. That channel also tells Cactus which product a message in it is about.

## Link your account

Discord and Slack do not share your Cactus sign-in, so Cactus matches each account to a teammate's by email. Only a linked teammate can ask Cactus for team-only answers, check status, or act on an escalation.

In Slack, `/cactus link` tells you that Cactus matches your Slack account to your Cactus account by email, and to log in at https://app.heycactus.ai with the address on your Slack profile.

A Slack user is a teammate when their Slack email matches a member of your team and they are a full member of the workspace, not restricted and not a stranger.

In Discord, `/cactus link` sends you a private link to a Cactus page.

That page is at https://app.heycactus.ai/link/discord, and it asks you to press **Confirm** before anything is linked. It needs you to be signed in to Cactus first.

Confirming links your Discord account to your Cactus account, and a link spends once.

A Discord account already linked to another Cactus account is refused. If it is already linked to yours, the link says so.

A linked Discord account on another team gets the published pages only.

## Ask Cactus in Slack

In a channel, Cactus answers a message that mentions it, or a reply inside a thread. It answers every direct message.

Three commands work in Slack: `/cactus ask <question>`, `/cactus status` and `/cactus link`. Any other `/cactus` gets a line listing them.

If the channel has no product, or the question names one of several and the channel doesn't pick one, Cactus gives a notice instead of an answer.

`/cactus status` is for teammates only. It says the product's name, its last build date or “Not built yet”, and how many escalations are open.

Each answer has thumbs buttons. A thumbs-down opens a form that asks for the reason, and each vote is kept.

## Ask Cactus in Discord

`/cactus` has five subcommands: `ask`, `status`, `link`, `reply` and `resolve`. A question can run to 6,000 characters.

In a server, Cactus hears a message that mentions it, and any message in a thread.

A message typed in Discord, rather than a slash command, reaches Cactus only while Cactus is connected to Discord.

Each person's question in a channel has its own conversation, so nobody reads another person's history.

A direct message is answered only for a linked teammate whose account is on one team with a server connected. Anyone else is told where to ask instead.

A mention with no question gets a one-line reply that names the product.

`/cactus status` is for a linked teammate on this server's team.

## Handoffs in Slack and Discord

When a conversation needs a person, Cactus posts a handoff card into the escalation channel and edits it as the conversation moves on.

The card's title says who was handed over, and its subtitle is the product's name with “Escalation”.

The buttons depend on the escalation's state.

| The card shows | Its buttons |
| --- | --- |
| An escalation nobody has claimed | **Claim**, **Reply…** and **Resolve** |
| An escalation a teammate has claimed | **Reply…** and **Resolve** |
| A cancelled escalation | **Reply…** |
| A closed escalation | **Reopen** and **Reply…** |

**Claim** gives the escalation to the teammate who pressed it. If someone already has it, the reply names them, and a closed escalation must be reopened first.

Only a teammate can press these buttons. In Slack a press by anyone else is refused with the teammate line. In Discord the press must come from a linked teammate on this server's team.

**Resolve** and **Reopen** act on the escalation at once. In Discord they answer “Resolved.” or “Reopened.”

### Replies to the visitor

**Reply…** opens a form. Whatever is typed there is sent to the visitor as the team's reply, and it reaches them the way a team reply does. Replies are read by visitors through [Handoffs](https://cactus.heycactus.ai/a5tamg-handoffs).

In Discord the receipt says “Sent to the visitor by” the teammate's name.

`/cactus reply` with the words does the same from inside an escalation thread, up to 2,000 characters. Outside a thread it is refused.

The card says “Reply… sends your words to the visitor. Messages in this thread stay with your team.”

### Notes in a handoff thread

A message in a handoff thread that does not mention Cactus is kept as a note for the team. It is not sent to the visitor.

In Slack only a full teammate's message is kept as a note. In Discord the message is kept once the teammate check on this server passes.

A teammate who mentions Cactus in a handoff thread asks it a question about that conversation.

### Asking for a person from an answer

A visitor on Discord can hand their conversation to the team from an answer, and only the person who asked can do it. Cactus confirms with “Escalated to the team.”

In Slack the same button works only for the person who asked.

## If something goes wrong

| What you see | What it means | What to do |
| --- | --- | --- |
| “Link your account with /cactus link first.” | You are not a linked teammate on this server's team. | Type `/cactus link` and confirm the link. |
| “Only a teammate can do that. Cactus knows you by the email address on your Slack profile: log in to Cactus with that address, or ask a teammate to add it to your team in Cactus.” | Your Slack email does not match a full member of the team. | Log in to Cactus with the address on your Slack profile. |
| “Only a linked teammate can ask Cactus in an escalation thread. Link your account with `/cactus link` first.” | You mentioned Cactus in a handoff thread without being a linked teammate. It is sent to you privately. | Link your account as above. |
| “_Name_ already has this one.” | Another teammate has claimed the escalation. | Ask that teammate, or wait for them to resolve it. |
| “That escalation is closed. Reopen it first if it needs somebody.” | The escalation was resolved. | Press **Reopen** on the card first. |
| “That escalation isn’t on this server.” | The escalation belongs to another server or team. | Press the card in the channel it was posted to. |
| “This server isn’t connected to Cactus. Connect it on the Discord page under Connect in Cactus.” | The server has no connection. | Connect the server on the [Discord page](https://app.heycactus.ai/deploy/discord). |
| “This Slack workspace is no longer connected to Cactus.” | The Slack connection was removed. | Connect the workspace again on the [Slack page](https://app.heycactus.ai/deploy/slack). |
| “This server is connected to Cactus, but no product is set up yet.” | The team has no product. | Set up a product first. [Setting up your first product](https://cactus.heycactus.ai/gg4aur-setting-up-your-first-product) |
| “Say which product in your question, or give this channel a product on the Discord page under Connect in Cactus.” | The channel has no product and the question names none. | Name the product, or bind the channel on the Discord page. |
| “Cactus couldn’t post in this channel. Invite it and try again.” | Cactus is not in the Slack channel. | Invite the Cactus app to the channel and try again. |
| “Cactus couldn’t take that. Try again in a moment.” | Cactus could not queue the press or the command. | Try again in a moment. |
| “Cactus answers in a server it’s connected to, not in a direct message. Ask in a channel of that server.” | You wrote to Cactus in a direct message from a server-less context. | Ask in a channel of the connected server. |
| “Your Discord account is linked, but not to a teammate of this server’s team. You get the published pages here.” | Your linked account is on another team. | Ask a teammate of this server's team. |
| “That workspace is already connected to another Cactus team.” | Another team holds the Slack workspace. | Ask the other team to disconnect it first. |
| “Only the person who asked can escalate this.” | Someone other than the asker pressed the escalation button on an answer. | Ask your question yourself to hand it to the team. |
