How to answer your team's "how do we do this in HubSpot?" questions with a HubSpot Agent

How many times this week has someone asked which property to use, which pipeline a deal belongs in, or what "SQL" actually means in your business? And how often has the answer depended on whoever happened to be free? You can hand those questions to an internal HubSpot agent.

It's built in Agent Builder (HubSpot's tool for creating custom agents, formerly Breeze Studio) and grounded in a knowledge vault, which is a store of your own documentation that the agent draws on. It answers your team in plain language using your portal's rules, and passes anything it can't answer to your HubSpot admin.

This article covers what the agent does, where it earns its keep, who should own it, and what to get right before you build it.

Example use cases this suits well:

• The new starter's first fortnight. A new SDR asks the agent how "Lead status" and "Lifecycle stage" differ in your portal. They get your definitions and your rules for when to change each one, instead of HubSpot's generic explanation.
• The three-region-properties problem. A marketing executive building a list can't tell which of three similar "region" properties is the live one. The agent points them to the correct property and explains that the other two are legacy fields kept for reporting history.
• The upsell that went into the wrong pipeline. An account manager asks whether an expansion deal belongs in the new business pipeline or the renewals pipeline. The agent gives them your rule, plus the deal stages they'll need to move it through.

The idea, in short: An internal HubSpot agent answers staff questions about how your company specifically uses HubSpot. That covers which properties mean what, which pipelines and processes apply, and which naming conventions to follow. It draws only on documentation your HubSpot admin maintains in a knowledge vault. When it can't answer confidently, it routes the question to the admin, and each gap it finds becomes the next piece of documentation to write.

Top tip: record the reason behind every rule.
An agent that knows why a rule exists handles edge cases far better than one that only knows the rule, and your team is more likely to follow a rule when the answer explains it.

Who should own this: Your HubSpot admin or RevOps manager. They already answer these questions; they own the property model and pipeline design, and they're the only person who can tell a current rule from a retired one. Team leads play a supporting role by flagging questions the agent gets wrong, but the vault content needs one accountable owner. If ownership is shared across a committee, the vault goes stale.

Considerations for the build:

• Write it down before you build. The agent can only be as good as your documentation. If your definitions currently live in one person's head, get them written down first. The property descriptions already in your portal are a useful starting point.
• Keep the scope to your portal. Generic "how do I build a workflow in HubSpot" questions are better served by HubSpot's own Knowledge Base or Breeze Assistant. Your agent should focus on the things only your business knows.
• Decide the escalation route up front. Choose where unanswered questions go, who picks them up, and how quickly. Treat that log as your documentation backlog.
• Build vault updates into your change process. Every new property, retired pipeline, or renamed stage needs a matching vault update. Otherwise, the agent will confidently describe a portal that no longer exists.
• Keep it read-only. This agent explains your portal and doesn't need permission to change records. Holding back write access keeps the risk low while you build trust in its answers.
• Check what goes in the vault. Internal process documents sometimes contain client names, pricing, or commercially sensitive notes. Strip those out before anything is loaded; do not upload everything.
• Estimate usage against credits. Custom agents consume HubSpot Credits every time they run, so model your likely question volume before rolling the agent out to the whole team.

Common mistake to avoid: Loading the agent with your original implementation documents. The onboarding deck and process guide from your first HubSpot rollout are tempting because they already exist. They're also usually out of date: pipelines have been restructured, properties renamed, and lifecycle rules tightened since then. The agent can't tell a current rule from a retired one, so it answers either way with equal confidence. Audit every document against the live portal before it goes in.

Once it's working, you'll notice it quickly. Your admin's inbox gets quieter. New starters find their own answers in their first fortnight instead of waiting on a colleague. The questions the agent can't answer give you a running list of what to document next. The agent is never finished, but each gap it exposes makes your portal a little easier to use for everyone.

FAQs

Can a HubSpot agent answer questions about how our own portal is set up?
Yes, as long as you give it documentation to draw on. A custom agent grounded in a knowledge vault of your property definitions, pipeline rules, and naming conventions can answer questions specific to your business. It only knows what you've documented, though. It can't reliably work out your processes from the portal configuration alone.

What HubSpot subscription do I need to build an internal agent? The Agent Builder is included in the Starter, Professional, and Enterprise editions of HubSpot. Custom agents consume HubSpot Credits each time they run. The exact running cost depends on how often your team uses the agent and the complexity of the tasks it performs (measured in 'action units'). Be sure to check your monthly credit allowance before rolling it out widely

How is this different from asking Breeze Assistant? 
Breeze Assistant is a general HubSpot AI helper, and it's good at explaining how HubSpot features work. An internal agent answers questions about your portal: which of your properties to use, which of your pipelines applies, and what your terms mean. The two work well side by side. Breeze Assistant covers the platform and your agent covers your conventions.

How do I stop the agent giving outdated answers? 
Make vault updates part of your change process. Whenever a property, pipeline, or process changes, update the matching documentation at the same time. Audit any older documents against the live portal before loading them, because outdated source material is the most common reason these agents give wrong answers confidently.

Should an internal agent be allowed to update records? 
For this use case, no. Its job is to explain your portal, not to change it, and read-only access keeps the risk low. If you later want an agent that acts on records, build it as a separate agent with its own scope and checks.

Written by Mel Baker - HubSpot Marketing Consultant