Joe - wanted to ask a few questions here:
1) Do I understand this correctly? You have an inbound flow that attached skills on the transfer to ACD action that routes to a specific queue?
2) can you tell me (or send a screenshot) of the routing settings for the queue in question? I'm specifically wondering what 'evaluation method' you are using b/c my guess is that its 'disregard skills, next agent' as I would expect to see the skills come through for either of the other two options (which require an agent to have all matching skills that are assigned to an interaction.
3) Can you make sure you have exposed the three 'skill' options in the view listed above and see if any skills show up?
Thanks,
Chris
------------------------------
Chris Bohlin
Product Manager - PureCloud
------------------------------
Original Message:
Sent: 05-11-2022 11:14
From: Joe keenan
Subject: Prove In-queue call logic works as it should
Thanks for this Chris
Right now I am seeing interactions using "Standard" Routing used whereas I'm expecting some of them to be routed using specific assigned skills ( Which are showing blank in each case for the interactions) based on the ANI.
I'm trying to understand if I can see in more detail why each are using Standard routing rather than what I'm expecting to see, any idea how to see this info?
------------------------------
Joe keenan
Zimmer, Inc.
GCA-GC
------------------------------
Original Message:
Sent: 05-06-2022 08:15
From: Chris Bohlin
Subject: Prove In-queue call logic works as it should
Hey Joe, thanks for reaching out. We have a lot of this data right in the interactions view. You can see 'RoutingRequested' and 'RoutingUsed' as well as the skills that are attached to the interaction. I've listed a screenshot below of the various routing data available right in the UI. (This is available in the analytics/conversations/details endpoint as well if you prefer the API.)

------------------------------
Chris Bohlin
Product Manager - PureCloud