The HubSpot Conversations Inbox
Where messages land before they become tickets, and the part of Service Hub people configure last and regret first.
What it is
A shared inbox that collects connected channels: team email addresses, live chat, forms and social, in one place with assignment and internal comments.
Conversations can become tickets, and on the help desk workspace they largely are tickets. The distinction matters because a conversation without a ticket has no pipeline, no status and no reporting.
Setting it up so nothing gets lost
Where duplicates creep in
Two specific patterns, both structural.
A customer starts a chat, does not get resolved, and emails. If those arrive on the same contact you get two conversations on one record. If they used a different email, you get two contacts and two records that never meet.
And a reply to a closed conversation frequently opens a new one, which is the same trap every helpdesk has and which people expect a CRM-native product to solve. It does not.
Frequently asked questions
What is the difference between the conversations inbox and the help desk?+
The inbox collects messages. The help desk workspace adds ticket pipelines, statuses and reporting on top.
Should every conversation become a ticket?+
If you want it reported on, yes. Conversations without tickets are invisible to your metrics.
Two conversations, one request
Chat then email is one problem arriving twice. Ticket Merger is coming to HubSpot, and works on Zendesk and Freshdesk today.
Start free trial14-day free trial. No credit card required.