Give each brand a support center
Set up a support center with a distinct URL and presentation for each brand or product. Customers can reach the service experience associated with the product they know.
Keep the customer in the right brand.
Publish the answers that belong there
Organize knowledge for the audience each brand serves. Keep product instructions and policies relevant to that support center, with an editorial owner responsible for maintaining them.
Reply with the right identity
Configure outgoing email settings for each brand. Review addresses and notification templates so a customer can recognize which brand is responding throughout the conversation.
“We really like how easy it is to have multiple brands and separate email categories with their own emails and email signatures.”
Make brand separation part of the workflow.
Associate categories with brands
Link the relevant ticket categories to each brand. Give incoming requests the operational structure agents need for ownership, handling, and reporting within the shared account.
Control who handles which requests
Configure category access and role permissions around agent responsibilities. Shared administration should be accompanied by deliberate access decisions for teams supporting different audiences.
Use the appropriate service process
Apply rules and service targets using the relevant ticket conditions. A brand with different operating hours or handling needs can be reflected in the account’s configuration.
Plan the details before adding a brand.
Map the support experience
Identify the support-center URL, visual identity, knowledge sections, request fields, and outbound email identity each brand needs. Review the journey from asking a question to receiving a reply.
Decide category boundaries
Choose how categories connect requests to brands and service teams. Check that the intended customer content and agent access follow those associations.
Assign content ownership
Name the people responsible for brand-specific articles and form copy. Plan how common guidance will be maintained when it applies to more than one audience.
Review custom domains
Confirm domain mapping and SSL requirements for each branded support center. Include those steps in the rollout plan alongside email configuration.
Check plan and brand limits
Confirm multi-brand availability and the number of brands permitted in the current plan. Review the commercial terms against the portfolio you need to support.
Plan an existing-account transition
Existing HappyFox accounts cannot be merged into one multi-brand account. Discuss the data and configuration work involved if brands currently run in separate accounts.
Questions before choosing your setup.
What is a multi-brand help desk?
A multi-brand help desk runs distinct customer support experiences inside one account. In HappyFox, each brand can have a support center, knowledge base, new-ticket form, and outgoing email settings, while agents manage the resulting tickets in the shared help desk.
How is it different from creating ticket categories?
Categories organize tickets and team responsibilities. Multi-brand configuration associates categories with a customer-facing support experience. Use both together when different products or audiences need distinct places to get help.
Can each brand have its own knowledge base?
Yes. Configure the knowledge content that belongs in each brand’s support center. Plan which articles are specific to that audience and which guidance needs a coordinated maintenance process.
Can brands use different outgoing email settings?
Yes. Each brand has outgoing email configuration. Confirm the sending channel, domain requirements, and notification content so replies and updates reflect the appropriate brand identity.
Can we restrict agents to particular brand work?
Configure category access and role permissions around the tickets agents should handle. Test the resulting access with representative agents; a branded support center alone is not a substitute for permission configuration.
Can existing HappyFox accounts be merged?
No. HappyFox’s multi-brand setup documentation states that existing accounts cannot be merged into a single multi-brand account. Discuss your transition requirements before deciding how to move separate brand operations.
Can a brand use a custom domain?
HappyFox supports custom domains for branded support centers. SSL requires separate setup for a custom domain. Confirm domain ownership, configuration, and certificate requirements during implementation.
Which plan includes multi-brand support?
Check the current plan and brand limits with HappyFox. Plan names and entitlements can change, so confirm availability for the number of brands and the account configuration you intend to use.
What should we review in a multi-brand demo?
Choose two brands with different support needs. Walk through each customer’s support center, form, knowledge, and email experience, then review agent access and ticket handling in the shared account.