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

# Route visitors to Slack

> Send identified Squid ID visitors to a Slack channel the moment they're recognized so your sales team can act on warm accounts without opening the dashboard.

When a visitor is identified, Squid ID posts an alert to Slack with their name, company, role, and the page they're on. Because it arrives in real time, you can reach out while they're still on your site.

By default every visitor goes to one channel. Squid ID can also send different visitors to different channels or people based on your [ICPs](/finding-visitors/icp-filtering), so each team only sees the visitors relevant to them.

## If you're coming from RB2B

If you currently use RB2B, here's how the Slack integration compares:

<div className="compare">
  <table>
    <thead>
      <tr><th /><th>RB2B</th><th>Squid ID</th></tr>
    </thead>

    <tbody>
      <tr><td>Destinations</td><td>One channel</td><td>Multiple channels</td></tr>
      <tr><td>Direct messages</td><td>Not available</td><td>Send to an individual teammate's DM</td></tr>
      <tr><td>Routing</td><td>All visitors to the one channel</td><td>Per-channel rules: all visitors, any ICP match, specific ICPs, or any high-intent page hit</td></tr>
      <tr><td>Multiple websites</td><td>Shared stream</td><td>Each channel fires only for its own website</td></tr>
      <tr><td>Failure handling</td><td>None</td><td>A broken channel is muted automatically without affecting the others</td></tr>
    </tbody>
  </table>
</div>

<p className="why"><strong>Why this matters.</strong> A single channel puts every visitor in one place, so your team sorts through them by hand. Routing by channel and direct message sends each visitor only to the people who need it, so a target account can go straight to the rep who owns it.</p>

## Before you start

<Info>You'll move faster if these are already in place.</Info>

* You're an **Owner** or **Admin** on the website. Viewers can see alerts but can't change routing.
* The [snippet is installed and verified](/getting-started/verify), so there are visitors to route.
* You can sign in to the Slack workspace you want alerts in.

<Info>You can connect Slack during initial setup too. On the last onboarding step, **"One last thing: get pinged on matches"**, pick **Slack**, sign in, and choose a channel or person, then **Finish**. Everything below also works later from **Settings → Integrations → Slack**.</Info>

## Connect your Slack workspace

<Steps>
  <Step title="Open the Slack connector">
    Go to **Settings → Integrations → Slack**.
  </Step>

  <Step title="Sign in with Slack">
    Click **Sign in with Slack**. A Slack window opens.
  </Step>

  <Step title="Approve the permissions">
    Squid ID uses them to post messages, list your channels, and send direct messages.
  </Step>

  <Step title="Confirm it's connected">
    The window closes and your workspace shows as **Connected**. This is a one-time step per workspace.
  </Step>
</Steps>

You can also paste an **Incoming Webhook URL** instead of using sign-in. A webhook supports a single channel and does not support the channel picker or direct messages.

## Create a channel route

A route is one destination plus a rule for what's sent there. You can add as many as you need.

<Steps>
  <Step title="Add a channel">
    On the Slack page, click **Add channel**.
  </Step>

  <Step title="Name it">
    Enter a name, for example `Sales · Enterprise`.
  </Step>

  <Step title="Pick the destination">
    Choose a public channel, private channel, or a teammate's direct message. Squid ID lists them from your connected workspace.
  </Step>

  <Step title="Choose what fires it">
    All visitors, any [ICP](/finding-visitors/icp-filtering) match, specific ICPs, or any [high-intent page](/finding-visitors/pages) hit (a visit to a page you flagged as high intent, like pricing or a demo).
  </Step>

  <Step title="Save">
    The route is active immediately.
  </Step>
</Steps>

## Common routing setups

Routes can be combined to send different visitors to different places. Some examples:

* **By deal size:** Enterprise-ICP matches to a senior rep's direct message, all other visitors to `#sales`.
* **By owner or territory:** one route per rep, each filtered to the [ICP](/finding-visitors/icp-filtering) for their accounts.
* **Executive alerts:** a route to a founder's direct message, filtered to a target-accounts ICP.
* **Buying signals:** an "Any high-intent page hit" route to `#hot-leads`, so anyone who views pricing or requests a demo pings the team, whether or not they match an ICP. The alert names the exact page they viewed.
* **Catch-all:** one "All visitors" route to a shared channel alongside your filtered routes.
* **Per website:** each route only fires for the website it belongs to.

Routes can be added, edited, or removed at any time.

## Unlock Squid ID+ from the alert

When a visitor matches and [Squid ID+](/add-ons/squid-id-plus) data is available but the website is set to reveal per record, the Slack alert shows which premium fields are on file (mobile, personal email, address) with the values hidden, alongside an **Unlock · \$0.25** button.

Click it and Squid ID charges \$0.25, reveals the record, and updates the same Slack message in place with the unlocked fields. No need to open the dashboard. The charge is drawn from your prepaid balance, and the price matches a per-record reveal in the app, so unlocking from Slack never costs more than unlocking from the profile.

<Info>The in-message button works on channels connected with **Sign in with Slack**. On webhook-only channels, the alert links to the profile in the dashboard, where you reveal it instead.</Info>

If the website is on [Automatic](/add-ons/squid-id-plus#turning-on-automatic), there's nothing to unlock: qualifying matches arrive already revealed, and the premium fields are in the alert from the start.

## Send a test

Next to any route, click **Test**. Squid ID sends a sample alert through the same path a real visitor uses, so you can confirm the channel is reachable.

## If a channel stops working

If a webhook breaks or a channel is deleted, Squid ID mutes that route after several failed sends (for ten minutes) so it doesn't block other routes or repeatedly retry Slack. The muted route shows a warning with the last error, and resumes automatically once the destination is fixed.