n-Help Scout's Slack App Tells Your Team a Ticket Happened. It Can't Do Anything About It.
Help Scout's native Slack integration posts a message to a channel whenever a conversation is created, assigned, replied to, or closed, with routing rules so different inboxes or event types land in different channels. It's a genuinely useful notification layer. What it isn't is a way to act on a ticket from inside Slack, that direction doesn't exist in the native app.
How the native integration works
Setup lives in Help Scout's app directory. Connect your Slack workspace, then build routing rules: which inbox, which event (created, assigned, updated, replied to, deleted, rated), and which Slack channel it should land in. Multiple rules can point at the same channel, so you can combine signals without cluttering every channel with every event.
It needs a plan with API access. The integration runs on Help Scout's API under the hood, so it's only available on plans that include API access, not every tier.
It @mentions the right person. When a conversation is assigned, the integration can tag the assigned teammate directly in the Slack message, with a link straight back to the conversation.
Where it stops being an integration and starts being a notification
Every version of this native connection runs one direction: Help Scout pushes a message into Slack. There's no built-in way to reply to a customer, resolve a conversation, reassign it, or add a tag from inside Slack itself. Someone still has to click the link and open Help Scout to do anything about what the message says.
It's also contained to Slack. The event that fired the notification doesn't go anywhere else, so if a tagged conversation should also kick off something in your order system or your on-call tool, that's a second integration entirely, one the native app was never built to handle.
What we've built on top of Help Scout and Slack
A support team running Help Scout and Slack together had the native integration posting every new conversation into a shared channel, which worked fine for visibility and did nothing else. Urgent tickets, the ones tagged 'escalation,' sat in the same channel as everything else, waiting for whoever happened to be scrolling past at the right moment. The team wanted an escalation tagged in Help Scout to actually page someone, not just get noticed eventually.
We built on top of the same webhook Help Scout already fires when a tag changes, routing escalation-tagged conversations into the team's on-call tool directly, with the assigned engineer paged within a minute instead of whenever someone next checked Slack. The Slack message still posts for visibility; it's just no longer the only thing that happens.
Posting every Help Scout event into Slack and stopping there?
Tell us which ones actually need more than a notification, an escalation, a refund tag, a status that should trigger something downstream. We can build past the point where the native integration leaves off. Slack's just one piece; we connect whatever's actually running your support operation to whatever needs to react to it.
Let's talk