The HubSpot shared inbox, named the conversations inbox inside the product, is one of the few pieces of serious shared inbox tooling that can be switched on without a paid plan. That is the reason it gets shortlisted, and it is also the reason the evaluation often stops too early. What the inbox does on day one and what it requires by month three are two different lists, and most of the second list is about seats, tiers, and a change to how tickets work that affects newer accounts only.
None of this is hidden. It is spread across several documentation pages and a pricing page, and the parts that matter most are the ones that read as footnotes.
What the inbox is
Every HubSpot account gets one conversations inbox created automatically, and the documentation lists the inbox under all products and plans, so basic functionality is not gated behind a tier. It is where a team views, manages and replies to incoming customer messages.
Channels are what feed it. The documented channel types are a team email channel, a chat channel, a Facebook Messenger channel and a form channel. Connecting a team email address is the usual first step, and until that happens HubSpot provides a stand in: a fallback email, described in the documentation as an email that HubSpot provisions so that certain tools, such as ticket automation, can be used before a team email address is connected.
The fallback email is worth a moment of thought rather than being clicked past. It exists so the account is never in a state where nothing can receive, and because it is provisioned by HubSpot rather than by the organisation, it is an address on a domain the organisation does not control. That is fine as scaffolding during setup. It becomes a problem if it reaches customers, because replies then arrive at an address that has no relationship to the brand and cannot be moved elsewhere later. Connecting the real team address early, and checking what the from address looks like on an outgoing reply, avoids the version of this that is discovered by a customer.
Creating more than one inbox is where the first tier boundary sits. The documentation states that a Professional or Enterprise subscription is required to create multiple conversations inboxes. For a single support address that is irrelevant. For an organisation that wants support, recruitment and billing kept apart, it is the whole decision, because separating them is not a matter of folders or views. It is a matter of plan.
The ticket change that catches newer accounts
This is the single most important thing to establish before reading any tutorial about the HubSpot shared inbox, because it determines whether the tutorial applies at all.
HubSpot's documentation states that all accounts created after April 1st, 2024 cannot create tickets from channels connected to the inbox, and directs those accounts to manage tickets in help desk instead. Help desk is a separate workspace, introduced later, aimed at the same job.
The consequence for evaluation is practical. Guides, comparison articles and community answers written before that date describe a workflow where a message arriving in the conversations inbox becomes a ticket with a pipeline stage, an owner and SLA reporting. An account created in, say, 2025 or 2026 does not behave that way. The inbox still receives and still lets people reply, but the ticket layer that made it a tracking system for newer accounts lives in help desk.
So the first question in any HubSpot shared inbox evaluation is when the account was created. If the answer is after 1 April 2024, then anything depending on tickets needs to be evaluated against help desk and its own tier and seat requirements, not against the free conversations inbox. Skipping that step is how a pilot reaches the end of a month before somebody notices that the thing being piloted was not the thing being described.
Seats decide who can be assigned work
HubSpot prices by seat, and the seat type is not only a billing detail. It governs behaviour.
The documentation is specific: an assigned Sales or Service Seat is required to automatically route incoming emails to specific users, and incoming conversations can only be automatically assigned to users with assigned Sales or Service seats. Users without such a seat are not locked out of the inbox. They can still respond to unassigned conversations if they have inbox access.
Read that pair of statements together and the operating model becomes clear. Free or core users can help. They cannot be the person the system holds responsible for an item. For a team of three where one person owns the queue and two chip in, that works. For a rota where whoever is on duty owns what arrives, it does not, because ownership is exactly the thing that needs to be assignable, and assignment is the thing that requires a paid seat per person.
This is the point where cost stops scaling with volume and starts scaling with headcount. A queue of 40 messages and a queue of 4,000 cost the same. Three people who can be assigned work and eight people who can be assigned work do not.
What it costs, as listed
Prices below are taken from HubSpot's Service Hub pricing page as of September 2026, in US dollars, and HubSpot lists them as starting prices.
| Plan | Listed price | Notes |
|---|---|---|
| Free | $0 | Listed as free for up to 2 users, no credit card required |
| Starter | From $7 per seat per month on annual commitment, $20 per seat per month monthly | Includes 500 HubSpot Credits |
| Professional | From $90 per seat per month on annual commitment, $100 monthly | Includes 3,000 credits, plus a required one time Professional onboarding fee of $1,500 |
| Enterprise | From $150 per seat per month | Includes 5,000 credits, plus a required one time Enterprise onboarding fee of $3,500 |
Three details in that table do more work than the headline numbers.
The gap between annual and monthly pricing is large in proportional terms at the Starter tier, which means the cheap entry price assumes a year of commitment. The onboarding fees at Professional and Enterprise are one time and required, and $1,500 lands before the first monthly invoice, which changes the shape of a first year budget considerably. And the free plan being listed as free for up to 2 users sets the boundary of the free tier in headcount, not features, which is consistent with how the rest of the pricing works.
The multiple inbox requirement sits at Professional. So does much of the automation that makes a busy queue manageable. A team that starts free, grows to five people and wants two separate inboxes is not making an incremental purchase. It is arriving at the Professional tier with five seats and an onboarding fee.
What the inbox is genuinely good at
The reason to choose it is not the inbox. It is what the inbox is attached to.
Every conversation sits next to a CRM record. The person emailing has a contact record with their history, the deals they are attached to, the marketing emails they have received and the pages they have visited. For a team whose work is commercial conversation, that context is the product, and no standalone inbox reproduces it.
That makes the decision much easier than a feature comparison suggests. An organisation already running marketing and sales in HubSpot's ecosystem, with contact records as the system of record, gains real value from having replies happen inside it. An organisation that would be adopting a CRM solely to get a shared inbox is buying a large structure for a small need, and paying per seat for people whose only requirement is to answer messages.
The second thing it does well is conversation. Threads, assignment, availability status, internal comments before a reply goes out. The unit of work is a back and forth exchange with a person, which is what a shared inbox is built around.
Where intake sits awkwardly in a shared inbox
The form channel means form submissions can arrive as conversations, and for an enquiry form that is exactly right. An enquiry is the opening line of a conversation.
Intake is a different shape. An application, a registration, a grant submission, a facility booking, a warranty claim: these arrive as a complete set of structured answers, and what happens next is not a reply so much as a decision. The questions asked of that queue are how many are unreviewed, who is reviewing each one, which ones are waiting on a document, and how many were accepted. A thread based inbox answers those questions with read and unread, assigned and unassigned, open and closed.
Teams bridge the gap in familiar ways. A spreadsheet next to the inbox holding the fields the inbox does not, labels standing in for stages, or a naming convention in the subject line. Each works, and each has the same weakness: the record of where something stands is maintained by somebody remembering to maintain it, separately from doing the work.
A form tool with response management takes the other route. The structured answers stay attached to the response, the owner and the status are properties of the response rather than of a thread, and the reply is sent from the same screen as the review. For teams whose queue is applications rather than conversations, that is the difference worth measuring, and the use cases pages set out what each kind of intake needs.
Before pointing your address at it
Five questions, answerable in an afternoon, that decide most of this.
When was the account created. After 1 April 2024 means tickets come from help desk, not from inbox channels.
How many people need to be assignable, not merely able to reply. Each of those needs a Sales or Service seat.
How many separate inboxes are needed. More than one requires Professional or Enterprise.
Is the queue conversations or structured intake. Threads suit the first. Fields, states and owners suit the second.
Is HubSpot already the system of record for contacts. If yes, the CRM context justifies a lot. If no, the seat based pricing is being paid for a shared inbox alone, and pricing that counts only the people who need access is worth putting side by side with it, which is what the pricing page is for.
What to change first
Check the account creation date before anything else, because it determines whether tickets are available from inbox channels or only through help desk, and every other comparison depends on that answer. Then count the people who must be assignable rather than merely present, since that number, not the message volume, is what the bill follows. If the queue turns out to be structured submissions rather than conversations, the shape to compare against is a queue with an owner and a status per response, which takes a couple of minutes to see in the Halict demo.
Q1. Is the HubSpot shared inbox free?
The conversations inbox is listed under all products and plans, and every account gets one inbox created automatically, so a single shared inbox can be run without a paid plan. HubSpot's pricing page lists the free Service Hub plan as free for up to 2 users, and creating multiple inboxes requires a Professional or Enterprise subscription.
Q2. Why can I not create a ticket from the conversations inbox?
HubSpot's documentation states that accounts created after April 1st, 2024 cannot create tickets from channels connected to the inbox, and directs those accounts to manage tickets in help desk instead. Guides written before that date describe the older behaviour, which is why they no longer match newer accounts.
Q3. Do all users need a paid seat to use the shared inbox?
No, but assignment depends on it. An assigned Sales or Service Seat is required for incoming conversations to be automatically routed to a specific user, while users without one can still respond to unassigned conversations if they have inbox access. Ownership is the part that requires a paid seat.
Q4. What does HubSpot Service Hub cost per seat?
As listed in September 2026, Starter starts at $7 per seat per month on an annual commitment or $20 monthly, Professional at $90 per seat per month annually or $100 monthly, and Enterprise at $150 per seat per month. Professional and Enterprise also carry required one time onboarding fees of $1,500 and $3,500.
Q5. Which channels can be connected to the HubSpot inbox?
The documented channel types are a team email channel, a chat channel, a Facebook Messenger channel and a form channel. Until a team email address is connected, HubSpot provisions a fallback email so that tools such as ticket automation can still be used.
Q6. Is a shared inbox the right place for application or registration forms?
It works, and the fit depends on what follows the submission. A shared inbox is built around threads that are open or closed and assigned or unassigned, so structured intake that needs stages, per response fields and a record of decisions usually ends up with a spreadsheet maintained alongside the inbox.