Help Scout and Slack: Deliberately Simple, and Better For It
Notifications from a mailbox into a channel. No agent surface, no reply path, no configuration maze — which fits a product built on the idea that support tooling should stay out of the way.
- Connector
- Native — Help Scout's Slack app, configured per mailbox
- Sync direction
- Almost entirely Help Scout → Slack
- Setup time
- 10 minutes
- Availability
- Available across Help Scout plans
| What | Direction | Detail |
|---|---|---|
| New conversations | Help Scout → Slack | Posted per mailbox, so a support mailbox and a sales mailbox can route to different channels. |
| Customer replies | Help Scout → Slack | Often more useful than new-conversation alerts, because a reply means someone is waiting on a thread already in progress. |
| Assignments | Help Scout → Slack | Best as a direct message to the assignee rather than a channel post — it is personal accountability, not team news. |
| Internal notes | Help Scout → Slack | Notes and mentions reach colleagues who are not in the Help Scout inbox all day. |
| Status changes | Help Scout → Slack | Conversation closed or reopened, useful mainly for monitoring a specific high-priority mailbox. |
| Per-mailbox routing | Configuration | Each mailbox maps to its own channel, which is the mechanism that keeps volume sane as you add mailboxes. |
Setting it up
- Connect the Slack app from Help Scout's app settings and authorise the workspace your team uses.
- Configure notifications per mailbox rather than globally. A single channel receiving every mailbox is the fastest route to a mute.
- Start with customer replies rather than new conversations. Replies indicate someone is waiting on an existing thread, which is the more actionable signal.
- Send assignment notifications as direct messages to the assignee, keeping channels for things the team collectively needs to see.
- Enable mention notifications so colleagues outside the support team can be pulled into a conversation without needing to watch the inbox.
- Reassess after a fortnight. If the channel is muted, reduce what you send rather than accepting that it is background noise.
Where the integration stops
- No replying from Slack. Every notification is a link back to Help Scout. This is a deliberate scope decision rather than a missing feature.
- Slack conversations do not attach to Help Scout conversations. Discussion in a channel leaves no trace on the customer record.
- Filtering is coarse compared with trigger-based helpdesks. You choose events per mailbox, not conditions on those events.
- Volume management is by mailbox, not by rule. Busy mailboxes will produce busy channels, and the only lever is which mailbox goes where.
- One Slack workspace per Help Scout account.
The case for a small integration
Help Scout's design philosophy is that support tooling should be invisible to the customer and unobtrusive to the agent. The Slack app follows the same logic: it does one thing, it takes ten minutes, and there is almost nothing to get wrong.
That is genuinely valuable. A meaningful proportion of the configuration effort in richer integrations goes into undoing defaults and taming volume. Here there is very little to tame, because there is very little on offer.
The event to choose
Customer replies, not new conversations.
A new conversation is a queue item — it will be picked up in the normal flow of work and does not need announcing. A reply on an existing thread means a customer responded to something an agent said and is now waiting, which is both more urgent and less visible in a mailbox view.
Teams that switch from new-conversation alerts to reply alerts usually find the channel becomes both quieter and more useful in the same week.
Where the ceiling is
The moment you want conditional alerting — notify only for VIP customers, only outside business hours, only when a conversation has been unanswered for two hours — you have exceeded what this integration expresses.
Help Scout's workflows can act on those conditions internally, but the Slack notification layer is not condition-aware in the way a trigger-based helpdesk is. That is a real constraint for larger support operations and a non-issue for teams of five.
The genuinely useful edge case
Mentions. Pulling a developer or a founder into a customer conversation, and having that reach them in Slack rather than requiring them to open a support tool they do not use, is the part of this integration that gets used long after the channel alerts have been trimmed back.
It costs nothing to enable and it is the reason to install the app even if you turn every other notification off.