Skip to content
Product Agents

Search Product Agents

Start with a guide, or search a topic

    New here? Read the five guides in order

    Subscribe

    HubSpot Customer Agent

    HubSpot’s Customer Agent bills when the customer goes quiet for 72 hours.

    HubSpot charges $0.50 per resolution, and a resolution is a sourced answer followed by 72 hours in which the customer never asks for a person. That one rule sets the bill, the reports and the handoff design.

    HubSpot’s illustration of a Customer Agent named TitanAssist: a Test Customer Agent button over the agent’s settings, a chat where a customer says “I’m having trouble with my dashboard” and the agent asks for details and links a troubleshooting article, a Coverage card showing 62% handled by the agent, and a channel table for calling and email.
    Image: HubSpot · Customer Agent product page

    At a glance#

    What it does

    Answers customers from the team’s knowledge sources on chat, email, WhatsApp, Facebook Messenger and forms. It can read or edit up to ten contact fields, call the team’s own APIs, and hand off to a person. Voice is in public beta.

    Who it’s for

    HubSpot customers on the Professional or Enterprise edition of any hub. HubSpot told investors in August 2026 that more than 10,000 customers use it.

    Price

    $0.50 per resolved conversation, charged as 50 HubSpot Credits, since April 14, 2026. Before that, $1.00 per conversation. Professional includes 3,000 credits a month (60 resolutions), Enterprise 5,000 (100). Extra credits are $10 per 1,000. Voice is 50 credits per minute.

    Model

    Not named. The docs say “powered by HubSpot’s AI,” and the CEO told investors HubSpot picks and chooses among AI models.

    Takes actions?

    Yes, with no person approving each one. Field edits and API actions carry an identity check the admin sets: none, match the email on file, or verify by emailed link.

    Claimed results

    72% of support tickets resolved without human escalation, per the Q2 2026 earnings call. The product page claims a 70% average resolution rate, with top teams at 90%, and 84% higher ticket resolution rates on average.

    Launched

    September 2024 as one of four Breeze agents at INBOUND, HubSpot’s annual conference. Outcome pricing April 14, 2026. Voice (beta), batch testing, knowledge generation from resolved tickets and a redesigned Agent Hub at UNBOUND, September 16 to 18, 2026.

    Why it matters#

    HubSpot’s Customer Agent lives inside the CRM that HubSpot’s 306,000 customers already run. Since April 2026 it costs $0.50 per resolution, down from $1.00 per conversation. HubSpot’s pitch is “you pay when it works, full stop.” So the whole product turns on one question: what is a resolution?

    Read this teardown for the answer. A resolution is a reply that cites a source or runs an action, followed by 72 hours in which the customer never asks for a person. Only the customer can stop that clock. A rep taking over by hand does not. That rule sets the bill, the dashboards and the handoff design, and I read the 72% HubSpot gave investors as the same number.

    How it works#

    What happens when a request reaches HubSpot Customer Agent.

    1. Take the conversation

      A customer writes in on chat, email or WhatsApp. The team sets what share of conversations the agent takes (Conversation coverage), during which hours, and for which contact segments.

    2. Answer from sources

      The agent answers from knowledge base articles, site pages, uploaded files and short answers, with citations. Private sources are never cited, but their content can still appear in a reply.

    3. Check identity, then act

      “Where is my order?” triggers an action, a GET or POST call to the team’s own API, and the agent explains the result using the response instructions. The admin chose its protection level: none, match the customer’s email to the contact record, or send a verification link and wait for the click.

    4. Hand off, or keep going

      If the customer asks for a person or hits a handoff phrase, the agent transfers the chat, live or for later, to users, a team or a workflow; the ticket gets a summary and the handoff reason. If the agent cannot answer, it asks the customer to rephrase or transfers.

    5. Wait 72 hours, then bill

      Three days after the customer’s last message, HubSpot checks for a qualifying handoff. If there was none and the agent cited a source or ran an action, the conversation is resolved and 50 credits ($0.50) are charged.

    6. Coach

      Reps open agent insights on any reply to see the sources used, actions triggered and knowledge gaps, then rate it or click Coach agent. Coaching opportunities group failures by knowledge, handoff, experience or action, and previews are free.

    The decisions worth studying#

    What they chose, why, and what it costs.

    1It charges per resolution, and a resolution is a timer only the customer can stop

    On April 14, 2026 HubSpot moved Customer Agent from $1.00 per conversation to $0.50 per resolved conversation. A conversation resolves when the agent sent a reply that shared a source or performed an action, and no qualifying handoff followed within 72 hours of the customer’s last message. Only two things qualify: the customer asks for a human, or their message matches a handoff phrase or guideline the team set.

    So a rep who takes a chat over by hand, or a workflow that reassigns it, does not cancel the resolution. The reporting guide still counts those transfers as handoffs, so one conversation can sit in both charts. A customer who gives up after a cited but wrong answer resolves too.

    My read: HubSpot picked the customer’s behavior as the meter because nobody can accuse the vendor of gaming it. The cost: the invoice, the resolution rate and the 72% quoted to investors are one number, and none checks whether the problem was solved.

    HubSpot · Ticket note after handoffProduct screenshot
    A ticket note from Bikey at 9:41 AM titled “Bike pump selection guidance”: “Handoff reason: Asked to speak to a human or trigger phrase matched”, then a Conversation summary: the customer asked about recommended bike pumps, Bikey suggested a floor pump and a portable mini pump and explained valve compatibility, “Customer requested human support agent”, and “Bikey informed no agents available and follow-up will occur via email”.
    On HubSpot’s tour ticket, the handoff reason reads “Asked to speak to a human or trigger phrase matched.” Those are the two handoffs that stop the 72-hour clock. HubSpot guided tour · step 5 of 10

    2Data access is granted one field at a time, each with its own identity check

    The admin picks up to ten contact properties the agent may touch, and toggles view and edit separately for each. Each grant carries an identity check: match the email the customer gives against the contact record, or send a verification link and wait for the click. Custom actions, which are calls to your own API, take the same two checks plus a third option, none.

    My read: this is the best data-access design in the set, and worth copying as is. Reading an address and changing it are different operations, and the admin never has to allow editing in order to answer a question.

    Two limits. No person approves an individual change or action; publishing an action approves every future call under its conditions. And HubSpot’s Undo for property changes excludes changes made by workflows, the API or connected apps, so reversing what the agent changed is not documented. HubSpot’s own advice for sensitive account changes is to send a secure link and never make the change in chat.

    3Handoff routes the conversation. Nothing makes a person take it.

    The team chooses live handoff, async handoff or none, and routes to specific users, a team or a workflow. HubSpot’s docs say routing to a team only skips the availability check, so the handoff goes through when nobody is online. HubSpot’s guided tour shows the result. The customer asks for a human and hears that no one is available. The ticket lands in an “Awaiting Human Assignment” view with status New and owner “No owner.” The ticket does carry a summary and the handoff reason.

    At UNBOUND in September 2026 HubSpot added handoff guidelines, so the agent knows when to transfer, and fallback routing the other way, sending conversations to the agent when humans are unavailable.

    My read: the agent’s job ends at the queue, and the pricing agrees. A handoff is unbilled, so nothing in the model rewards finishing it. Staffing that queue is the buyer’s problem, and an async handoff that sits unowned is a promise the customer never heard.

    HubSpot · Help desk queueProduct screenshot
    HubSpot Help Desk view “Awaiting Human Assignment (5)” with filters for Ticket owner, Priority, Pipeline, Ticket status and Assigned teams. Four visible tickets, three Live Chat and one Email, each show a Customer Agent Status of “Awaiting Human A…” and Ticket owner “No owner”; the fourth is “Ticket #47964259995”, from 20 minutes ago.
    Five tickets wait for a human in HubSpot’s tour. Each is routed, and none has an owner. HubSpot guided tour · step 4 of 10

    4Running out of credits turns the agent off

    Every account gets a monthly pool of HubSpot Credits that resets and does not roll over. Professional includes 3,000, which is 60 resolutions. Enterprise includes 5,000, or 100. Extra capacity is $10 per 1,000 credits, or $0.01 per credit pay as you go, but overage has to be switched on. By default, when the pool is empty the agent stops being assigned new conversations on every channel until the reset date or a top-up.

    For example, 1,000 conversations a month at HubSpot’s 72% rate is 720 resolutions, 36,000 credits, and about $310 beyond Enterprise’s included 5,000. Previews and reply recommendations are free. Voice is billed per minute, 50 credits, so outcome pricing stops at the phone.

    My read: the included pool is a trial size, and the default pause is a kill switch tied to budget. A good month can quietly turn the agent off in week three. Enable overage with a cap, or put the day the pool runs dry on someone’s calendar.

    What to watch#

    • The bill and the scoreboard are the same number

      Resolution rate, the resolutions chart and the invoice all use the 72-hour rule. Write down what you will count as solved before you compare months, and sample resolved conversations for repeat contacts.

    • Private sources leak into replies

      HubSpot says content from private sources is never cited but can still appear in answers. Keep internal exceptions and staff notes out of the agent’s sources.

    • Protection level none exists

      A custom action can run with no identity check at all. Treat the agent’s recognition of a visitor as a hint, and make your own API enforce who may change what.

    • The model is a black box

      HubSpot does not name the model behind Customer Agent and says it picks among providers. Answer quality can shift without a release note, so keep a batch test you rerun after every change.

    What it means for your team#

    What to decide before you ship an agent like HubSpot Customer Agent.

    • Finance

      Budget in credits per month: 50 per text resolution, 50 per voice minute, no rollover. Decide whether overage is on and at what cap, because the default is a paused agent.

    • Support

      Route handoffs to specific users and teams, since team-only routing ignores availability, and own the Awaiting Human Assignment view. Read a weekly sample of resolved chats where a rep had stepped in by hand.

    • Security

      Set every field grant and action to match or verify email, never none, and make your endpoint check that the verified customer may touch the record requested. A valid API key identifies HubSpot, never the visitor.

    • Product

      Start with a low conversation coverage percentage and raise it after batch tests pass. Report lead qualification apart from support, because a lead marked unqualified counts as resolved the moment it is marked.

    Steal this

    1. Grant the agent customer fields one at a time, each with the identity check it needs.

    2. Publish the exact rule behind any number you bill on, including its clock and what it ignores.

    3. Make an empty budget pause the agent loudly, and tell the team the day it happens.

    Reference#

    The evidence behind this teardown: recordings, sessions, what HubSpot Customer Agent gets right and wrong, and every source.

    Walkthrough · 4 frames

    From “What bike pump should I buy?” to a ticket with no owner#

    Frames from HubSpot’s guided tour of the Customer Agent, a scripted BikeTools demo linked from HubSpot’s product page, captured September 20, 2026. A scripted product tour with staged screens, not a live agent: no real handoff or ticket was tested.

    1. Step 1 of 4: Bikey answers; the visitor asks for a human

      The Bikey chat, “Powered by AI”, answers “What bike pump should I buy?” with two options, a floor pump for home and a compact portable pump for rides, naming Bike Tools’ Portable Bike Pump beside an “Explore more” link marked 1. Below the answer: “2 Sources”, thumbs up and down, then the visitor’s message “Can I speak with a human?”.
      Image: HubSpot guided tour · step 3 of 10

      1. Bikey recommends the store’s own Portable Bike Pump and links a numbered source, “Explore more”.

      2. HubSpot counts a conversation with a shared source as resolved if no qualifying handoff follows within 72 hours of the visitor’s last reply.

      3. The visitor asks for a person, and in the tour the chat then ends with a promise of email follow-up.

    2. Step 2 of 4: The help desk queues tickets for a human

      HubSpot Help Desk view “Awaiting Human Assignment (5)” with filters for Ticket owner, Priority, Pipeline, Ticket status and Assigned teams. Four visible tickets, three Live Chat and one Email, each show a Customer Agent Status of “Awaiting Human A…” and Ticket owner “No owner”; the fourth is “Ticket #47964259995”, from 20 minutes ago.
      Image: HubSpot guided tour · step 4 of 10

      1. The help desk has a view for exactly this state: Awaiting Human Assignment, with five tickets.

      2. Each ticket waits for a human, and each Ticket owner reads “No owner”: routed, but not yet taken.

      3. Next, the tour opens Ticket #47964259995, a Live Chat from 20 minutes ago.

    3. Step 3 of 4: Bikey’s note gives a reason and summary

      A ticket note from Bikey at 9:41 AM titled “Bike pump selection guidance”: “Handoff reason: Asked to speak to a human or trigger phrase matched”, then a Conversation summary: the customer asked about recommended bike pumps, Bikey suggested a floor pump and a portable mini pump and explained valve compatibility, “Customer requested human support agent”, and “Bikey informed no agents available and follow-up will occur via email”.
      Image: HubSpot guided tour · step 5 of 10

      1. The handoff reason is one label for two triggers: “Asked to speak to a human or trigger phrase matched”.

      2. The summary carries the chat’s ending: the request for a human, then “no agents available and follow-up will occur via email”.

    4. Step 4 of 4: The ticket waits with no owner

      The ticket’s sidebar: Ticket owner “No owner”, Assigned teams “---”, Pipeline “Customer Support”, Ticket status “New”.
      Image: HubSpot guided tour · step 5 of 10

      1. The ticket has no owner and no assigned team, so no named person holds the work yet.

      2. Ticket status is New in the Customer Support pipeline: the handoff routed the conversation, and nobody has started on it.

    Sources#

    2. Understand the customer agentknowledge.hubspot.com
    7. Set up the customer agentknowledge.hubspot.com
    11. Undo property value changesknowledge.hubspot.com
    12. Manage HubSpot Creditsknowledge.hubspot.com

    Sources checked September 28, 2026.

    Next teardownAsana AI Teammates

    Asana’s AI Teammates are agents a person assigns tasks to, like a colleague.