What's new in Customer Journeys?

Connect and learn more! ×
Best practices for rerouting incidents to other queues — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Best practices for rerouting incidents to other queues

Received Response


Content (required):

We frequently need to reroute/reassign incidents to another team by changing the queue. Our agents struggle to know which is the correct queue to select. We have several very siloed teams that each work in their own queue and have expertise in specific topics. If they don't choose the right queue, the incident won't be seen by the proper team and ultimately the response is significantly delayed. Does anyone have any suggestions and best practices for improving this experience?

Version (include the version you are using, if applicable):

Code Snippet (add any code snippets that support your topic, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!