Chat Priority

Any news on this request?  I'm also wanting to prioritise chat visitors and all my agents have all the skills so I don't need to create a new department.  Just have the ability to change the priority - you can do this with email by including a word in the subject title - maybe chat needs a subject title option?  Or is this already there and I just don't know… LOL!

Hey Zachary, thanks for your reply! I'll definitely look into that option and see if it will meet the requirements. 

We originally wanted to set up messaging but it didn't allow for us to authentication details to the widget so we had to use the basic chat, however, I understand this is also under development. 

Good luck with the transition 

Rebecca Katz my understanding is this is supported in Omnichannel Routing, which will work for messaging, but not chat. So I doubt this will developed, since it seems nothing new is being developed for chat. We're in the middle of a transition from chat to messaging because of this and several other features that are missing for chat. 

We have the exact same request, does anyone know if this has been developed in the past 5 years since this request was made? 

I  have the same needs Harriet is describing above. In Support we can assign SLA's based on ticket priority, and can create different SLA policies based on Org/User/Ticket attributes, and sort our queues by the SLA. This allows us to be very targeted about how our support is delivered.We should be able to do something similar in Chat. 

Hi René,

The problem with skills-routing in this scenario (at least for our user case) is handling high profile or high risk customers isn't a skill as such - all agents are capable of handling them, we just want to be able to reply to that customer segment (or queries that fall in that skill) first.

Please correct me if I've misunderstood, but I'm not sure using skills based routing or a separate department for this isn't a workaround unless you create a separate team specifically for high profile customers - which for us as a 24/7 operation isn't sustainable.  For example:

I have 10 agents online
3 have the skills for High Priority and Normal Priority Customers
7 have the skill for Normal Priority Customers only

If all 3 agents with High and Normal are at capacity, wouldn't the wait time for High Priority customers will end up being longer? As Normal Priority has a pool of 10 agents, and High Priority only a pool of 3 (and the High Priority customers will have some wait before being reassigned to the next available agent).

In short, I'm not clear on how Skills routing helps with prioritising based on type of customer or the skill - if there is a way to do this, it'd be great to see the configuration steps broken down to show how to prioritise Skills.

Thanks!

Hello Joe, Thanks for your comment. Have you considered to use our Skill based chat routing as a workaround?

Skills routing provides a way to identify specific skills for both visitors and agents and route chats accordingly, helping make sure your customers get the relevant and targeted support they need. For example, you might want to create a skill for Spanish-speaking visitors and agents so that chats are automatically routed appropriately.

More info here: Routing chats based on agent skills

agree with everyone above - any workarounds I've seen suggested fail to address the problem. Is there any update with this? 

I agree with Isac, is there any update on this feature? It has been three years since this was brought up to your attention.

This is a feature in your talk service, why not chat?