Zendesk multi-brand setup: several brands, business units or portals on one instance

The problem: one brand too many, or one too few

Multi-brand problems come in two shapes. The first is one legacy brand carrying several teams or product lines, so every request lands in the same place and someone sorts it by hand. The second is a separate Zendesk instance or brand per customer, acquired company or portal, so administration is duplicated, reporting is fragmented and nobody can compare performance. Both end with agents reassigning tickets and leaders without a clean number.

Zendesk brands, brand spaces, organizations and the messaging API give you the pieces. The design decision is where the boundary goes: a brand per business unit, a brand space for a department that must stay private, or one brand with routing by organization. We make that decision with you before configuring anything.

How we approach a Zendesk multi-brand setup

A brand per business unit, one instance for the company

For a hardware maker with two business units, each needing its own support experience across multiple sites, we set up a brand for each unit with its own ticket intake and routing, a branded help center on its own support domain, and a shared publishing standard so both follow the same Zendesk controls. One instance with two brands keeps one set of reporting and administration, which the client expects to cut administration effort by about 35 percent compared with two instances.

Brand spaces for a department that must stay separate

When HR needs its own space inside a shared help desk, Zendesk brand spaces give it one. For a fresh-meal company we set HR up as its own brand so HR requests stayed with HR, with notifications under the right brand, while technical support kept the shared desk. We chose this over a separate instance to keep one admin surface and one set of reports, and the whole implementation went from redesigned forms to a live multi-brand help desk in about two weeks.

Splitting a legacy brand into two

For a software company running two internal service teams through one legacy brand, we rebuilt the instance as a multi-brand setup, routed requests by brand and then by request type, pointed inbound email from both company domains at the matching brand, and retired the legacy brand in stages so no open request was lost. Brand-first routing is expected to cut manual reassignment by about 35 percent.

Consolidating instances into one, without losing the brand

A banking infrastructure provider ran separate Zendesk setups with brands per customer platform. We replaced that with one consolidated instance, routing by customer organization through the Zendesk messaging API, with co-branded sender addresses preserved so end users still see the sender they recognize. A custom web widget takes each portal's styling and passes customer, organization and brand context into the ticket when it loads. The pattern is documented so it repeats on further portals.

Brand-based routing that scales

For an outsourcer supporting many retail brands, we chose one routing variable that identifies the brand, so routing works across channels without a queue for every brand and channel combination. The help center is organized by brand, and the escalation process is shared.

What to check in your own setup

• How many brands, instances and help centers you run today, and who administers each.
• Which audiences must never see each other's content, and which merely need their own look.
• Whether email domains and sender addresses map cleanly to the brands you want.
• Whether routing could key off one variable, such as brand or organization, rather than a queue per combination.
• What reports leadership wants across all brands, because that argues for one instance.

Buy Zendesk through ShadowRock

ShadowRock is an authorized Zendesk reseller and a Zendesk Premier Implementation Partner. Companies consolidating or splitting brands can buy Zendesk Suite from us with licensing and the multi-brand implementation in one contract, and we will tell you which plan the number of brands you need requires. Verify our Zendesk partner status on the Zendesk Marketplace.