What This Update Actually Is
HubSpot shipped Ticket Capacity Limits to Service Hub Professional on May 7, 2026. Before this, capacity-aware routing lived exclusively behind the Enterprise paywall. Now Pro teams can use it too.
Here's exactly what admins can configure:
- Per-user ticket limits: set a ceiling on how many tickets automatic assignment can send to any single agent.
- Capacity by ticket type: apply separate limits for Calling, Messaging, and Email/Other tickets so that a phone-heavy agent isn't blocked from getting chat tickets.
- Smarter definitions of "active" tickets: exclude tickets from the capacity count based on pipeline stage or ticket age, so stale work doesn't artificially block new assignments.
- Capacity-aware routing: automatic assignment skips agents who are at their limit and routes to someone with room.
- Visible capacity during manual reassignment: when a manager moves a ticket by hand, they can see whether the target agent is already at limit.
One hard line to know: Inbox capacity limits are still Enterprise-only. This update covers Help Desk tickets specifically, and it requires a Service Hub seat.
Why HubSpot Shipped This
The old model counted open tickets to decide who was available. That sounds logical until you watch it in action inside a real portal.
An agent can be sitting on 30 tickets that haven't moved in two weeks. The system sees 30 open tickets and treats that human as slammed. Meanwhile, a newer agent with 5 fast-moving tickets gets buried because the routing engine thinks they have headroom.
We've seen this pattern in portals running 10-person support teams and 50-person support teams. The size doesn't matter. The broken feedback loop does.
HubSpot's answer is a capacity model that reflects reality. Stale tickets don't count the same way live tickets do. Different ticket types carry different weight. And agents can finally see their own load instead of guessing.
How to Use It Step by Step
You'll configure this inside your Help Desk settings. Here's the path:
- Go to Settings, then Inbox and Help Desk, then Help Desk.
- Open the Routing tab and find the Capacity Limits section.
- Enable capacity limits and choose your limit type: a single limit for all ticket types or separate limits for Calling, Messaging, and Email/Other.
- Set per-user limits. You can customize limits per agent if their role or workload differs from the team default.
- Define your "active" ticket rules. Choose which pipeline stages count toward capacity and set a ticket-age threshold after which a ticket stops counting.
- Save your settings and run a test assignment to confirm routing is skipping agents at capacity.
Start conservative. Set your initial limits a bit higher than you think is right, watch the routing data for two weeks, then dial in from there.
What It Touches in Your HubSpot Strategy
This update lives in Service Hub, but its ripples go further than one tool.
Help Desk routing is the first place this lands. Automatic assignment now respects limits, which means your round-robin or load-balancing logic gets smarter without you rebuilding it from scratch.
Ticket properties and pipeline stages feed directly into the capacity definition. If you haven't audited your pipeline stages recently, now's the time.
Key Takeaway
Your "active" ticket definition is the most important decision you'll make during setup. A misconfigured age threshold or wrong pipeline stage exclusion means capacity numbers won't reflect reality, and routing will fail silently.
Reporting is the next layer. Capacity data opens up new questions: which agents hit their limit most often, which ticket types create the most congestion, and whether your team size actually matches your ticket volume. Combine this with Help Desk performance reports to see the full picture.
If you've recently worked through the Service Hub update locking Help Desk email sending to Service users only, Ticket Capacity Limits is the natural next configuration step. Both updates push toward a tighter, more intentional Help Desk setup.
If your portal hasn't had a full audit in a while, it's worth running through a comprehensive HubSpot portal audit before you configure capacity rules. Stale pipeline stages or miscategorized tickets will undermine the whole system.
Key Takeaway
Capacity limits only work as well as your ticket data. Clean pipeline stages, consistent ticket type usage, and accurate ticket age data are prerequisites, not afterthoughts.
Workflow automations that close, reassign, or escalate tickets may also interact with capacity counts. Review any ticket-based workflows after you set limits to make sure automated actions aren't inflating or deflating capacity numbers unexpectedly.
Who Should Care Most
This update is built for a specific moment in a company's growth. Here's who it hits hardest:
- Service managers at companies with 5 to 30 support agents who've been using manual reassignment as a workaround for uneven load distribution.
- HubSpot admins on Service Hub Pro who've wanted capacity-aware routing but couldn't justify the Enterprise upgrade just for this feature.
- RevOps leaders who own both the CRM and the service function and want routing logic that doesn't require constant manual intervention.
- Support team leads managing humans across multiple ticket channels (phone, chat, email) who've watched a one-size-fits-all limit break down by ticket type.
If you're on Enterprise, you likely already have this. If you're on Starter or Free, this doesn't apply yet. The sweet spot is exactly Pro.
George's Take
I've watched support teams at the Pro tier build elaborate workarounds for exactly this problem. Custom properties, manual triage queues, Slack alerts when someone's ticket count hits a certain number. All of it is duct tape. HubSpot bringing real capacity logic to Pro means those humans can stop managing their routing system and start focusing on the customers waiting on the other end of the ticket. The ticket-type separation is the detail I'm most excited about. Calling is not the same workload as email, and treating them the same was always a flawed assumption baked into simpler routing models.
“Capacity limits aren't an admin feature. They're a people feature. When routing respects how much a human can actually handle, the whole service experience gets better, for agents and for customers.”
If you're rethinking your Help Desk setup more broadly, pair this with the Universal Record Page beta so your agents get faster access to ticket context right alongside smarter routing.
If you want help configuring Ticket Capacity Limits or auditing your full Help Desk setup before you turn this on, let's talk. Book a strategy call with the Sidekick team and we'll walk through your portal together.
Frequently Asked Questions
What are Ticket Capacity Limits in HubSpot Service Hub Pro?
Ticket Capacity Limits let admins set a maximum number of tickets that can be automatically assigned to each agent. You can set separate limits by ticket type (Calling, Messaging, Email/Other), exclude inactive tickets from the count, and give agents visibility into their own workload. It's available in Service Hub Professional and Enterprise.
Is Ticket Capacity Limits available on Service Hub Starter or Free?
No. Ticket Capacity Limits for Help Desk are available on Service Hub Professional and Enterprise only. A Service Hub seat is also required. Inbox capacity limits remain an Enterprise-only feature and are not included in this Pro release.
How does HubSpot define an "active" ticket for capacity purposes?
HubSpot lets admins configure which tickets count toward an agent's capacity. You can exclude tickets based on pipeline stage or ticket age. This means stale tickets that haven't moved in weeks don't unfairly block new assignments from reaching an agent who's actually available.
Can I set different capacity limits for different agents?
Yes. While you can set a team-wide default, HubSpot allows per-user customization. If some agents handle higher-complexity tickets or have different roles, you can give them individual limits that reflect their actual workload rather than applying one number across the whole team.
Will Ticket Capacity Limits affect my existing ticket workflows or automations?
Potentially yes. Automated actions that close, reassign, or change ticket stages may interact with how capacity is counted. After you configure limits, review your ticket-based workflows to make sure automated ticket movement isn't creating inaccurate capacity signals for your routing engine.
Where do I configure Ticket Capacity Limits in HubSpot?
Go to Settings, then Inbox and Help Desk, then Help Desk, then open the Routing tab. You'll find the Capacity Limits section there. Enable limits, choose whether to apply one limit or separate limits by ticket type, set per-user numbers, and define your active ticket criteria before saving.
