Reply to HubSpot conversations from Slack
BackReply is a HubSpot + Slack integration with a real reply path: conversations from your Inbox or Help Desk become Slack threads, your team answers in the thread, and the reply reaches the customer through HubSpot—email threads included. HubSpot stays your system of record.
Reply to email threads from Slack
Most HubSpot-to-Slack setups stop at notifications, and email is where they stop hardest: seeing the thread in Slack is easy, answering it from Slack isn't. BackReply makes the Slack reply a real customer-facing email.
Email threads included
Reply from Slack and the customer receives an email in their existing thread—subject carried, CC'd parties kept.
A customer reply, not an internal note
Your message reaches the customer on the original channel, attributed to the right agent—not filed as a comment nobody sees.
Collaboration without extra seats
Loop in engineering, product, or founders without provisioning everyone in HubSpot.
One loop, no inbox switching
The Slack thread is where the work happens; HubSpot keeps the record.
- Customer writes in viachat, email, or Messenger
- The HubSpot conversation appears asa Slack thread
- Teammate repliesin the thread
- BackReply syncs it tothe HubSpot conversation
- Customer receives it ontheir original channel
Replies flow in both directions across chat, email, and Messenger, and every thread links back to the conversation in HubSpot. See how replying from Slack works.
How it connects to HubSpot
Secure OAuth connection
Connect your portal with least-privilege OAuth scopes. No passwords stored, easy to revoke from HubSpot at any time.
Conversation sync loop
HubSpot → Slack → HubSpot. Replies flow seamlessly in both directions across chat, email, and Messenger.
Admin-managed routing rules
Control which inboxes and channels route to which Slack channels with flexible rules.
Works on Inbox and Help Desk
Both HubSpot inbox types are detected automatically at connect time. No configuration to choose between them.
The Slack installation guide covers the Slack side of setup.
Six ways to route a HubSpot conversation
Rules are evaluated top to bottom, and the first match wins.
| Condition | Example |
|---|---|
| Assignee | Route Dana's conversations to #dana |
| Team | Route the Sales team to #sales-support |
| Inbox | Route the Support inbox to #support |
| Channel | Route email threads to #email-queue |
| Status | Route only open conversations |
| Actor type | Route Breeze AI handoffs to #ai-escalations |
Route on AI vs. human
Actor type tells you whether a message came from a person or from Breeze AI—so you can send AI-to-human handoffs straight to the channel that handles them.
What stays in HubSpot
Conversation history stays canonical
HubSpot remains the single source of truth for all customer interactions.
Assignments synced in real time
All actions taken in Slack—assign, close, add notes—are reflected in HubSpot instantly.
Links back to source for audits
Every Slack thread includes a direct link to the HubSpot conversation, in the right regional portal.
How this differs from HubSpot's own Slack integration
HubSpot's built-in integration is useful—it just has a different scope. Here's the honest picture, per HubSpot's documentation as of August 2026.
HubSpot's built-in Slack integration
- Conversations inbox: reply from Slack threads on live chat, Facebook Messenger, and WhatsApp—but not on the team email channel.
- Help Desk: ticket notifications and property updates from Slack, but Slack thread replies sync as internal comments—they don't go to the customer.
BackReply
- Customer-facing replies from Slack on both the Conversations inbox and Help Desk, detected automatically.
- Email threads included: your Slack reply becomes a real email in the customer's existing thread.
- Plus routing rules, ownership controls, and reply permissions built for teams working out of Slack.
If notifications and internal comments cover your workflow, the built-in integration may be all you need. BackReply is for teams that want to actually answer customers from Slack.
HubSpot + Slack questions, answered
Can I reply to HubSpot conversations from Slack?
Yes—that's what BackReply does. Conversations from your HubSpot Inbox or Help Desk are posted as Slack threads; reply inside the thread and your message is delivered to the customer through the HubSpot conversation, on the channel they wrote in from.
Do Slack replies reach the customer, or are they internal comments?
They reach the customer. A BackReply reply is a customer-facing message in the HubSpot conversation—on email threads it arrives as a real email in the customer's existing thread. Internal notes are separate and explicit: use the Add Note action when you want something only your team can see.
Does this work with Help Desk, or just the Conversations Inbox?
Both. BackReply detects which inbox type you're using when you connect, and the reply experience is identical on either.
Who does the customer see as the sender?
The teammate who replied, as long as their Slack account is mapped to a HubSpot seat. Mapping happens automatically when emails match, and you can adjust it by hand. Unmapped teammates still get their reply delivered under a fallback agent, with their real name disclosed in the message.
Can we route on conversation tags?
HubSpot conversations don't carry tags, so there's nothing to route on. You get six other conditions instead—assignee, team, inbox, channel, status, and actor type—including two that Intercom has no equivalent for.
Do you support non-US portals?
Yes. EU, APAC, and North American portals are all supported, and links back to HubSpot resolve to your portal's own region.
Can we connect HubSpot and Intercom at the same time?
Yes. Each workspace keeps its own provider, settings, and behavior—there's no bleed between them.
Using Intercom instead? BackReply works with Intercom too.