HubSpot now charges only when its support agent resolves the ticket

Bottom line. Since 14 Apr 2026, HubSpot’s Breeze Customer Agent costs $0.50 per resolved conversation instead of $1.00 per conversation. If you run a small support queue on HubSpot Pro or Enterprise, that flips the math in your favour: you pay when the bot actually closes a ticket without a human. The one term to read before you switch it on is HubSpot’s definition of resolved.

HubSpot moved its Breeze Customer Agent to outcome-based pricing on 14 Apr 2026: $0.50 per resolved conversation, down from a flat $1.00 per conversation. The Prospecting Agent moved the same way, to $1.00 per lead recommended for outreach. Both now come with a 28-day free trial, and both require a Pro or Enterprise plan.

The reasoning HubSpot put behind it is the reason to pay attention:

“Businesses are being asked to make big bets on AI right now. Too often, that means paying for potential rather than performance. Outcome-based pricing removes that risk.”

— Jon Dick, Chief Customer Officer, HubSpot, on the 14 Apr 2026 change.

The definition that decides your bill

Here is the part to read twice. HubSpot’s documentation defines a resolved conversation as one where the agent shares a content source or performs an action, and there is no handoff to a human agent within 72 hours of the last message. Resolution is evaluated and locked 72 hours after the agent’s last reply.

Two consequences follow, and both work in your favour. A conversation the agent handles but that one of your people touches inside 72 hours is not billed. And a conversation that goes quiet and reopens after 72 hours starts a fresh window rather than stacking charges.

Pricing from HubSpot’s announcement, 14 Apr 2026.

The math for a small team

Run it against your own volume, not a vendor example. Say you handle 200 support conversations a month. Under the old model you paid for every one the agent touched. Under the new one you pay only for the ones it closes cleanly, so your bill tracks your genuine deflection rate. That is the number to find out, and the 28-day trial exists precisely so you can measure it before you commit.

The comparison that matters is not $0.50 against zero. It is $0.50 per resolved ticket against your loaded cost per human-handled ticket. If the agent cleanly resolves a useful share of those 200 at $0.50 each, the question answers itself; if it resolves very few, the small bill is also telling you the agent is not deflecting much.

Where it does not fit

Outcome pricing is better for you only if the agent actually resolves things. If your knowledge base is thin or your queries are non-standard, a low resolution rate means few billed conversations but also little deflection, and you are back to paying people for the rest. The pricing change does not fix a weak knowledge base; it stops you paying for the bot’s misses. For a small support function, the cheaper experiment is now genuinely cheap, which makes the trial worth running, and the solo-founder customer-service stack read is the next step if you outgrow the agent’s reach.

The enterprise version of this cost discipline, watching what agents consume rather than what they list at, is in the agentic-AI cost-governance read; the small-business framing of the broader support stack sits in the AI customer service for small business piece and the solopreneur stack-consolidation read.

What changes this verdict

Cadence on this piece is 30 days, because vendor pricing on AI agents is moving fast and HubSpot could adjust the per-resolution rate, the resolution definition, or the plan requirement. The three changes that would move the recommendation: HubSpot raising the $0.50 rate or narrowing the 72-hour resolution window; HubSpot extending the agents below the Pro plan, which would widen who this is for; or a competing help desk shipping a comparable outcome-priced agent that a small team already on that platform should weigh instead. We re-test against HubSpot’s published pricing on or before 5 Jul 2026; the Holding-up record for OPS-091 carries any change, dated.