Genesys Cloud - Main

Has anyone had trouble with contact list sorting when using skill-based dialing?
I am sorting items by a unique sequence number-type column and using 2 other fields for skill values.  The dialer is calling items in random order....not by the sort order at all, and we confirmed we have agents available for all the skill values so its not skipping records due to available agents.   Any idea what's going on??

More details:   DialMode=Progressive;  Dynamic Sorting=Enabled;  Dynamic Filtering=Enabled;  Sort by "priority" numeric ascending;  Filter in place does not restrict any records in the contact list.

So, looks like you are asking Dialer to do too many conflicting things kind of like Robby the robot a simple question and you get 

Skills based dialing is its own dictator when it comes to dialing patterns in that it will pretty much ignore almost all other priorities to dial for only the agents that are available for the skill needed.  Even the pacing between Power and Progressive can be affected.  My suggestion would be that if you REALLY want skills-based dialing, then only do that.  If you are doing skills-based routing, then you can do the sorting and filtering.

Has anyone had trouble with contact list sorting when using skill-based dialing?
I am sorting items by a unique sequence number-type column and using 2 other fields for skill values.  The dialer is calling items in random order....not by the sort order at all, and we confirmed we have agents available for all the skill values so its not skipping records due to available agents.   Any idea what's going on??

More details:   DialMode=Progressive;  Dynamic Sorting=Enabled;  Dynamic Filtering=Enabled;  Sort by "priority" numeric ascending;  Filter in place does not restrict any records in the contact list.

Very happy to see [Environmental Control] Robot again!  Wish i had an 8-track on hand to program him with.  
SBD (skill-based dialing) "documentation" doesn't put a condition on sorting, but we know there's a dependency when Dynamic Sorting is required to enable it in the first place.  I sorted the data by skills and it didn't line up to the order of calls either.  And we did verify all skills in the contact list were assigned to available agents...no records were skipped over due to agent availability.   We're doing this in a testing environment so we're able to pull back on the reins to let the dialer do one record a time with one available tester/agent.   Sorting on a non-skill field is required because it drives the order of processing by the dialer;  our users will add records whilst the campaign is running for priority calls (sorting bubbles them up to the top).  Both SBD and Sorting are required to make it work.   Dropping SBD will result in queued campaign calls and a high abandonment rate and a bad experience for our customers; thus a no-go there.
We've opened a support ticket.

So, looks like you are asking Dialer to do too many conflicting things kind of like Robby the robot a simple question and you get 

Skills based dialing is its own dictator when it comes to dialing patterns in that it will pretty much ignore almost all other priorities to dial for only the agents that are available for the skill needed.  Even the pacing between Power and Progressive can be affected.  My suggestion would be that if you REALLY want skills-based dialing, then only do that.  If you are doing skills-based routing, then you can do the sorting and filtering.

Has anyone had trouble with contact list sorting when using skill-based dialing?
I am sorting items by a unique sequence number-type column and using 2 other fields for skill values.  The dialer is calling items in random order....not by the sort order at all, and we confirmed we have agents available for all the skill values so its not skipping records due to available agents.   Any idea what's going on??

More details:   DialMode=Progressive;  Dynamic Sorting=Enabled;  Dynamic Filtering=Enabled;  Sort by "priority" numeric ascending;  Filter in place does not restrict any records in the contact list.

Has anyone had trouble with contact list sorting when using skill-based dialing?
I am sorting items by a unique sequence number-type column and using 2 other fields for skill values.  The dialer is calling items in random order....not by the sort order at all, and we confirmed we have agents available for all the skill values so its not skipping records due to available agents.   Any idea what's going on??

More details:   DialMode=Progressive;  Dynamic Sorting=Enabled;  Dynamic Filtering=Enabled;  Sort by "priority" numeric ascending;  Filter in place does not restrict any records in the contact list.