Breeze agents are HubSpot's AI agents that act on your CRM data to answer visitors, qualify leads, and draft content
An agent is only as good as the content and data behind it, so cleanup comes before configuration
Give each agent one narrow job and clear guardrails, then expand once it earns trust
Keep a human reviewing answers and handoffs while the agent is new
Measure accuracy and deflection, not just how many conversations the agent handled
Breeze is HubSpot's set of AI agents that work directly on your CRM. Instead of a chatbot bolted on the side, a Breeze agent draws on the content and records you already hold to answer visitors, qualify leads, and draft content, around the clock. The appeal is an agent that handles routine conversations and admin without adding headcount.
The risk is just as real. Point an agent at thin content or messy data and it will answer confidently and wrongly, in front of your prospects. That is why a good setup starts with the data and guardrails, not the configuration screen. Get those right and Breeze becomes a quiet, reliable extension of your team. Get them wrong and it becomes a liability talking to your buyers.
Breeze is evolving quickly, so confirm the exact menu names and availability against your own portal and tier before you build.
Step 1: Confirm Access and Plan
Log into your HubSpot account
Check that Breeze agents are included in your subscription, as access and limits vary by tier
Identify the specific agent you want first (customer, prospecting, or content), rather than switching on everything
Confirm in your portal which agents your plan supports before building around them
Step 2: Prepare the Knowledge Source
An agent answers from your content, so this step decides whether it helps or invents. In HubSpot, tidy the sources the agent will draw on:
Review your knowledge base articles for accuracy and gaps
Update key site pages the agent may reference
Make sure the records the agent uses are clean and current
Remove or fix outdated content that could produce wrong answers
Step 3: Create and Scope the Agent
Step 4: Set Behavior and Guardrails
Define what the agent can and can't do before it ever goes live:
Step 5: Test, Then Publish Narrow
Problem: The agent gives confident, wrong answers
Solution: Its knowledge source is thin or outdated. Improve the content it draws on and tighten what it is allowed to answer.
Problem: It tries to handle questions it shouldn't
Solution: Your guardrails are too loose. Narrow the topics it can answer and set clearer escalation rules to a human.
Problem: Prospects get frustrated and drop off
Solution: The agent isn't handing off soon enough. Lower the threshold for escalation so a person steps in faster on hard conversations.
Breeze agents are powerful because they act on your real CRM data, and risky for exactly the same reason. Start narrow, with one job, clean source content, clear guardrails, and a human watching. Set an agent up to be accurate before you set it up to be busy, and it becomes a dependable part of your team. This careful, data-first approach is how we turned marketing into a scalable revenue engine for Maple Assist, building automation on a clean foundation so it could be trusted to run. See the Maple Assist case study.
We treat AI agents as a data problem before we treat them as a configuration task:
This careful, data-first approach is how we turned marketing into a scalable revenue engine for Maple Assist, building automation on a clean foundation so it could be trusted to run. See the Maple Assist case study.