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

# Juicebox for Slack

> Bring Juicebox notifications and profile actions into the Slack channels where your recruiting team already collaborates.

## Overview

Recruiters and hiring managers already coordinate on roles in Slack, but candidate profiles live in other tabs.

Juicebox for Slack closes that gap: connect a Project or Agent to the channel where the team works, and updates show up at the right time — right in the thread, ready to act on.

Juicebox for Slack lets you:

* **Notify, answer, and act** on existing projects, sequences, and Agents
* **Review and surface leads** produced by an existing Agent or shortlist
* **Act faster** on common actions — especially on mobile

## Set up in three steps

<Steps>
  <Step title="Connect Slack to Juicebox">
    Navigate to the **Integrations** tab and connect the Slack integration to Juicebox. This creates a single workspace connection.
  </Step>

  <Step title="Link a project or Agent">
    From the **Projects** page, connect the relevant project to the Slack channel where the team collaborates on that role.
  </Step>

  <Step title="Tag @Juicebox in the slack channel">
    Get started by asking Juicebox what it can do in Slack.

    Type:

    ```text theme={null}
    @Juicebox, what can you do?
    ```

    Juicebox will be added to the Slack channel and will now surface notifications, project updates, and shortlist review requests in that channel.
  </Step>
</Steps>

## Core capabilities

### Review leads directly in Slack channels

When a review is requested, Slack posts a candidate carousel: approve, skip, or reject each profile.

* Add context during the decision; feedback syncs back and informs the Agent's learning and the platform.
* Carousels hold up to 10 cards, and press **See More** to generate more profiles at the end of the carousel.
* Shortlist reviews and Agent leads follow the same flow.

### Get project and sequence notifications

Once a Project is connected to a Slack channel, activity shows up in that channel:

* New Agent leads ready for review, or interested replies from an email sequence
* Project activity such as name changes or collaborators being added or removed
* Project activity summaries on a configurable cadence

You can also chat directly with Juicebox in Slack to get project notifications and status updates.

### Ask @Juicebox for project and Agent analytics

Tag `@Juicebox` in your Slack Chat to get quick answers without navigating dashboards:

* Pending, approved, or reviewed lead counts at a glance
* Outreach volume — how many people contacted or added to a sequence
* Pipeline, project, Agent, or sequence health, answered in the thread
* What happened to a profile after it was approved

### Manage notifications from Slack

Configure which Juicebox notifications a channel receives without leaving Slack. In any channel connected to a project or Agent, run:

```text theme={null}
@Juicebox settings
```

Juicebox posts a launcher that opens an in-Slack configuration modal for the projects and Agents linked to that channel. From the modal you can:

* **Mute all notifications** for the project or Agent in this channel
* **Choose which notification groups fire** — for example, new leads, sequence replies, or project activity

Changes made in Slack stay in sync with the notification settings on the web, so you can manage the same connection from either surface. Muting keeps your group selections intact, so unmuting restores your previous choices. The project activity summary schedule (daily, weekly, or monthly digest) is unchanged and continues to follow the cadence set in Juicebox.

Before the modal opens or a change is saved, Juicebox checks that your Slack account is linked to a Juicebox user and that you have permission to manage the project or Agent. If you don't, Juicebox posts a private message in the channel explaining why instead of opening the modal.

### Take profile actions and create tasks

Manage profiles and follow-up straight from Slack:

* Add a **note** or update **tags** on a profile
* Create a **reminder or task** and assign it to a teammate in the channel — the assignee is tagged in Slack, and the task and note live in Juicebox
* Share a **LinkedIn URL** and add it straight to a project shortlist

### Archived Slack channels

If a Slack channel linked to a Juicebox project or Agent is archived, Juicebox marks the connection inactive and stops sending notifications to that channel. Your notification preferences and the connection record are preserved. To resume delivery with the same settings, reconnect the project or Agent to a channel from the **Projects** page.

## Actions to try in Slack

| Action                | Example prompt                                                               |
| --------------------- | ---------------------------------------------------------------------------- |
| Notification settings | `@juicebox settings`                                                         |
| Lead review           | `@juicebox, show me the pending leads for [Agent].`                          |
| Agent status          | `@juicebox, how is [Agent] doing?`                                           |
| Approvals             | `@juicebox, how many leads did we approve this week for [Project]?`          |
| Outreach              | `@juicebox, how many people have we contacted in [Sequence]?`                |
| Profile history       | `@juicebox, what happened to [Profile] after we approved them?`              |
| Shortlist add         | `@juicebox, add this LinkedIn profile to the shortlist for [Project].`       |
| Pipeline health       | `@juicebox, what is the current health of [Project]?`                        |
| Task                  | `@juicebox, assign [Teammate] a task to follow up with [Profile] by Friday.` |

## Slack permissions requested

When you connect Slack, Juicebox requests the following scopes:

| Permission               | Purpose                                                                                                            |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| `app_mentions:read`      | Detect when a user starts a request with @Juicebox, so Juicebox knows when to respond.                             |
| `assistant:write`        | Show Juicebox as a Slack AI assistant and show progress while it processes a request.                              |
| `channels:history`       | Read messages in public channels where Juicebox is present, so it can understand and answer requests.              |
| `channels:read`          | Identify public channels, so Juicebox can maintain the correct project-to-channel connection.                      |
| `channels:manage`        | Create a public channel when a user chooses to create one for a Juicebox project or Agent.                         |
| `channels:write.invites` | Invite selected project members to a public channel that Juicebox creates.                                         |
| `chat:write`             | Send replies, notifications, and review requests as Juicebox.                                                      |
| `chat:write.public`      | Send a message to a connected public channel when Juicebox is not yet a channel member.                            |
| `files:read`             | Read supported files shared where Juicebox is present, so it can use them when answering a request.                |
| `files:write`            | Upload files or images that Juicebox includes in a Slack response.                                                 |
| `groups:history`         | Read messages in private channels where Juicebox is present, so it can understand and answer requests.             |
| `groups:read`            | Identify private channels where Juicebox is present, so it can maintain the correct project-to-channel connection. |
| `groups:write`           | Create a private channel for a confidential Juicebox project or Agent.                                             |
| `groups:write.invites`   | Invite selected project members to a private channel that Juicebox creates.                                        |
| `im:history`             | Read direct messages with Juicebox, so it can understand the conversation and answer follow-up questions.          |
| `im:read`                | Identify direct-message conversations with Juicebox, so it can reply in the correct conversation.                  |
| `im:write`               | Start a direct message when Juicebox must send a private response.                                                 |
| `links:read`             | Detect Juicebox links in messages, so it can determine whether a preview is available.                             |
| `links:write`            | Show a preview for supported Juicebox links.                                                                       |
| `mpim:history`           | Read group direct messages where Juicebox is present, so it can understand and answer requests.                    |
| `mpim:read`              | Identify group direct messages where Juicebox is present, so it can reply in the correct conversation.             |
| `reactions:read`         | Read reactions on Juicebox messages, so it can recognize existing feedback or status.                              |
| `reactions:write`        | Add or remove a reaction to acknowledge a request or show its status.                                              |
| `users:read`             | Identify Slack members, so Juicebox can use the correct names, mentions, assignments, and invitations.             |
| `users:read.email`       | Match a Slack member to the correct Juicebox user for access checks, assignments, and invitations.                 |

## Best practices

* The integration creates one workspace connection, but supports unlimited Slack channel to project or Agent mappings. We recommend **one channel per project or Agent**, though some teams put everything in a single channel.
* Notifications are scoped to the channel — anyone in the channel gets them. Some notifications (project renamed, collaborators added or removed) can't be disabled. The project activity summary has a configurable cadence — it defaults to weekly, and can be set to daily or monthly.
* You only need to tag `@Juicebox` when starting a new thread, not on every message within the thread.
* DMing Juicebox directly works for status and analytics questions, and works for users without a Juicebox seat (view-only). Lead review cannot happen in DMs.
