Slack integration
Send 11x alerts to Slack. Get notified on replies, booked meetings, qualified leads, completed calls, and flagged conversations, routed to the right channel.
The Slack integration pushes 11x events into Slack in real time, so your team doesn't have to watch a dashboard. When a call completes, a lead replies, a meeting is booked, or a lead qualifies, Slack is notified immediately with enough detail to act without clicking through. Notifications route by event type, and the lead owner is tagged automatically.
Who this applies to: 11x workspace Admins connecting the workspace, and any rep who wants to receive alerts. Connecting Slack requires permission to install apps in your Slack workspace.
What Slack gets notified about
| Event | Notification goes to |
|---|---|
| Lead replies | The lead owner, plus your outbound channel |
| Meeting booked | The assigned rep, plus your pipeline channel |
| Lead qualified | The assigned rep and their manager |
| Call completed | Your inbound channel, with the outcome |
| Conversation flagged | Whoever owns escalations |
Which of these fire is configurable — you choose the event triggers rather than receiving all of them.
Key behaviours
Instant notifications
Real-time alerts, so nobody has to check a dashboard to find out a lead replied.
Routed to the right channels
Customizable by event type and by team, so your inbound channel isn't flooded with outbound noise.
Context without click-through
Enough detail lands in the message itself to decide what to do next.
Automatic rep tagging
The lead owner is tagged automatically, so alerts reach a person and not just a channel.
Threaded updates per account
Multiple touchpoints on the same prospect thread together, so the full history is in one place.
Configurable event triggers
Choose which events are worth interrupting someone for.
Setup
Connect your Slack workspace
In 11x, go to Settings → Integrations and select Slack. Authorize the app in your Slack workspace. You'll need permission to install Slack apps, or an admin to approve the request.
Choose which events notify
Start conservative. Booked meetings and escalations are almost always worth an alert; every completed call usually isn't, at volume.
Map events to channels
A common split: one channel for booked meetings and qualified leads, one for inbound call outcomes, one private channel for escalations and flagged conversations.
Enable rep tagging
So the assigned rep is notified directly rather than relying on someone reading the channel.
Test with a real event
Run a test lead through and confirm the notification arrives in the right channel with the right person tagged.
Notification fatigue is the main failure mode here. If a channel gets noisy enough that people mute it, the integration has stopped working even though it's technically fine. Turn events off aggressively.
Recommended channel setup
| Channel | Events | Who's in it |
|---|---|---|
#pipeline-wins | Meeting booked, lead qualified | Sales team and leadership |
#inbound-calls | Call completed, with outcome | Inbound team and RevOps |
#11x-escalations | Flagged conversations, replies needing a human | Campaign owner and managers |
#11x-alerts | Deliverability and connection warnings | RevOps and admins |