HubSpot’s AI updates are starting to show up in places your team already works: campaign planning, Microsoft 365, and the CRM records reps rely on.
That’s a better direction than another shiny AI sidebar.
But it comes with a catch. These tools are only as strong as the context behind them. If the CRM is patchy, campaign goals are vague, or fields are out of date, AI will speed up the wrong things.
This week’s updates all point to the same job: get your sales and marketing foundations clear enough that AI has something solid to work with.
The short version
HubSpot has added or highlighted three AI and data updates that are worth a closer look:
- Breeze Assistant can help shape Loop Marketing campaign work inside HubSpot.
- HubSpot context can now be brought into Microsoft 365 Copilot through HubSpot’s Copilot agent.
- Data Enrichment can fill and refresh contact and company details in the CRM.
The shared theme is not “more AI”. It is context. HubSpot is trying to put CRM knowledge closer to the work your team is already doing.
That only pays off if the underlying setup is clean enough to trust.
1. Breeze Assistant can help with campaign planning
Source links: HubSpot What’s New; HubSpot Knowledge Base, Use Breeze Assistant.
HubSpot says Breeze Assistant can now guide teams through Loop Marketing tasks, including early campaign work such as defining ideal customer profiles and building campaign briefs.
That matters because the slow part of campaign planning is rarely the blank page. It is getting the right inputs together.
Who are we trying to reach? What do we know about them? What worked last time? Which offer or message is actually credible? What should sales do when someone responds?
If Breeze can pull more of that HubSpot context into the planning conversation, it can help the first campaign brief take shape faster.
The important bit is the word “first”.
You still need a person to challenge the angle, check the audience, and make sure the campaign sounds like something a real buyer would respond to. AI can prepare the rough shape. It should not be the final editor.
A simple way to test it:
- choose one upcoming campaign
- check the audience segment, offer, recent campaign results and source reporting first
- ask Breeze to help shape the brief
- have marketing and sales review the output together
- turn the result into a sharper human-owned brief
That is a better test than asking it for ten generic campaign ideas and hoping one feels right.
2. HubSpot context is moving into Microsoft 365 Copilot
Source links: HubSpot What’s New; HubSpot AI tools.
HubSpot has also made HubSpot data available inside Microsoft 365 Copilot through its HubSpot Agent for Microsoft 365 Copilot.
In plain English, this means CRM context can follow people into Microsoft tools they may already use every day.
For some teams, that is more interesting than another place to log in.
A sales manager might be reviewing account notes before a meeting. An operations person might be pulling context together for a pipeline discussion. A marketer might be checking whether a campaign audience lines up with the customer data already sitting in HubSpot.
The value is not that Copilot can summarise a record. The value is whether the team can make a better decision without losing the source of truth.
Before switching it on broadly, we would check four things:
- who should have access
- which records and fields are actually safe to surface
- what questions the team should use it for
- how people will check the answer before acting on it
That last point matters. CRM context inside Microsoft 365 is only a win if it keeps people closer to the truth. If it creates another place for half-checked answers to spread, it becomes a governance problem.
3. Data Enrichment can clean up the CRM inputs
Source links: HubSpot What’s New; HubSpot Knowledge Base, Get started with data enrichment.
HubSpot’s Data Enrichment update focuses on filling missing fields and refreshing stale contact and company records.
That sounds small, but it sits underneath almost everything else.
Poor CRM data affects lead routing, lifecycle reporting, campaign segmentation, sales prioritisation and AI output. If the system does not know who a company is, what industry they are in, or which fields matter to your process, every downstream workflow gets weaker.
Enrichment can help, but it should not be treated as a magic clean-up button.
You still need to decide which fields matter, which properties your team trusts, and where enriched data should trigger action. Otherwise, you risk filling the CRM with more data without making the system easier to use.
A sensible first pass is to pick a small number of fields that directly affect sales or marketing decisions. For example:
- company size
- industry
- region
- lifecycle stage
- source or campaign context
- owner or routing rules
Then test whether enrichment improves the decisions tied to those fields. If it does not change routing, follow-up, reporting or segmentation, it is probably not the first thing to prioritise.
What to check before turning these on
The common trap with AI features is turning them on because they are new, then working out the operating model later.
We would do it the other way around.
| Area | What to check first |
|---|---|
| Campaign planning | Whether your audience, offer, source reporting and sales handoff are clear enough for Breeze to work from. |
| Microsoft 365 access | Which teams need HubSpot context inside Copilot, and what they are allowed to ask or act on. |
| CRM data quality | Which contact and company fields actually drive routing, reporting, segmentation or sales follow-up. |
| Human approval | Where AI can prepare work, and where a person still needs to approve the final decision. |
If HubSpot is already central to your sales and marketing work, these updates are worth a controlled test.
If your portal is messy, start with the foundations. Clean up the fields, lists, lifecycle stages and campaign reporting first. The AI layer will only be as good as the CRM underneath it.
CLCK’s take
This is the direction we expected HubSpot to keep moving in.
AI is not sitting off to the side anymore. It is being pulled into the systems where teams plan campaigns, review customer context and decide what to do next.
That is good news for businesses with a clean CRM and clear rules of engagement.
It is less helpful for teams with patchy data, unclear ownership or too many half-used fields. In that case, the priority is not more AI. It is making the CRM easier to trust.
Our recommendation is simple:
- Pick one campaign planning use case for Breeze Assistant.
- Pilot HubSpot context in Microsoft 365 Copilot with a small sales or operations group.
- Choose a short list of CRM fields for Data Enrichment.
- Review what changed after two to four weeks.
- Keep the human approval step clear.
If the pilot saves time, improves handoffs, or gives the team cleaner context for decisions, expand it.
If it mostly creates more noise, tighten the CRM setup before rolling it further.
If you want help deciding which HubSpot AI and data updates are worth testing in your portal, book a strategy session with CLCK: