Skills in Zendesk are agent attributes that help determine their suitability for handling specific tickets. They can be traditional skills, like language proficiency, or other attributes such as location or timezone. When setting up skills, you create skill types to categorize them, allowing you to assign specific skills to agents. For instance, you might have a 'Product' skill type with skills like 'ProductA', 'ProductB', and 'ProductC'. You can define up to 10 skill types, each containing up to 30 skills. To fully define a skill, it needs a name, a method to add it to tickets, and a set of agents who possess that skill.Learn more about skills in Zendesk.
Setting up skills-based routing in Zendesk involves several steps. First, plan out the skills you need, then create and assign them to agents. Next, configure an automated way to assign these skills to tickets. Depending on your needs, you can…
Omnichannel routing in Zendesk allows you to direct tickets from various channels like email, messaging, and calls to agents based on their availability, capacity, skills, and ticket priority. When skills are used in omnichannel routing, agents…
Yes, you can use skills-based routing for Messaging and Talk tickets in Zendesk, but only through omnichannel routing. Unlike standalone skills-based routing, omnichannel routing can handle messaging conversations, calls, and sometimes chats based…
If a ticket in Zendesk doesn't have a skill, the system assumes it can be assigned to any agent. To prevent this, you can use triggers to set a tag on tickets with skills, ensuring only tagged tickets are assigned to groups. This way, tickets…
The skills timeout setting in Zendesk's omnichannel routing is crucial for managing ticket assignments. It allows the system to first attempt to assign work to agents with matching skills. If no such agents are available within a specified time,…
Standalone skills-based routing in Zendesk is used for tickets received via email, web form, side conversations, and the API. It sorts incoming tickets by skills but doesn't directly route them to agents. Instead, agents use Views based on skills…