Question
A number of tickets were systematically routed from one agent back to the group. There aren't any triggers or automations responsible for the reassignments. None of my agents reassigned these tickets. Why were tickets randomly reassigned back to the group?
Answer
When you remove the current assignee from a group, the ticket maintains its group status.
If an agent is assigned tickets in a particular group and then removed from that group, those tickets are automatically reassigned back to the original group. In some cases, those tickets are automatically reassigned back to the admin who removed the original assignee from that group.
For more information, see the articles: Best practices for removing agents and Best practices for deleting groups.
3 comments
JOSEFA
Hi, This is great. I do have a question thoguh. I have 2 agents who are in quite varied roles and they will frequently move in and out of groups. Is there a way we can keep them in all groups but only allow phone calls to come through to them from one of the groups they are part off? Eg if an agent is part of "sales", "internal support" and "contact centre" can I keep them in all of these groups but only have calls from "internal support" routed to them?
Cheers, Josef
0
Dave Dyson
I think the only way to do that would be to maintain special groups for the routing of calls. If you like, please post to our Feedback - Voice (Talk) topic, using our Product Feedback Post Template to format your input. Thanks!
0
Mike Larsen
We are seeing this, but in a different circumstance. Our agent is continuously a member of the group - so, again, it is NOT that we removed the current assignee from a group.
Instead, the “system” makes the assignee empty (it clears the assignee). This happens thusly:
To be clear, we want the assignee to remain unchanged so the agent is still the assignee and the ticket is NOT unassigned.
We believe the agent was online throughout. In fact, we are seeing cases where the agent marks a ticket as solved and then the user responds shortly after while the agent is still viewing the ticket. But of course the agent must reassign the ticket to themselves.
The system does this action. We review the tickets' history and see the fingerprint of the ‘system’ - there is no trigger or other rule that does this. And I've looked at system settings and find no setting that would do this sort of reassignment. I thought maybe the agent was somehow “offline” and the system determined an “online” agent should have the opportunity - but this seems to not be the case.
Why does the system take the assignment away from the assignee agent when a WhatsApp ticket transitions from Solved or Pending back to Open?
0