What This Update Actually Is
Support Macros are a new reply-driven automation tool inside HubSpot Help Desk. A macro combines a message with one or more follow-up actions into a single, saveable button.
When a rep clicks "send and apply," the message goes out AND the ticket gets updated. No second screen. No manual property edit. No separate workflow trigger to chase down.
Each macro has two parts: an optional message (typed text, a snippet, or a template) and a set of actions. Actions can update the ticket owner, name, description, category, priority, status, or any editable custom ticket property. You can also enroll the ticket in an active, ticket-based workflow for more complex logic.
One important constraint: macros live in Help Desk only. They aren't available in the Inbox or from the CRM record view.
Why HubSpot Shipped This
Ticket volume is up. Customer expectations are up. The headcount to handle both is usually not.
We've seen this pattern across dozens of portals: a rep types a reply, sends it, then clicks over to the ticket properties panel to change the status to "Waiting on customer," then reassigns the owner, then maybe opens a separate workflow to trigger a follow-up. Each step is small. Together they eat minutes per ticket, multiplied by every ticket in the queue.
The internal frustration isn't laziness. It's that the tool required too many clicks for work that is genuinely repetitive and predictable. Macros collapse that repetitive sequence into one saved action.
This also fits the broader direction HubSpot is taking with its agentic platform. If you want the bigger picture on where AI-assisted service is heading, the HubSpot Agentic Platform pillar gives you the full context.
How to Use It Step by Step
Here's how to build and apply your first macro. You'll need "create/edit macro" permission under Service settings.
- Go to Settings, then Help Desk and Inbox, then Help Desk, then Macros.
- Click "create macro" and give it a name and an internal description.
- Add a message if needed. You can type directly, or insert a snippet or template. Important caveat: snippets and templates in macros are static. If you update the original snippet later, the macro won't reflect that change. Plan accordingly.
- Add one or more actions. Use the built-in dropdown to update owner, name, description, category, priority, or status. For any other editable ticket property (non-system, no field-level permissions), you can update that too. For advanced logic, enroll the ticket in an active ticket-based workflow.
- Set sharing. Share with everyone on the team, or limit access to specific users and teams. You can manage sharing in bulk from the macros list page. Note: changing access overwrites the previous setting rather than adding to it.
- Save as a draft or publish. Drafts count against your portal limit (500 for Pro, 1,500 for Enterprise), so don't let old drafts pile up.
- To apply a macro, open a ticket in Help Desk, click "macros" next to the send button in the reply editor, search or browse, select the macro you want, review the message and listed actions, then click "send and apply."
- Changed your mind before sending? Hover over the action or workflow name at the bottom of the reply editor and click the X to remove it before you send.
What It Touches in Your HubSpot Strategy
This update lives in Service Hub, but its ripple effects touch several layers of your stack.
Ticket properties and data hygiene get better automatically. Because macros enforce consistent property updates at reply time, your ticket data becomes more uniform without relying on reps to remember to update fields. That cleaner data makes your support reports more trustworthy.
Key Takeaway
Macros aren't just a speed tool. They're a data quality tool. Every rep applying the same macro updates the same properties the same way, every time.
Workflows get a new entry point. If you connect a macro to an active ticket-based workflow, you can trigger escalations, internal notifications, or multi-step sequences without the rep needing to know any of that is happening. The macro is the front door; the workflow is the engine behind it.
That workflow connection becomes especially powerful when you pair it with HubSpot's ability to use records created mid-workflow later in the same flow. You can create follow-up tasks or linked records inside the workflow a macro triggers, then act on those records downstream without splitting into a second automation.
Snippets and templates: the static nature of macro messages is a real operational consideration. If your team maintains a library of frequently updated snippets, you'll want to decide whether macros should use stable, rarely-changed message text instead. Build a review cycle into your macro management so stale messages don't go out to customers.
Permissions and governance: "create/edit macro" is a new permission under Service. Admins should audit who gets it. Not every rep should be building macros. Limit creation to leads or ops, and give broader apply-only access to the rest of the team.
Key Takeaway
Start with your three highest-volume ticket scenarios. Build a macro for each. Measure handle time before and after. That's the business case for your next Service Hub seat conversation.
If your team is also exploring how HubSpot's AI-powered Customer Agent can handle the first response layer, check out how Customer Agent now responds to form submissions automatically. Macros and Customer Agent can work as two layers of the same support motion: AI handles the first touch, humans handle the complex replies with macros keeping them fast.
Who Should Care Most
Macros are purpose-built for a specific profile. Here's who gets the most value.
- Service Hub Pro and Enterprise customers with active Help Desk usage: this is the core audience. If your team is already living in Help Desk and managing real ticket volume, macros are an immediate upgrade.
- Support team leads and ops managers: you're the humans who should design and govern the macro library. This is a process-definition job as much as a technical one.
- RevOps professionals who own the HubSpot instance: macros introduce a new governance surface. Permissions, sharing settings, draft limits, and static snippet risks all need to be documented in your portal's operating model.
- Growing B2B companies with small support teams: when two or three humans are handling a ticket queue that would justify five, macros help close that gap without adding headcount.
If you're on Service Starter or Free, this one isn't for you yet. Macros require a seated Service Hub Pro or Enterprise license.
George's Take
“The best support tool isn't the one with the most features. It's the one that lets your humans spend more time actually solving problems and less time clicking through fields that should have already been updated.”
When I look at macros, I don't just see a speed feature. I see a signal about where HubSpot is pushing the Help Desk product. They're building a layer where the rep's action is always the trigger, and the system handles the bookkeeping. That's the right direction. The humans on your support team should be spending their cognitive energy on the customer's problem, not on remembering to flip a status dropdown. The teams I've watched adopt this kind of reply-driven automation consistently see handle time drop and data quality climb at the same time. Those two things usually move in opposite directions, which is what makes this worth paying attention to.
Want to make sure your Help Desk setup is actually built to take advantage of updates like this? Let's look at your portal together. Book a strategy call with the Sidekick team and we'll show you exactly where macros fit into your current support workflow and what to build first.
Frequently Asked Questions
What are HubSpot Support Macros?
HubSpot Support Macros are saved combinations of a reply message and ticket actions that a rep can apply in one click from Help Desk. A single macro can send a message and update ticket status, owner, priority, category, or any editable custom property at the same time. They're available to Service Hub Pro and Enterprise seated users only.
Where can I find and manage macros in HubSpot?
Go to Settings, then Help Desk and Inbox, then Help Desk, then Macros. From that page you can create, edit, publish, and manage sharing for all macros in your portal. You need the "create/edit macro" permission under Service settings to build or modify them.
Can macros trigger workflows in HubSpot?
Yes. When building a macro, you can choose to enroll the ticket in an active, ticket-based workflow as one of the macro's actions. This lets you connect a simple one-click rep action to complex multi-step automation. Only active ticket-based workflows are compatible with macros.
Do snippets and templates inside macros update automatically?
No. Snippets and templates added to macros are static at the time of creation. If you update the original snippet or template later, that change won't carry over to any macro using it. You'll need to manually edit each macro to update its message content.
How many macros can a HubSpot portal create?
Service Hub Professional portals can create up to 500 macros. Service Hub Enterprise portals can create up to 1,500 macros. Draft macros count toward this limit, so archive or delete unused drafts to keep your count clean and your library manageable.
Are HubSpot Support Macros available in the Inbox or on CRM records?
No. Macros are only available inside Help Desk. They can't be used from the Conversations Inbox or from a ticket record in the CRM. This is a current limitation to be aware of if your team uses both Help Desk and the legacy Inbox for ticket handling.
