The Multibrand feature in Zendesk Support is configured by default to allow all agents to access tickets for all brands. This enables 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 work on tickets for specific brands.
This article describes how to, effectively, restrict agent access to tickets for specific brands using custom agent role permissions (Enterprise plans) and business rules for routing tickets.
Step 1: Limit agents to groups
Your custom roles can be set to restrict agents to only access tickets within their groups. To do this, open the custom role for editing. Then, scroll down to the Tickets they can access section and select All with this agent's group(s).
Step 2: Set up all the necessary groups
You need to add groups, then add your agents to these groups. Possibly just one 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
Step 3: Create routing rules
You can now build triggers to route new tickets to a group for the right brand. It might be beneficial to first route tickets to a triage group, who will then assign them to the appropriate group based on the type of request.
Set the condition of the trigger to be when a ticket is created for a certain Brand:
Then the action will assign it to the correct group, and you can add any notification messages or other ticket updates as well:
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 for 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.