The Multibrand feature in Support is configured by default to allow all agents to access tickets for all brands. This allows your support team to seamlessly move between requests from all of your brands and provide faster support. However, some teams might want to restrict the agents that are able to access tickets for specific brands.
This article describes how to effectively restrict agent access to tickets for specific brands by following the steps below:
- Step 1: Create groups
- Step 2: Limit agents to groups
- Step 3: Set up triggers
- Optional: Add group-limited views
Step 1: Create groups
After you've set up multiple brands, create groups. You may want to create just one group per brand or maybe many per brand, depending on how granular you want restrictions to be. For example:
- Simple: BrandA, BrandB, BrandC, etc
- Complex: Support_BrandA, Returns_BrandA, Support_BrandB, Returns_BrandB, Support_BrandC, Returns_BrandC, etc
When creating these groups, add the agents whose access to specific brands you want to restrict.
See Creating groups and Adding team members to groups.
Step 2: Limit agents to groups
Next, limit agent access to only tickets within their groups.
(Enterprise only) Custom roles can be set to restrict agents to only access tickets within their groups. Create or edit an existing custom role, then in the Tickets they can access section, select Within their groups. See Creating custom roles and Editing custom roles.
(Suite Growth and Professional) You can limit agent access to tickets in their groups from their profiles in Support. Learn more about setting up agent access restrictions.
Step 3: Set up triggers
You can now set up triggers to route new tickets to a group for the right brand. It might be beneficial to first route tickets to a triage group, which will then assign them to the appropriate group based on the type of request. See Creating triggers.
Set the condition of the trigger to be when a ticket is created for a certain brand:
Then the action assigns it to the correct group:
You can add any notification messages or other ticket updates as well.
Note that agents are able to edit the brand of tickets. Agents can still access tickets that they change the brand of as long as it is still assigned to their group.
To further restrict your agents' access to specific brands, you can set up a trigger that reassigns the ticket when the brand is changed. For example:
Optional: Add group-limited views
In addition to the group and trigger workflow, you can also restrict your views to a specific group. This way, you can have a view of BrandA's tickets and only allow a specific group of agents to see that view:
For more information, see Using views to sort branded tickets.
would this solution remove the brand dropdown menu on the left sidebar?
No it wont as this is workflow is designed to route tickets to an appropriate group but it would not totally restrict them from seeing the Brand drop down field as this is a system field.
This should be included in roles... So much cleaner :)
Or in the agent-profile. Even better !
Are there any ETA on this? It's really, really restricted since we have brands where some tickets must stay privates.
Why in the world are Brands available in Professional, but this feature is only available in Enterprise? If you are not going to allow us to assign agents to a Brand, why even give us the brand option?
This article would be greatly improved by implementing a specific example, such isolating agents who provide sales support from those who provide clinical support. As it is, instructions likes those in Step 1 are too vague to be useful. And in Step 3, where does one set the routing rules?
One way we could use it in our case is like this:
We have a tech support center in one brand. They should have acces to all tickets in this brand without exception.
The other brand is a transportation service for schools.This brands also has confidential requests for parents children so our other agents MUST not see tickets from their brands.
Please sign in to leave a comment.