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

# Slack

> Connect Slack so your agent can chat with employees and notify technicians.

The Slack integration installs the Rallied.ai bot into your client's Slack workspace. Once connected, employees can message the agent directly or mention it in a channel, and the agent responds in real time. Technicians receive approval requests as Slack DMs and can approve or deny without leaving Slack.

<Note>
  Slack is configured in **MSP Settings → Integrations**.
</Note>

## How to connect

<Steps>
  <Step title="Open the Integrations tab">
    Navigate to **MSP Settings → Integrations** in the Rallied.ai dashboard.
  </Step>

  <Step title="Connect Slack">
    Find the Slack card and click **Connect**. A Slack authorization window opens.
  </Step>

  <Step title="Authorize the bot">
    Sign in to the client's Slack workspace and grant Rallied.ai the requested permissions. The bot is installed automatically once you approve.
  </Step>

  <Step title="Confirm the connection">
    The Slack card shows **Connected**. The bot is now present in the workspace and the agent can send and receive messages.
  </Step>
</Steps>

## What the agent can do

Once Slack is connected, the agent gains the following tools in that client's workspace:

| Tool                         | Default policy  | Description                                                          |
| ---------------------------- | --------------- | -------------------------------------------------------------------- |
| `slack:list-users`           | Auto            | List workspace members with profile details, email, and admin status |
| `slack:lookup-user-by-email` | Auto            | Find a Slack user by email address                                   |
| `slack:get-user-info`        | Auto            | Get detailed profile for a user by their Slack ID                    |
| `slack:list-channels`        | Auto            | List channels in the workspace with membership status                |
| `slack:send-message`         | Auto            | Send a message to a channel or open a DM with a user                 |
| `slack:update-message`       | Auto            | Update an existing message                                           |
| `slack:set-channel-topic`    | Auto            | Set the topic of a channel                                           |
| `slack:get-reactions`        | Auto            | Read emoji reactions on a specific message                           |
| `slack:invite-to-channel`    | Approval needed | Invite one or more users to a channel                                |

## How employees interact with the agent

Employees can reach the agent in two ways:

* **Direct message** — employees send a DM to the Rallied.ai bot. The agent responds in the same thread and continues the conversation until the issue is resolved.
* **Channel mention** — employees mention the bot in any channel (`@Rallied`). The agent responds in a thread on that message.

The agent reads the employee's request, diagnoses the issue, and takes action using the tools available from all connected integrations (Microsoft 365, Jira, RMM, etc.).

## Approval notifications via Slack

When the agent's plan includes a step that requires technician approval, a DM is sent to the assigned technician in Slack. The message describes the proposed action and includes an approve or deny option.

Technicians reply to the DM to approve or deny. A reply of "approve" (or similar affirmative) approves the request; "deny" (or similar negative) rejects it. The agent detects the intent automatically — the technician does not need to use a specific command.

<Tip>
  If you have both Jira and Slack connected for a client, approval requests are posted as a Jira comment **and** sent as a Slack DM simultaneously. Technicians can approve from either channel.
</Tip>

## After approval is resolved

If a technician approved or denied via Slack for a ticket that originated in Jira or another ticketing integration, Rallied.ai posts a back-channel note on the original ticket documenting who resolved the approval and when. This keeps your ticket history accurate regardless of which channel the technician used.

## Policies

All Slack tools that send or modify messages default to **auto** — the agent can use them without requesting approval. The `invite-to-channel` tool defaults to **approval needed** because it changes workspace membership.

You can adjust any of these defaults from the **Policies** tab on the client's settings page.