What a multi-brand help center is
A multi-brand help center is one setup behind several branded help sites: each brand gets its own domain, look, languages and assistant, and one team runs the content and support for all of them. Customers only ever see the brand they bought.
A week with one of your brands' customers
Take Harrow House, a small appliance group with three brands: Corvo espresso machines, Tillet blenders and Fenwick water filters. One support team covers all three, in the UK, France and Spain. Camille lives in Lyon and owns a Corvo machine.
Monday, 7:05 am: her machine, her language
Camille signs in to Corvo's help center with the account she made when she registered her machine. It opens in French, in Corvo's colors, and leads with the care guides and recent tips for her exact model. Nothing about blenders or filters.
7:20 am: the descale light, answered
The descale light starts flashing. She types her question in plain French. Corvo's assistant replies with the descaling steps for her model with a link to the guide it used so she can keep it open beside the machine.
Wednesday, 8:40 am: a weak shot, sorted before work
Her espresso comes out thin and fast. She searches "café trop liquide" and finds a short troubleshooting guide: grind finer, check the basket, tamp harder. Two changes later, her second cup is right, and she marks the article helpful.
Friday, 6:15 pm: a leak, and a person who knows her machine
Water is pooling under the machine, and no guide covers it. She sends Corvo a WhatsApp message from her phone, the app she uses all day anyway. The message reaches the Corvo queue with her model, purchase date and Shopify order already attached, so Luc on the support team asks for one photo and books a repair. Her help center account shows the request as open, then as scheduled.
Saturday: warranty, in Corvo's words
Camille checks her warranty. The page reads like Corvo, in French, though the same answer also sits on Tillet's and Fenwick's sites in their own voices.
The next week: the team behind all three brands
The support lead looks at the searches by brand. Corvo owners in France keep asking how to clean the milk wand, and no page answers it. She writes one, gets the French version reviewed, and it's live on Corvo's help center that week.
What your brands' customers can do
See only what fits them
Each customer lands in the help center of the brand they bought, on that brand's domain and in their language. Signed in, they see guides for their own products first, and never another brand's.
Get answers on their own
Customers search or ask the brand's assistant in their own words. Answers come from that brand's approved content, with a link to the source, in the customer's language.
Sort out common problems without waiting
Care guides and troubleshooting steps are written for each product, and customers rate what they read. Most small problems end at home, with no ticket and no queue.
Talk to someone on a channel they already use
For anything a guide can't fix, customers reach you by web chat, email, WhatsApp, Messenger or Instagram. The request goes to that brand's queue carrying their product and order, so they explain it once.
Know where their request stands
Signed-in customers see each request and whether it's open, waiting on them or resolved.
What your support and content teams get
Requests from every brand arrive in one shared inbox, with a queue for each brand. They claim a conversation, pass it on with a private note, and answer on whichever channel the customer chose. Writers keep every brand's content in one place: an article can belong to one brand or be shared by several, and each shared answer shows up in every brand's own design. Analytics split by brand show what customers search for, what goes unanswered and which articles get low ratings.
What running every brand this way changes
Every brand keeps its own face, and you keep one operation. Separate domains, looks and languages sit on shared content and one inbox, so adding a brand doesn't mean adding a tool.
A policy change reaches every brand at once. Shared answers like warranty and delivery are written once and appear on each brand's site in that brand's voice.
Customers never get another brand's answer. Each assistant answers only from its own brand's content, so a question about a Fenwick jug never gets an espresso reply.
Requests arrive ready to solve. Brand, product and order travel with every request, which means the first answer can fix things rather than collect details.
You see which brand's customers are stuck. Searches and unanswered questions by brand tell you exactly which page to write, and you can have it live that week.
Your team and each brand's assistant
Every brand has its own assistant, answering from that brand's content and citing it, so Corvo answers never borrow from Tillet. When a customer needs a repair, a refund decision or simply a person, the assistant hands the chat to that brand's queue with the conversation and order attached. It acts only within the permissions you set for each brand, and each action is logged.
How to set up help centers for several brands
- Bring in your content. Connect existing articles from Zendesk or Freshdesk and manuals from SharePoint or Google Drive, then label each by brand and product.
- Decide what's shared. Mark which answers apply to every brand, like warranty and delivery, and which belong to one.
- Create a help center per brand. Give each its own domain, branding, navigation and languages, with translations reviewed by a person before they go live.
- Let customers sign in. Link accounts to registered products or orders so each customer sees their own products and requests first.
- Add an assistant per brand. Point each at its brand's content and choose which questions go to a person, and to which queue.
- Open the channels. Create a queue per brand, connect web chat, email and WhatsApp, and bring in order details from Shopify.
Connections for a multi-brand support operation
Zendesk and Freshdesk to bring existing help content across, SharePoint and Google Drive for manuals, Shopify for order details on each request, and web chat, email, WhatsApp, Messenger and Instagram as channels into one inbox. Webhooks and an API cover the rest, among 30-plus sources.
Related
- Running one help center across multiple products
- Multilingual AI support, brand by brand
- AI agent for product support when your catalog runs to hundreds of models
- Help centers on MatrixFlows
- Best help desk software
| Multi-brand help center on MatrixFlows | A separate help center per brand | |
|---|---|---|
| What customers see | Their brand's site, in their language, with their products first | A separate site per brand, each built and kept up on its own |
| Shared answers | Written once, shown on every brand's site in its own voice | The same answer copied into each site, drifting apart |
| AI answers | An assistant per brand, answering only from that brand's content | One bot per site, or a single bot that mixes brands up |
| Getting help | Web chat, email, WhatsApp, Messenger or Instagram, with order attached | A contact form per site, then questions about the order |
| Request status | Visible in the customer's account | A reference number and an email to chase |
| Support team | One inbox with a queue for each brand | A login per brand and a lot of switching |
| Spotting gaps | Searches, unanswered questions and ratings compared by brand | Separate reports stitched together by hand |
Every brand you run is part of your customer operations, and on MatrixFlows they share one platform. That same platform runs your partner programs and your employee help too.