Slack
Send relevant support notifications to your team’s Slack workspace.
On this page
Overview
Slack integration posts operational notifications (new ticket, handoff, and similar events you enable) to an Incoming Webhook URL. Agents still reply in HelSup Inbox. Slack is not a customer channel and not a replacement for email or live chat.
When to use this
On-call teams already sit in Slack. A single webhook avoids polling Inbox on a phone without moving the conversation out of the helpdesk.
Where to find the controls
Settings → Integrations → Slack view. Logs on the integrations log list.
Who can make these changes
manage_integrations to set the URL. Recipients are Slack workspace members, not portal customers.
Before you begin
Create a Slack Incoming Webhook, paste the URL, choose events, send a test. Rotate the URL if it leaks. Export of settings excludes webhook secrets.
Follow these steps
- Create the Slack webhook.
- Paste it into HelSup.
- Enable the events you want.
- Create a test ticket or handoff.
- Confirm the Slack message.
- Open the ticket from the SPA, not by emailing Slack.
Settings reference
Webhook URL, enabled events, last delivery status, error text. No Slack Bot token family beyond what the pane documents.
Example workflow
Handoff at 02:00 posts “Visitor asked for a human — ticket #ES-184”. The on-call agent opens #/inbox Live Chat view.
Good practices
Use a dedicated #support-oncall channel. Disable noisy events (every public reply) if the channel floods.
Important considerations
A leaked webhook URL lets anyone post to that channel. This is not end-to-end customer chat. Do not paste ticket internals that violate privacy policy.
If something does not work
No Slack message: URL revoked, event disabled, queue backlog, or Slack 4xx. Contact support after the integration log shows the HTTP status.