Help Scout + Slack
Connect Help Scout and Slack to Keep Your Support Team in the Loop
Route customer conversations, escalations, and ticket activity from Help Scout into Slack automatically. No tab-switching required.
Why integrate Help Scout and Slack?
Help Scout is where your support team works, but Slack is where decisions get made, fires get fought, and teams stay aligned. When these two tools don't talk to each other, urgent customer issues go unnoticed, SLA breaches sneak up on you, and escalations stall because the right people find out too late. Connecting Help Scout and Slack with tray.ai closes that gap by routing the right conversation signals to the right channels and people in real time.
Automate & integrate Help Scout & Slack
Use case
Real-Time New Conversation Alerts in Slack
Whenever a new conversation is created in Help Scout, tray.ai can instantly post a structured message to a designated Slack channel — including the customer name, subject line, mailbox, and a direct link to the thread. No inbound request goes unnoticed, even during peak volume. Support leads can monitor incoming load without opening Help Scout.
Use case
Escalation Notifications for High-Priority Conversations
When a Help Scout conversation is tagged as urgent, assigned a specific label, or manually escalated, tray.ai can trigger an alert to a dedicated escalations channel and optionally @mention the assigned agent or on-call manager. No more relying on email notifications or manual hand-offs during critical moments. Teams can acknowledge and act on escalations within seconds.
Use case
SLA Breach Warnings Sent to Slack
tray.ai can monitor Help Scout conversations for approaching or breached SLA thresholds and fire proactive warning messages into Slack before the breach happens. Alerts include conversation details, time remaining, and a quick-action link back to Help Scout. Agents and managers get enough runway to respond before a commitment is missed.
Use case
Customer Satisfaction (CSAT) Score Alerts
After a Help Scout conversation is rated by a customer, tray.ai can post the CSAT result and customer comment into a Slack channel. Teams can celebrate wins, catch service failures quickly, and follow up with unhappy customers fast. Negative ratings can be routed to a dedicated review channel or directly to the agent who handled the conversation.
Use case
New Conversation Assignment Notifications for Agents
When a Help Scout conversation is assigned or reassigned to a specific agent, tray.ai sends that agent a direct Slack message with conversation context and a deep link to the thread. Agents don't need to constantly refresh their Help Scout queue, and nothing falls through the cracks during handoffs. It's especially useful for teams operating across shifts or time zones.
Use case
Daily Support Summary Digest Posted to Slack
tray.ai can pull Help Scout metrics each day — conversation volume, average first response time, open tickets, CSAT scores — and post a formatted summary to a Slack channel every morning or at shift start. The whole team gets a shared picture of support health without any manual reporting. Leaders can spot trends early and adjust staffing or priorities before things pile up.
Use case
Cross-Team Notifications for VIP or Enterprise Customer Conversations
When a conversation from a VIP, enterprise, or at-risk customer lands in Help Scout, tray.ai can route an alert to account management or sales channels alongside the support queue. Customer-facing teams stay informed on sensitive accounts without needing Help Scout access. Account managers can add context, flag renewal risk, or jump in to help — all from Slack.
Get started with Help Scout & Slack integration today
Help Scout & Slack Challenges
What challenges are there when working with Help Scout & Slack and how will using Tray.ai help?
Challenge
Mapping Help Scout Agents to Slack Users Reliably
Help Scout identifies agents by email address, while Slack uses unique user IDs. Without a reliable mapping layer, accurate @mentions and direct messages break down when routing conversation assignments or escalations through Slack.
How Tray.ai Can Help:
tray.ai's data mapping and lookup tools let you build a translation layer between Help Scout agent emails and Slack user IDs — either through a static lookup table or a dynamic Slack users.lookupByEmail API call — so every notification lands with the right @mention automatically.
Challenge
Avoiding Noisy, Low-Signal Slack Notifications
Sending every Help Scout event to Slack without filtering creates notification fatigue fast. Agents start ignoring the channel and miss the alerts that actually matter. Getting the signal-to-noise ratio right across different mailboxes, tags, and conversation types is harder than it looks.
How Tray.ai Can Help:
tray.ai's conditional logic and branching let you apply granular filters — by mailbox, tag, conversation status, customer tier, or any custom field — so only the events that genuinely need attention surface in Slack, keeping your channels focused and useful.
Challenge
Handling Help Scout Webhook Reliability and Retries
Help Scout webhooks can occasionally fail to fire or deliver events out of order during platform incidents or network issues. Without a retry mechanism, critical notifications like escalations or VIP alerts can be silently dropped.
How Tray.ai Can Help:
tray.ai has built-in error handling, retry logic, and workflow monitoring so failed webhook deliveries are caught and retried automatically. You can also set up alert notifications within tray.ai if a workflow fails, so your integration holds up when things go wrong.
Challenge
Keeping Slack Messages Formatted and Readable at Scale
Raw Help Scout webhook payloads are nested JSON. Passed directly to Slack, they produce unreadable walls of text. Crafting well-structured Slack Block Kit messages with the right fields, truncation, and links requires thoughtful data transformation — and that work needs to stay current as Help Scout's payload structure changes.
How Tray.ai Can Help:
tray.ai's data transformation tools let you parse, reshape, and format Help Scout payloads into clean Slack Block Kit messages with rich formatting, buttons, and contextual fields. When payloads change, updating the transformation is a simple workflow edit rather than a code deployment.
Challenge
Supporting Multiple Mailboxes with Different Routing Rules
Most support teams run multiple Help Scout mailboxes — separate inboxes for billing, technical support, and onboarding, for example — each needing to route notifications to different Slack channels with different urgency levels and formatting. Building and maintaining that per-mailbox routing logic by hand is fragile and eats up time.
How Tray.ai Can Help:
tray.ai's workflow branching and configurable routing logic make it straightforward to build a single integration that inspects the mailbox ID on each Help Scout event and routes the notification to the correct Slack channel with the right message format and urgency level — all maintained from one centralized workflow.
Start using our pre-built Help Scout & Slack templates today
Start from scratch or use one of our pre-built Help Scout & Slack templates to quickly solve your most common use cases.
Help Scout & Slack Templates
Find pre-built Help Scout & Slack solutions for common use cases
Template
Post New Help Scout Conversations to a Slack Channel
Automatically posts a formatted Slack message to a specified channel whenever a new conversation is created in Help Scout, including customer name, subject, mailbox source, and a direct link.
Steps:
- Trigger: New conversation created in Help Scout via webhook or polling
- Transform: Extract customer name, subject, mailbox, and conversation URL from the payload
- Action: Post formatted message to designated Slack channel using Slack's chat.postMessage
Connectors Used: Help Scout, Slack
Template
Send Slack Alert When a Help Scout Conversation Is Tagged as Urgent
Watches for Help Scout conversations that receive a specific urgency tag or label and immediately fires an alert to a dedicated Slack escalations channel, @mentioning the assigned agent.
Steps:
- Trigger: Help Scout conversation updated with a target tag (e.g., 'urgent', 'escalate')
- Filter: Confirm the tag matches escalation criteria before proceeding
- Action: Post alert to Slack escalations channel with @mention of the assigned agent
Connectors Used: Help Scout, Slack
Template
Notify Agent in Slack When Assigned a Help Scout Conversation
Sends a direct Slack message to the relevant agent whenever a Help Scout conversation is assigned or reassigned to them, including conversation subject, customer name, and a deep link.
Steps:
- Trigger: Help Scout conversation assigned or reassigned event fires
- Lookup: Map the Help Scout agent email to their Slack user ID
- Action: Send a direct Slack message to the agent with full conversation context and link
Connectors Used: Help Scout, Slack
Template
Post CSAT Ratings from Help Scout to a Slack Feedback Channel
Every time a customer submits a CSAT rating in Help Scout, this template posts the score, customer comment, and conversation link to a Slack feedback channel, with negative scores routed to a separate review channel.
Steps:
- Trigger: Help Scout customer satisfaction rating submitted
- Branch: Route positive ratings to the team kudos channel and negative ratings to the review channel
- Action: Post formatted CSAT card with score, comment, agent name, and conversation link
Connectors Used: Help Scout, Slack
Template
Daily Help Scout Performance Digest to Slack
Runs on a schedule to pull Help Scout metrics — open conversations, average response time, conversations closed, and CSAT — and posts a clean summary card to a Slack channel.
Steps:
- Trigger: Scheduled run (e.g., daily at 9am in team's timezone)
- Action: Query Help Scout Reports API for previous day's conversation and CSAT metrics
- Action: Format and post a structured summary block to the designated Slack channel
Connectors Used: Help Scout, Slack
Template
Alert Slack When a Help Scout Conversation Has Been Waiting Too Long
Periodically scans Help Scout for open conversations that haven't received a reply within a defined time threshold and posts a Slack alert to the support channel so agents can prioritize them immediately.
Steps:
- Trigger: Scheduled interval (e.g., every 30 minutes during business hours)
- Action: Query Help Scout for open conversations where last customer reply is older than the SLA threshold
- Action: Post a Slack message listing at-risk conversations with customer names and links
Connectors Used: Help Scout, Slack