Business rules for multiple brands

Rules written before your second brand existed apply to both. Reviewing them is the real work in a multibrand setup.

Rules written before your second brand existed apply to both. Reviewing them is the real work in a multibrand setup.

Add brand to your conditions

1. Open the trigger, automation or view.
2. Add a condition on Brand.
3. Save and test with a ticket from each brand.

Brand is available as a condition everywhere, which makes the mechanics easy. Knowing which rules need it is the harder part.

Which rules need reviewing

Work through these in order, because they are the ones that show.

• Anything that sends a message. Notifications carrying your company name reach the wrong customers under the wrong name.
• Routing rules. A trigger assigning everything to one group sends the new brand's tickets there too.
• Service level agreements. Two brands rarely have identical promises.
• Views. Agents working one brand want their queue, not everything.
• Macros. The wording usually names a brand somewhere.

Use placeholders instead of names

The better long-term answer for messages. A placeholder for the brand name means one trigger serves every brand and keeps working when you add a third. Hard-coding the name means a rule per brand and a set of near-duplicates that drift apart.

Test from each brand

Send a genuine ticket to each brand's address and follow it through. What routes, what the customer receives, and which name is on it. That is fifteen minutes and it catches what reading conditions does not.

See also

• What placeholders are
• Using views to separate brands
• Email addresses per brand