Once a ticket is reassigned to a group outside a restricted agent's access, they can no longer view it. This maintains data security while allowing necessary ticket reassignment.
The workaround using custom fields and triggers enables restricted agents to reassign tickets without needing to view them post-assignment. This ensures that sensitive information remains protected while still allowing operational flexibility.
Restricted agents can assign tickets outside their groups using triggers and custom fields. By creating a custom ticket field and setting up triggers, restricted agents can effectively reassign tickets to other groups without needing direct access….
A custom ticket field helps manage ticket assignments across groups. It allows restricted agents to specify which group a ticket should be assigned to, even if they don't have direct access to that group. To create this field, navigate to Admin…
Triggers automate the process of reassigning tickets based on custom field values. They ensure that tickets are assigned to the correct group when updated, regardless of the agent's permissions. To set up a trigger, go to Admin Center, select…
If your triggers aren't working, ensure all conditions and actions are correctly set. Double-check the custom field values and trigger conditions to ensure they match. If issues persist, consider reaching out to Zendesk support for further…