HubSpot's Customer Agent answers customers on live chat, email, WhatsApp and Facebook Messenger, and the Fall 2026 Spotlight added voice as a public beta, along with new handoff controls. On WhatsApp, where people expect a quick and personal reply, the real decision is not whether the agent can answer, but which questions it should answer and which belong with a person.
What Customer Agent is, and what it needs
Customer Agent, once branded Breeze Customer Agent, is HubSpot's AI agent for customer conversations. It needs a Professional or Enterprise subscription to Marketing Hub, Sales Hub, Service Hub, Content Hub, Data Hub, Smart CRM or Revenue Hub, plus HubSpot Credits (HubSpot knowledge base). To publish it you need at least one Facebook, WhatsApp or live chat channel connected to the conversations inbox or help desk. An agent cannot be deleted once created, only paused or edited.
HubSpot lists its channels as live chat, email, forms, WhatsApp, Facebook Messenger, calling (beta) and, for accounts in a separate beta, custom channels (deploying the agent to channels). WhatsApp is not new: the agent was reported working on WhatsApp and Messenger in 2025 (MarTech, July 2025), and this autumn's Spotlight lists no WhatsApp-specific change to the agent.
Voice comes with conditions. It needs Sales Hub or Service Hub Professional or Enterprise, a Super Admin to opt in to the beta, an existing customer agent and a HubSpot calling channel on a HubSpot-provided number. It takes inbound calls only, and HubSpot describes the beta as "optimized for inbound support use cases" (setting up voice).
How it decides to answer, ask or hand over
HubSpot puts it plainly: "Based on its confidence levels, the customer agent will either generate a response backed by a verifiable source, ask follow-up questions to clarify the visitor's request, or reassign the conversation to a human agent." By default it hands over when it cannot answer, when the customer asks for a person, or when the agent is paused.
You add your own rules as handoff guidelines, such as "Cancellation" or "Refund", and choose live handoff to the next available person, async handoff for a later follow-up, or no handoff. Conversations can route to an inbox or help desk, to named users or teams, or through workflows, though only users with a Sales or Service seat can be in routing rules. A "Customer Agent ticket status" property shows whether a conversation is pending, awaiting a person or handed off (the handoff process).
You also set its hours (all hours, set hours or only outside them) and a coverage percentage, so it takes only a share of conversations at first. The Fall 2026 release added fallback routing, which passes conversations to the agent when nobody is free (HubSpot Spotlight).
What it knows: your content, and a little of the record
The agent answers from sources you give it: knowledge base articles, website pages, blog posts, public URLs, uploaded files such as PDFs, hand-written "short answers", and questions and answers generated from resolved tickets or past conversations. Sources marked private are not cited, but their content "may still appear in responses", so upload nothing you would not want said to a customer (content sources).
CRM access is narrower than people expect: "The customer agent can only currently access or update contact properties. You can add a maximum of 10 properties." Each property has a protection level, such as matching the customer's email address or sending a verification link, before the agent shares anything (CRM data access). So "where is my application?" only works if the answer sits in a contact property, not on a deal, ticket or custom object.
What it costs, and what counts as a resolution
Since 14 April 2026 HubSpot has charged for outcomes: USD 0.50 per resolved conversation, or 50 HubSpot Credits, down from USD 1.00 per conversation (HubSpot newsroom). Voice costs USD 0.50 a minute for the time the agent is on the call, including before a transfer. Extra credits are USD 10 per 1,000 (Product and Services Catalog).
A conversation counts as resolved when the agent shares a content source or performs an action and there is no qualifying handoff within 72 hours of the customer's last message, or when a lead is marked as qualified, partially qualified or not qualified. Only handoffs the customer starts, by asking for a person or triggering a handoff guideline, stop a resolution counting. A conversation your team reassigns by hand, or through a workflow, can still count. Credits are charged per resolution, not per message, and when they run out the agent stops taking new conversations. You can opt in to 14 days of free access when you first set it up (how resolutions are counted).
WhatsApp's rules, and where Flowella fits
On WhatsApp the agent uses HubSpot's own channel, which needs Marketing Hub or Service Hub Professional or Enterprise and a WhatsApp Business account connected through Meta's set-up window. The number cannot already be on another WhatsApp account or integration unless you use coexistence (connecting WhatsApp). Three rules shape what an agent can do there:
- The 24-hour window. You can reply freely for 24 hours after the customer's last message. After that, only an approved template will send, so an async handoff on WhatsApp has a clock on it.
- Meta's messaging limits. A new business portfolio can message 250 people in a rolling 24 hours outside that window. Business verification can raise this to 2,000, and steady, good-quality sending raises it automatically from there. The limit is shared across all the portfolio's numbers (Meta's developer documentation).
- Templates. HubSpot cannot sync templates with a location header or Flow buttons, only contact and company personalisation tokens work, and workflow sends need opt-in consent (WhatsApp templates in HubSpot).
That missing Flow button is where Flowella, from our sister company, comes in. It is not a chatbot. It turns your HubSpot forms into WhatsApp Flows: short, multi-screen forms with dropdowns, dates and choices, answered inside the chat. The answers come back as HubSpot form submissions, so the lists, scoring and workflows you already have act on them.
The two do different jobs. If the customer needs an answer ("When is the next open day?", "Can I park on site?"), that is the agent's job. If you need information from the customer in a shape your CRM can use, such as a booking or a course choice, that is a form, and on WhatsApp that is a Flow sent from a workflow. Plenty of teams will want both.
What the agent should answer, and what must go to a person
Our rule of thumb: the agent answers what is published and the same for everyone; anything that needs judgement, care or authority goes to a person.
Good for the agent:
- Opening hours, dates, locations, parking and what to bring.
- How to apply, book, renew or join, with a link to the right page.
- Entry requirements, eligibility rules and policies, as written.
- Status questions, but only where the answer sits in a contact property and the customer's identity is checked.
Always to a person:
- Complaints. They need a person, and often a formal process.
- Safeguarding. Any sign that a child or vulnerable adult may be at risk goes straight to trained staff, by live handoff in hours and a clear route outside them. The agent should never try to handle it.
- Money. Refunds, fee disputes, failed payments, discounts and hardship requests.
- Decisions about a person. Offers, exceptions, cancellations and anything a policy leaves to discretion.
- Anyone who asks for a person, and any topic your content does not cover.
Write each of these as a handoff guideline, not a later reassignment by staff, so the handoff happens at the right moment and is not billed as a resolution. People rarely type "safeguarding", so word guidelines broadly and test them with real examples. HubSpot's batch testing runs the agent against real customer questions before go-live, at no credit cost, and a low coverage percentage lets you start small. After launch, review handed-off conversations weekly and turn repeated questions into short answers.
We set up Customer Agent and WhatsApp journeys for HubSpot clients, starting with the content and the handoff rules rather than the switch. If you are weighing up an agent on WhatsApp, see how we approach AI for HubSpot.