Skip to content

Slack · Team alerts

Slack integration for customer support

Your team already lives in Slack. Hushdesk posts the three moments that need a person now: a shopper starts a live chat, a ticket is urgent, or the AI hands a conversation over. Everything else stays in the inbox.

Example messages

What Hushdesk posts to your Slack channel

Three alerts, written to be read in a second. Each one links straight to the conversation.

What Hushdesk sends to Slack
{
  "text": ":speech_balloon: *New live chat* from Ana Reyes\n> Hi! Does the linen throw come in sage?\n<https://…/app/inbox?c=…|Open the chat>"
}

New live chat

When it is posted

A visitor starts a chat on your store or website. Every new chat is posted, so someone can jump in while the shopper is still on the page.

What is in it

  • The customer’s name, or their email when there is no name
  • The first message, up to 280 characters
  • A link that opens the chat in Hushdesk

Chats come from the widget on your store: see live chat.

What Hushdesk sends to Slack
{
  "text": ":rotating_light: *Urgent ticket* from Jun Park: Charged twice for order #1077\n<https://…/app/inbox?c=…|Open the ticket>"
}

Urgent ticket

When it is posted

A new email or form ticket arrives with Urgent priority. Your automation rules run first, so a rule that marks a ticket urgent is enough to send it to Slack.

What is in it

  • Who wrote in
  • The ticket subject
  • A link that opens the ticket
What Hushdesk sends to Slack
{
  "text": ":raising_hand: *The AI handed a ticket to the team*: Exchange for size M (Lily O’Donnell)\nWhy: The customer sounds upset: a person should answer\n<https://…/app/inbox?c=…|Open the ticket>"
}

AI hand-over

When it is posted

The AI agent, running on autopilot, decides not to send a reply itself. It tags the ticket for the team and says why, so a person picks it up fast.

What is in it

  • The ticket subject and who wrote in
  • Why the AI held back, in plain words
  • A link that opens the ticket

How the AI decides is explained on the AI agent page.

Deliberately not posted: ordinary emails, customer replies, agent replies and closed tickets. A channel that pings for everything gets muted, and then the urgent one is missed too.

Setup

How to connect Slack to Hushdesk

Slack calls this an incoming webhook: a private URL that posts into one channel. It takes about two minutes.

  1. 1

    In Slack, create an app for your workspace (api.slack.com/apps, Create New App, From scratch) or open one you already use for alerts.

  2. 2

    Open Incoming Webhooks, switch them on, and click Add New Webhook to Workspace.

  3. 3

    Pick the channel the alerts should go to, for example #support-alerts, and allow it.

  4. 4

    Copy the webhook URL. It starts with https://hooks.slack.com/services/.

  5. 5

    In Hushdesk, open Settings, Apps, Slack, paste the URL and click Connect.

  6. 6

    Hushdesk posts a test message to the channel before saving. When it appears, you are done.

Slack’s own guide: Sending messages using incoming webhooks.

Hushdesk · Settings · Apps · Slack

Incoming webhook URL

https://hooks.slack.com/services/…

Stored encrypted and never shown again.

# support-alerts

Hushdesk is connected. Urgent tickets, new chats and AI hand-overs will show up here.

The test message Hushdesk posts before it saves anything.

Recipe

Send urgent tickets to Slack with an automation rule

Slack hears about a new ticket after your rules have run. So the simplest way to decide what counts as urgent is a rule: words that mean money or reputation are at stake, a VIP tag, or a channel you always want eyes on.

Build it under Workflows in Hushdesk. Read more about automation rules.

WhenA ticket is created
IfThe message contains any of: chargeback, fraud, never arrived
ThenSet the priority to Urgent

Result: an “Urgent ticket” message in your channel.

Privacy

What leaves Hushdesk when Slack is connected

  • Only what the alert needs

    The customer’s name or email, the subject or the first 280 characters of a chat, and the AI’s reason for handing over.

  • Links, not data dumps

    Orders, addresses and full threads stay in Hushdesk. The link in each alert asks for a Hushdesk sign-in.

  • Post-only access

    An incoming webhook can post into one channel and nothing else: Hushdesk cannot read your Slack workspace.

Bring the urgent ones to where your team already is

Start free, connect Slack from Settings, Apps, and see the test message land.

FAQ

Slack integration: questions and answers

How do I connect Slack to Hushdesk?

Create an incoming webhook in Slack for the channel you want, copy its URL, then paste it in Hushdesk under Settings, Apps, Slack and click Connect. Hushdesk posts a test message to that channel before saving, so you know straight away that alerts will arrive.

What does Hushdesk post to Slack?

Hushdesk posts three kinds of message: a new live chat with its first line, a new ticket marked urgent, and a ticket the AI agent handed to your team with the reason. Each message links straight to the conversation in Hushdesk. Ordinary emails and replies are not posted, which keeps the channel quiet.

Can I choose which Slack channel gets Hushdesk alerts?

Yes. You pick the channel when you create the incoming webhook in Slack, and Hushdesk posts only to that channel. To move alerts to another channel, create a new webhook for it and connect Slack again in Settings, Apps with the new URL. Each workspace sends to one channel.

Does Hushdesk post every support email to Slack?

No. Emails are posted only when a new ticket arrives with Urgent priority, for example because a rule marked it urgent. New live chats and AI hand-overs are the other two alerts. Customer replies, agent replies and closed tickets are never posted, so Slack stays useful instead of noisy.

How do I send urgent tickets to Slack?

Create a rule in Hushdesk that runs when a ticket is created and sets the priority to Urgent when the message contains words like chargeback or fraud. Rules run before Slack is notified, so every ticket the rule marks urgent is posted to your channel with a link to open it.

Is the Hushdesk Slack integration secure?

Yes. The webhook URL is encrypted at rest and never shown again after you save it, and an incoming webhook can only post to its channel: it cannot read your Slack messages. Alerts carry the customer’s name or email, the subject or first 280 characters, and a link that needs a Hushdesk sign-in.

Can I reply to customers from Slack?

No. Slack messages from Hushdesk are alerts with a link, not a second inbox. Replies are written in Hushdesk, where the customer’s orders, your macros and the AI drafts are beside the conversation, and every reply is kept on the ticket. The link in each alert opens the right conversation in one click.

Why does Hushdesk say Slack did not accept the test message?

Hushdesk sends a test before saving, and Slack refused it. Check that the URL starts with https://hooks.slack.com/services/, that the webhook has not been removed from the Slack app, and that its channel still exists and is not archived. Create a new webhook if needed and connect again.

Who can connect Slack to Hushdesk?

Only workspace owners and admins can connect or disconnect Slack, or any other app. Agents and viewers see the alerts in Slack but cannot change where they go. Every connect and disconnect is written to the workspace audit log with who did it and when.