All hands on deck. This is not a drill.

If your team uses HubSpot and Slack, Breeze Assistant can now jump into Slack threads and help you work with CRM data without making you leave the conversation.

Yes, technically breeze has been “in slack” for a while, but this new update is going to give it super powers.

Plus, breeze itself has improved so much as of late, it just further increases the impact of the slack connector.

You can @mention Breeze in a Slack thread and ask it to summarize a contact, company, deal, or ticket. You can also have it create tasks, log notes, prep you for meetings, or summarize the Slack thread itself and save that summary back to HubSpot.

That last part is the one really caught my attention.

Because a lot of important customer context does not start in HubSpot. It starts in Slack.

Someone asks, “What’s going on with this deal?”
Someone else drops in the backstory.
A CSM adds the latest blocker.
Sales shares what they heard on the last call.
Then everyone moves on, and that context? Just stays in slack.

Now, in theory, you can pull Breeze into the thread, summarize what happened, and log it back to the CRM record where it actually belongs.

That is very useful.

A few important notes: Breeze only responds when it is explicitly @mentioned, so it is not just lurking in your channels like a tiny CRM gremlin.

It also only works in channel threads, and you need the HubSpot Slack app connected plus Breeze Assistant turned on in your portal.

But still. This is a big step toward making HubSpot less of a place you “go update later” and more of something that can meet your team where the work is already happening.

Very worth testing if your Slack is where customer context currently goes to become impossible to find.

Don’t Make a New Form - Make a Form + URL Workflow
If your HubSpot portal has 47 versions of basically the same form, this one is for you.

This happens all the time. A team has one form for the pricing page, one for the demo page, one for the events page, one for the partner page, one for the “actually this is the same form but we need to know where it came from” page, and suddenly your forms tool looks like someone opened a junk drawer and gave it embed codes.

The instinct makes sense. You want to know where the person converted. But making a brand new form every time you need a slightly different attribution path is usually not the cleanest way to do that.

A better setup is:

Use one master form, then let the page URL tell HubSpot what happened.

So instead of building:

“Contact Us - Homepage”
“Contact Us - Pricing”
“Contact Us - Events”
ETC.

You build one form and create workflows that look at the form submission page URL.

If someone submits the form on a catering page, set the inquiry type to catering.

If they submit it on a private events page, set the inquiry type to private events.
And so on.

Same form. Different downstream logic.

This is especially useful when the form fields are basically identical, but the business process after submission needs to change. The screenshot here is from a real setup where the workflow trigger is not just “submitted form,” but “submitted form on a page URL containing X.”

That tiny distinction matters.

Because now the form is reusable, reporting is cleaner, and your future admin is not opening 30 cloned forms trying to figure out which one is actually live.

The big idea is this:

Don’t use separate forms as a substitute for process logic.

Use the form to collect the information.
Use the page URL to understand the context.
Use the workflow to route, label, assign, or update the record.

Not glamorous. Very useful.

And if you ever invite me into your account to help, this is one less item I will Gordon-Ramsay-Yell at you about.

I am actually so passionate about this that a few weeks ago, I released a FREE spreadsheet template which will help you plan and implement this change.