In a Multibrand setup, all agents have access to all brands by default. However, you can create brand views for agents to use. If you need to restrict access, you can use triggers to assign brand tickets to specific groups and restrict agent permissions to those groups. This setup allows for more controlled access and management of brand-specific tickets.
Before migrating from Hub and Spoke to Multibrand in Zendesk, ensure you're actually using all your spokes. If your spokes aren't being used or aren't sharing tickets with the hub, a migration might not be necessary. Additionally, remember that a…
Migrating from Hub and Spoke to Multibrand in Zendesk involves several behavior changes. For instance, all agents will have access to all brands by default, and you can create brand views for agents. Additionally, there's only one signature per…
The migration to Multibrand in Zendesk involves several steps, including configuring your Multibrand instance, verifying sample content migration, and preparing for downtime. The timeline depends on Zendesk resources, migration complexity, and your…
Migrating to Multibrand in Zendesk comes with several limitations. For instance, ticket events and IDs cannot be migrated, and Help Center content like article creation dates and comments are not available post-migration. User information such as…
Yes, you can migrate your Help Center community content when moving to Multibrand using the Help Center API. However, note that some settings and content, like article creation dates and comments, won't be available post-migration. It's important…
During the migration to Multibrand, you can restrict access to specific ticket forms by brand. This allows you to control which ticket forms are available to end-users and agents based on the brand of the Help Center or ticket they're viewing. This…