An owner runs three brands from one WordPress multisite. The products differ, the prices differ and two of them compete with each other in the same category.
He installs one widget across the network with one set of answers. A visitor on the premium brand asks about pricing and is quoted the budget brand's figures.
Nothing was configured incorrectly. It was configured as one business, and three brands existing on one installation is a technical arrangement rather than a commercial one.
1. Decide what is genuinely shared
Group policies, privacy handling, escalation rules and the complaints route. These are usually common and maintaining them once is a real saving.
2. Decide what must be separate
Prices, products, availability, opening hours, contact routes and tone of voice. Blending any of these produces answers that are confidently wrong.
3. Configure per site, deploy through the network
The installation mechanism can be network wide while the configuration remains per site. Conflating the two is the most common mistake in this setup.
4. Keep the brands apart in the answers
An assistant on one brand should not volunteer information about another, particularly where they compete. This is a positioning decision rather than a technical one.
5. Decide how cross brand questions are handled
Where a visitor genuinely needs another brand in the group, a clean referral is better than either silence or an attempt to answer from the wrong knowledge.
6. Keep the escalation routes separate
Each brand's enquiries should reach the people who handle that brand. A shared inbox across three brands recreates the routing problem the sites were meant to avoid.
7. Match the tone to each brand
A premium brand and a budget brand should not sound identical. Tone is part of what the customer bought and it is easy to lose in a shared configuration.
8. Handle the shared customer carefully
Somebody who has bought from two brands in the group should not be surprised by what one knows about the other, which is a privacy consideration as much as a commercial one.
9. Keep the reporting separate
Per brand, so that each can be judged on its own. A rolled up figure hides the brand that is failing behind the one that is working.
10. Plan the maintenance as one job
Shared elements updated once, brand specific elements per site, on a schedule. Without this, one brand's answers quietly fall behind, which is the discipline in running assistants for several brands.
11. Watch the caching across the network
Multisite installations frequently cache at several layers and changes can appear on one site and not another, which is the ground in caching questions that confuse everybody.
12. Watch for plugin conflicts that differ per site
Different themes and different active plugins per site mean a widget that works on two may misbehave on the third, which is the diagnosis process in plugin conflict questions wordpress owners ask.
13. Document each site's configuration
What is where, who owns it and when it was last reviewed. Three configurations held in one person's memory is a problem waiting for a holiday.
14. Set the first one up properly and repeat it
Getting one site right and cloning the structure is faster than configuring three differently, which is the approach in onboarding a saas assistant in one afternoon. See the integrations, features, start at try, and the sector view sits under small business.