Good Morning!
Looking for a little advice or thoughts on how to handle a particular scenario. Let me set it up first:
We have two queues:
Calls first route to Queue 1 with one or two skills, and the customer gets qualified for our product. At this point let's say the call has "Skill A".
Once that happens, if the customer qualifies we route try to do a consult transfer to Queue 2 through a flow to work with a professional in a state they're licensed to work in. At this point we add a skill to the call to make sure only the correctly licensed agent gets the call. Let's call this "Skill B".
The issue come into play when nobody is available to take the call right away. In our In-Call flow we have the ability to create a regular callback and leave the call in the Queue 2. This works great and only leaves the call with "Skill B" which is expected.
If, however, the customer isn't able to take a call again right away and wants one scheduled it appears that both "Skill A" and "Skill B" are attached to the scheduled callback we create because those skills were, at some point, added to the participant data of the call. Or at least that's my assumption.
Because of this, when the callback is created it contains skills for both Queue 1 and Queue 2...but nobody can answer the call because nobody has both sets of skills. Just one or the other.
Our current workaround is to just monitor these situations and create a new callback via the API with the correct skills and participant data, then delete the old one. This obviously isn't ideal, however.
Let me know if the situation makes sense and if you have any thoughts.
Cheers!
#ArchitectureandDesign
------------------------------
Brian Stephens
Telecom Developer
------------------------------