Round Robin Ignores Language Skill During Peak
HelpDesk Co. has eight agents and three skills: Spanish, Billing, and API. About 120 tickets arrive each day; roughly 30 are Spanish and 25 are Billing. Dispatch'r is configured with these rules in order: (1) if subject contains 'factura' or 'pago', assign to Billing group; (2) if subject contains 'error' or 'API', assign to API group; (3) round-robin to the General group. Agent skills are recorded in Freshdesk, but the rules never reference them. One of the three Spanish agents is on leave for two weeks. Spanish billing tickets now land with monolingual Billing agents, who reassign them manually; 45 tickets are unassigned or misassigned, and first response for Spanish tickets has risen to 18 hours. The manager wants to add a fourth rule that assigns all Spanish tickets to the remaining two Spanish agents. You need to improve routing without burning out those two agents or starving the General queue.
1. Explain why the current Dispatch'r order produces the observed misrouting, and what else you would check before editing rules.
Read the worked answer
Dispatch'r evaluates rules from top to bottom and the first matching rule wins. A Spanish billing ticket with 'factura' matches rule 1 and goes to the Billing group before any language logic can run. Rule 4, added at the bottom, would only catch Spanish tickets that did not match rules 1 or 2 - which is the wrong subset. The skills exist on agent profiles but are not used by the rules, so assignment is keyword-driven, not skill-driven.
Before editing, check group membership and whether Billing has any Spanish speakers, verify the three Spanish agents' skills and availability, and confirm the round-robin setting for each group. Check whether Observer or another automation reassigns tickets after creation, which could undo Dispatch'r. Also check whether 'factura' appears in non-billing contexts, causing false positives. The observed 45 misassigned tickets are consistent with rule order plus leave, not with a missing fourth rule.
2. Propose a routing design that respects skills, handles the leave, and includes an overflow path.
Read the worked answer
Redesign around skill-based groups and combined conditions. Create Spanish Billing, Spanish General, Billing, API, and General groups. Put combined rules first: if language is Spanish and product is Billing, assign to Spanish Billing; if language is Spanish, assign to Spanish General; then billing and API rules; then General. Use a required custom field for language rather than subject keywords, because customers write in many formats.
Within each group, use round robin or load balancing, not a manual list. During the leave, temporarily add one bilingual billing agent to Spanish Billing, cap that group's WIP, and add an overflow rule: if a Spanish ticket is unassigned for 15 minutes, assign to the Spanish General group and notify the lead. Do not send all Spanish tickets to the remaining two agents; that creates a new bottleneck and burnout risk. Reassess after the leave and remove the temporary membership.
3. Which metrics would show whether the redesign worked, and what would make you roll it back?
Read the worked answer
Track Spanish first-response time, percentage of Spanish tickets reassigned at least once, unassigned age by group, per-agent open ticket load, SLA breach rate, and CSAT for Spanish vs English. Also track the two Spanish agents' WIP and after-hours workload. A successful redesign should lower reassignment rate and Spanish first response without raising General queue age.
Roll back or adjust if the Spanish queue age rises above the pre-change baseline for two consecutive weeks, if either remaining Spanish agent exceeds the agreed WIP cap, or if General tickets starve because bilingual agents are pulled into overflow. Compare a two-week pilot against a two-week baseline, not a single day. If the combined rules increase misrouting because the language field is incomplete, fix the form first rather than adding more keyword rules.