Testing HubSpot’s Breeze Assistant – what it can actually do today

HubSpot's Breeze Assistant continues to evolve at a rapid pace, and over the past few weeks we’ve run a few tests across desktop and mobile to understand what it can actually deliver today.

Our aim is simple: identify the real operational value, map the limits, and define where teams should proceed with caution before relying on it inside a production CRM.

Below are some of the capabilities that are working well, the areas that still need guardrails, and what HubSpot’s expansion into mobile and third-party ecosystems means for day-to-day users

1. Task creation: useful, but not hands-off

Breeze can create tasks with due dates, descriptions, object associations and detailed instructions. This reduces the manual load, especially when you're on mobile or multitasking.

• But accuracy depends heavily on your understanding of your own CRM. When using voice-to-text, you need to know the exact record, deal, or pipeline you’re referring to, because Breeze can and does assign tasks to the wrong object if your instruction isn’t explicit. It’s helpful, but every output still requires verification.

Practical takeaway: Good for speeding up repetitive admin, but double-check associations every time.

2. Property creation: strong for simple fields, not for edits

Breeze is most reliable when creating new, straightforward properties with clear instructions. It can handle naming conventions, field types and option values, especially if you paste the values directly into the prompt.

• But editing existing properties, restructuring fields or changing dependencies remains risky. These actions can break workflows, reporting or segmentation without obvious immediate signs.

Practical takeaway: Use Breeze for property creation only. Test everything in a sandbox or low-risk record before applying changes to your main portal.

3. Workflow creation: basic automation only

Breeze can create simple workflows, add triggers and generate branching logic when the instructions are specific and the workflow is uncomplicated. For example, it can create branches for each value within a region property.

• But replicating this success for more complex workflows has been inconsistent. Breeze still requires you to understand what the workflow should look like — otherwise you can’t give correct instructions or confidently validate the result.

Practical takeaway: Use it to scaffold basic workflows, not to build anything business-critical or multi-layered.

4. CRM Record updates: fast but requires oversight

Breeze can update CRM records — changing deal stages, marking tasks complete, adjusting lifecycle values and updating properties. This is where the assistant can save time, especially when you’re cleaning up data or managing follow-ups.

• However, accuracy is entirely dependent on your clarity. If your instruction is vague, Breeze may update the wrong field.

Practical takeaway: Good for quick record updates, but always check the record afterward.

5. Mobile testing: where Breeze becomes genuinely productive

We also tested Breeze on mobile, and this is where the assistant shows real potential. Voice-to-text works well, allowing you to create tasks, update records or draft follow-ups through natural conversation.

The assistant can also summarise meetings, qualify prospects and book meetings — letting you complete CRM actions in the moment, rather than waiting to get back to a desktop.

With integrations expanding into Google Workspace, Microsoft 365 and Slack, you can now draft follow-ups or summarise discussions directly on your phone. It’s clear HubSpot is moving beyond simple timeline summaries and toward a mobile-first AI workflow layer.

Practical takeaway: Strong for on-the-go updates and follow-ups, but still requires specific instructions and post-action review.

Final take: valuable progress, but not a replacement for CRM expertise

Breeze Assistant is becoming a meaningful operational tool, particularly for quick tasks, simple workflows and basic property creation. But every successful outcome still depends on two things:

1. Your understanding of how HubSpot is structured

2. Your ability to check its work

It’s not a “set and forget” assistant. It’s a productivity layer that accelerates admin when you already know what the correct output should look like. If you’re unclear on the workflow, field structure or CRM logic, Breeze won’t fix that for you — and it may create more problems than it solves.

The safest approach is consistent across all use cases:
Start with low-risk actions, test everything in sandbox or on dummy records, and expand only when you’re confident in the results.

When used with guardrails, Breeze Assistant can meaningfully reduce manual effort and support cleaner, more consistent CRM operations. But it still requires operators who understand what “good” looks like.