Customer Agent Now Supports Multiple Brands in One Portal

What This Update Actually Is

HubSpot shipped Multi-Brand Support for Customer Agent. Before this update, every portal was limited to one Customer Agent. That single agent handled every brand under your umbrella, which created real problems for companies running two or more distinct brands.

Now you can create one dedicated agent per brand. Each agent carries its own identity, personality, knowledge base, behavioral rules, routing logic, and reporting footprint. They don't share information. They don't bleed into each other's conversations.

One important caveat: this feature requires the Brands Add-on. It's not bundled into any hub tier by default. If you're running Service Hub Pro or Enterprise without the add-on, you'll need to add it before this functionality is available to you.

Why HubSpot Shipped This

We've seen this pattern repeatedly in multi-brand portals: a holding company manages three consumer brands, they deploy one Customer Agent, and within weeks they're troubleshooting why Brand A's knowledge is surfacing in Brand C's chat window. It's not a configuration error. It was a product gap.

HubSpot's own release notes name three failure modes that multi-brand organizations hit with a single-agent setup:

• Tone leakage: the wrong brand voice shows up in conversations
• Knowledge leakage: information from one brand surfaces for another brand's visitors
• Context leakage: the agent confuses audiences, products, or brand contexts mid-conversation

The internal frustration for the humans managing these portals is real. They were either building expensive workarounds or accepting lower-quality AI experiences for at least one of their brands. This update closes that gap directly.

How to Use It Step by Step

Here's the practical path from zero to a fully isolated multi-brand setup:

1. Confirm your Brands Add-on is active. Without it, the multi-agent controls won't appear. Contact your HubSpot rep or check Settings > Account > Billing if you're unsure.
2. Navigate to Customer Agent in your Service Hub settings. You'll now see an option to create a new agent rather than editing the single existing one.
3. Name and configure each agent per brand. Set a distinct identity, personality, and tone for each one. These are separate entities, so treat them that way from the start.
4. Train each agent on brand-specific knowledge. Upload the right knowledge sources for each brand only. Don't cross-pollinate. Isolated knowledge bases are what make complete brand separation possible.
5. Assign channel deployments carefully. The new controls show exactly which agent is live on which channel. Built-in safeguards prevent you from accidentally deploying two agents to the same channel.
6. Validate routing logic for each brand. Make sure visitors land in the right agent's conversation flow before you go live. Test with internal users before pushing to real visitors.

What It Touches in Your HubSpot Strategy

This update ripples further than just the chat widget. Here's where it shows up across your portal:

• Help Desk views now display each agent as a distinct entity, so your support team knows which brand's agent handled a conversation without digging through records
• Reporting dashboards segment performance by agent, so you can measure deflection rates, satisfaction scores, and volume per brand independently
• Workflow builder recognizes each agent as a separate trigger source, giving you brand-specific automation paths without a tangled single-agent workaround
• Channel assignments are tracked at the agent level, which means your ops humans can audit exactly what's deployed where without guessing

If your team has already been tracking how Customer Agent handles volume and routing, this update pairs naturally with the conversation volume estimation feature HubSpot released earlier this year. Run volume estimates per brand agent before you go live so you're not surprised by load.

Also worth noting: if you've recently dealt with HubSpot's routing changes, understanding the legacy channel routing sunset will help you configure per-brand channel assignments cleanly from the start instead of inheriting old routing conflicts.

Who Should Care Most

Not every HubSpot portal needs this update. Here's who does:

• Holding companies and parent organizations managing two or more consumer or B2B brands from one HubSpot portal
• Franchise networks that need a central portal but distinct brand voices for each franchise group
• Service Hub admins and RevOps leads who've been fighting tone or knowledge bleed in existing agent configurations
• Customer experience teams at mid-market and enterprise companies where brand integrity in support conversations is non-negotiable
• Marketing ops humans who want clean, brand-segmented reporting without building manual workarounds in the report builder

If you're a single-brand company on Service Hub Pro or Enterprise, you don't need this right now. But if you're planning brand expansion or an acquisition, understanding how this scales is worth your time. George actually wrote about his own experience deploying Customer Agent moving from a third-party clone to HubSpot's native agent, which gives you useful context on what it takes to configure an agent well before you multiply that effort across brands.

George's Take

I've worked inside enough multi-brand portals to know that the single-agent limitation wasn't a minor inconvenience. It was a trust problem. When the humans visiting your Brand B website get an answer that clearly belongs to Brand A, they don't think 'oh, the AI made a mistake.' They think 'this company doesn't know what it's doing.' Multi-brand support for Customer Agent fixes that at the architecture level, not with a patch. If you're running more than one brand in HubSpot, this is the update to prioritize in your Q2 portal review.

If you're ready to configure multi-brand Customer Agent the right way or you're not sure whether your current setup is ready for it, let's talk. Book a strategy call with the Sidekick team and we'll audit your portal, map out the right agent structure for your brands, and get you live without the guesswork.

Frequently Asked Questions

What is Multi-Brand Support in HubSpot Customer Agent?

Multi-Brand Support lets organizations create a separate Customer Agent for each brand inside a single HubSpot portal. Each agent has its own identity, brand voice, knowledge base, routing logic, and reporting data. Brands don't share information, which eliminates tone leakage, knowledge leakage, and context confusion between agents.

Do I need a special add-on to use Customer Agent multi-brand support?

Yes. You need the HubSpot Brands Add-on to access this feature. It's not included in any hub tier by default. Without the add-on, the multi-agent controls won't appear in your portal. Contact your HubSpot account rep or check your billing settings to confirm whether you have it.

Which HubSpot hubs and tiers support multi-brand Customer Agent?

The feature is available across Content Hub, Marketing Hub, Data Hub, Sales Hub, and Service Hub at both Professional and Enterprise tiers. You also need the Brands Add-on active on your account. The expected release date is May 21, 2026.

Will one brand's knowledge base bleed into another brand's Customer Agent?

No. Complete brand isolation is the core feature of this update. Each agent's knowledge base is fully separated. Information from one brand won't surface in another brand's conversations. Tone, behavior, and context are also isolated per agent, so there's no cross-brand contamination.

Can I accidentally deploy two brand agents to the same chat channel?

HubSpot built in safeguards to prevent exactly that. The channel deployment controls show which agent is active on each channel, and the system blocks you from assigning multiple agents to the same channel. Routing is predictable, and visitors always reach the correct brand's agent.

How does multi-brand Customer Agent appear in HubSpot reporting?

Each agent shows up as a distinct entity across Help Desk views, reporting dashboards, the workflow builder, and channel assignments. You can track deflection rates, conversation volume, and performance metrics per brand agent without combining data or building manual workarounds in the report builder.