HubSpot Chat in Slack for Support Teams

Slack is where your team already is. Getting HubSpot chat into Slack is easy. Doing it well, so nobody mutes the channel by Thursday, is the actual job.

What HubSpot chat in Slack actually does

HubSpot has an official Slack app, installed from the HubSpot app marketplace or the Slack directory, connected with an admin account on both sides.

Broadly it gives support teams three things.

Notifications in Slack. New conversations, assignments, mentions and ticket activity pushed into a channel or a direct message.
Replying from Slack. Respond to a HubSpot conversation without opening HubSpot, with the reply logged back against the record.
Creating and looking up records through slash commands, so somebody in a general channel can open a ticket without switching tools.

Exact capabilities shift as the app is updated, and some depend on your subscription tier. Check the current listing rather than trusting a feature list you read somewhere, this page included.

Notifications people will actually read

Here is the failure mode, and it happens within a fortnight in almost every rollout.

Somebody switches on notifications for everything. The channel fills with every new conversation, every assignment, every reply, every stage change. By Thursday, three people have muted it. By the following month, the escalation everybody needed to see scrolls past unread, and Slack is now a place where support alerts go to be ignored.

The fix is to be aggressively selective from day one.

Notify on exceptions, not on volume. A breach, a VIP account, a reopen, an ageing ticket. Not every arrival.
One channel, one purpose. An escalation channel that fires four times a week gets read. A firehose does not.
Direct messages for personal assignment, channels for team-level events. Mixing them guarantees both get muted.
If a notification never leads to action, delete it. Ask that question monthly.
The value of a Slack alert is inversely proportional to how many of them there are. A channel with six messages a day is a tool. A channel with two hundred is wallpaper.

Replying from Slack, and when not to

Replying without leaving Slack is genuinely useful for a specific case: a short answer, from somebody who isn't a full-time agent, to a question that arrived while they were mid-conversation about something else.

It is not a substitute for the help desk workspace. Slack shows you a message. It does not show you the customer's previous tickets, their company, their account tier, or the four other open conversations from the same person. An agent working entirely from Slack is an agent working without context, and it shows in the replies.

The sensible split: Slack for quick answers and internal coordination, HubSpot for anything requiring history or judgement. Say that out loud to the team, because otherwise people gradually drift into Slack-only working and nobody notices until the reporting looks wrong.

Escalation channels that work

The best use of Slack in support isn't customer replies at all. It's the internal handover.

A dedicated escalation channel, fed by a workflow rather than by a human remembering, is worth more than every other part of this integration combined. Something breaches, a VIP account raises a ticket, a ticket reopens for the third time, and it appears where the people who can act on it already are.

Three things to get right:

Include the link back to the record. An alert without a click-through is a rumour.
Include enough context to triage without opening it. Customer, topic, age, why it fired.
Give the channel an owner. A channel everybody watches is a channel nobody watches.

For engineering escalation specifically, a channel plus a linked issue in your tracker beats forwarding emails. The important part is the return path: when the fix ships, somebody has to tell the customer, and that step is the one teams forget to design.

The traps

Four, in rough order of how often they bite.

Threads that fork. A conversation starts in the Slack thread, continues in HubSpot, and the two halves never meet. Decide where the record of truth lives and be boring about it.
Slash-command tickets with no context. Someone creates a ticket from Slack with a one line description and no contact association. It becomes an orphan record that never appears in the customer history.
Duplicates from two directions. A customer emails support and pings your shared Slack Connect channel about the same problem. Two records, both real, nothing linking them. Inbox automation will not catch this, because rules only ever see one conversation at a time.
Permissions drift. The integration inherits what the connecting account can see. Review it when people change roles, and again when somebody leaves.
FAQ

Frequently asked questions

Does HubSpot have an official Slack integration?

Yes. There is a HubSpot app for Slack, installed from either marketplace and connected by an admin on both sides. Capabilities change as it is updated, so check the current listing.

Can I reply to HubSpot chats from Slack?

Replying to conversations from Slack is supported, with the reply logged against the record. It works best for short answers, since Slack doesn't show you the customer history that a full agent view does.

Should support tickets be created from Slack?

Sparingly, and only when the person creating it includes enough detail and the right contact. A ticket created from a one line Slack command usually becomes an orphan record nobody can act on.

What should the Slack integration notify us about?

Exceptions only. Breaches, VIP accounts, reopens and ageing tickets. Notify on every new conversation and the channel is muted within a fortnight, alerts included.

Two channels, one problem

When a customer messages you in Slack and emails support, you get two tickets for one issue. Ticket Merger merges those automatically on Zendesk and Freshdesk today, and HubSpot is on the roadmap.

Start free trial

14-day free trial. No credit card required.