# How to Run Support for Several Brands From One Help Desk

[Ben Puzzuoli](https://www.cayzu.com/blog/author/ben/) Updated October 27, 2026 First published October 26, 2026 6 min read

For most companies with two or more brands, one help desk is the better setup. Each brand keeps its own portal, address and help articles, and your team answers all of it from one queue with one login.

Separate help desks still make sense when each brand has its own team, nobody works across both, and the teams shouldn't see each other's tickets.

A [multi-brand help desk](https://www.cayzu.com/multiple-product-brand-helpdesk/) is one account that runs a separate support site for each brand or product. A customer of brand A sees brand A's logo, domain and articles, and never sees brand B. On your side, every ticket from every brand lands in the same list, marked with the brand it came in through. The same setup works as a multi-product help desk for a software company with several apps.

## One help desk or one per brand?

Start with who answers the tickets. If the same people handle both brands, two help desks cost you a little every day. Two logins. Two queues, and one of them gets checked less. Two sets of numbers to add up at the end of the month.

Price cuts both ways. Help desks charge per agent, so anyone who works both brands is a seat in each account. That's the only person the comparison is about. Someone who works one brand is one seat either way.

For an agent who works both, here's the math in Cayzu. All prices here are per agent per month, billed yearly. Multi-brand is on Enterprise at $65. Two Pro accounts would be $39 twice, or $78. Two Standard accounts would be $19 twice, or $38, which is less than Enterprise. But Standard has no response time targets (SLAs), so neither brand gets them. If that's fine for your brands, two small desks can cost less. You pay for it in the daily switching.

One help desk is the right call when:

- The same people answer for more than one brand.
- You want one set of numbers, with the option to look at each brand alone.
- Customers sometimes write to the wrong brand, and you'd rather move the ticket than forward an email.

Separate help desks are the right call when:

- Each brand has its own team and nobody crosses over.
- The brands have different owners, or one might be sold. We'd keep that one apart, because a brand that already runs on its own is easier to hand over.
- A brand has its own small team and can live without response targets. Standard at $19 per agent, billed yearly, may cost less than putting everyone on Enterprise.

[An agency supporting client brands](https://www.cayzu.com/help-desk-software-for-call-centers/) usually lands in the first list. If your agents work every client, one help desk with a portal per client is the simple answer. If one client's tickets have to be hidden from part of your team, that's still one help desk, with access settings doing the hiding.

## What has to be different for each brand

A customer of one brand should never see the other. So anything a customer touches carries the right brand:

- Its own portal, with its own logo, colors and domain, like help.yourbrand.com. [Custom branding](https://www.cayzu.com/custom-branding/) covers what you can change.
- Its own support address. Each brand's support@ address comes in as its own mailbox, and replies go out from the address the customer wrote to.
- Its own signature. Signatures are set per [mailbox](https://www.cayzu.com/manage-multiple-mailboxes-and-emails/), so each brand signs off in its own name, with the agent's name added on top.
- Its own help articles. Each brand has a knowledge base inside its portal, so product A's setup guide never turns up in product B's search.
- Its own ticket forms, if the brands need to ask different questions.

Two more things often differ, and they need a bit more thought.

Response times. If one brand promises faster answers, give it [its own SLA policy](https://www.cayzu.com/help-desk-sla/). Each policy has conditions, a bit like a rule, and a ticket gets the policy whose conditions it matches. Set a policy's brand condition to that brand, and its tickets get the faster targets while the other brands keep theirs. Brand conditions need multi-brand, so they're on Enterprise.

Saved replies. Canned responses are shared across all your brands, and you can't limit one to a single brand. So we'd start the name of any reply that fits only one brand with that brand, like "Brand A: refund policy." It keeps the wrong brand's answer from going out.

## What your team should share

Everything the customer doesn't see can be shared, and usually should be.

The agents. One account, one login per person, whatever brands they work.

The queue. Every ticket sits in one list with a brand column, so nothing waits in an inbox nobody opened.

The reports. Reports and exports filter by brand, so the same screen gives you the whole desk or one brand's month.

The answers that are the same everywhere. Asking for a screenshot doesn't change by brand. One saved reply covers both.

## One shared queue or a queue per brand?

Start with one shared queue, and split it only when the brands need different knowledge. Then an [assignment rule](https://www.cayzu.com/automation-through-assignment-rules/) with brand as its condition sends each brand's tickets to its own group as they arrive.

Groups sort the work, but on their own they don't lock anything. By default, every agent can open every brand's tickets. If a group must not see the other brand, the ticket access scope setting can limit an agent to their own groups' tickets, so a contractor on brand B never opens a brand A ticket. [Custom roles](https://www.cayzu.com/helpdesk-customizations/customizable-agent-roles/) can do the same, and they also set what each agent can do with a ticket.

## How to set it up

The steps, in the order that saves going back:

1. Open the Brands screen in settings and click Add Brand. Give it its name, logo and colors. The Brands screen lists every brand with its incoming domain and how many mailboxes it has, so you can check your work there later.
2. Forward the brand's support address to its own mailbox, and write that mailbox's signature in the brand's name.
3. Put the portal on the brand's own domain with one DNS record. On Enterprise, each brand can have its own domain. Until you do this, the portal sits on a Cayzu address.
4. Add the brand's articles before you announce the portal. Start with the few questions that brand gets most, so the first customer who searches finds something.
5. Test it like a customer. Email each support address from a personal account, open each portal on your phone, and check that the reply comes from the right address with the right signature.

Don't skip the last step. It's the one that catches a form or signature attached to the wrong brand, before a customer does.

## What to check in any multi-brand help desk

If you're comparing tools, ask these:

- Which plan has multi-brand, and what does it cost per agent?
- Does each brand get its own portal, domain, reply address and signature?
- Does each brand get its own knowledge base and its own response times?
- Can rules route by brand, and can reports filter by brand?
- Can you limit which agents see which brand?

We'd ask the last one first. It decides whether an agency, or a company with a separate team per brand, can share one desk at all. For Cayzu, most of the answers are on the [multi-brand page](https://www.cayzu.com/multiple-product-brand-helpdesk/), and the plan details are on [pricing](https://www.cayzu.com/pricing/).

## The limits to know before you choose

- Multi-brand is on Enterprise only, at $79 per agent per month, or $65 per agent per month billed yearly. Standard and Pro run one brand.
- Each brand has one knowledge base, not several.
- Every agent sees every brand unless the ticket access scope setting or a role limits them.
- Rules run when a ticket is created. If you move a ticket that came in on the wrong brand, the rules don't run again, so assign it by hand.
- An email sent to two brands' addresses at once makes two tickets, one per mailbox. A merge fixes it.

And for every brand, support comes in by email and the portal. Cayzu has no built-in chat or phone.

If you're running two brands out of two inboxes today, the trial is a quick way to see whether one help desk fits. It includes multi-brand, so you can set up the second brand before you choose a plan. The first 15 days of Cayzu are [free with every feature](https://www.cayzu.com/sign-up/), and no card is needed.

More on Help desk basics

Help desk basics

### [Canadian Data Residency for Your Help Desk: What It Means and What to Ask](https://www.cayzu.com/canadian-data-residency/)

Canadian data residency means your help desk data is stored in Canada. It doesn't decide whose law can reach that data. What Canadian privacy law asks, five questions to put to any help desk, and our own answers.

Ben Puzzuoli October 27, 2026 7 min read

Help desk basics

### [What Is a Help Desk SLA? How Business Hours Change the Clock](https://www.cayzu.com/help-desk-sla/)

A help desk SLA is a target for first reply and resolution, set per priority and measured on a clock. Here's how to set the targets, and why the clock you pick decides whether your report tells the truth.

Ben Puzzuoli October 26, 2026 7 min read

Help desk basics

### [What's the Difference Between Help Desk and Customer Service Software?](https://www.cayzu.com/whats-the-difference-between-help-desk-and-customer-service-software/)

Vendors use help desk, customer service software, service desk and CRM as if they meant the same thing. They don't. Here's what each one is and which one you need.

Ben Puzzuoli February 18, 2022 4 min read

Running a help desk?

Cayzu is the simple, affordable one. Every feature free for 15 days.

[Get started for free](https://www.cayzu.com/sign-up/) [Watch a demo](https://www.cayzu.com/demo/)

---

The web page: https://www.cayzu.com/multi-brand-help-desk/
