Hi,
We currently use outbound campaigns to deliver non-call tasks to agents. This has worked well, however, we are finding that it is requiring an increasingly large number of queues to be managed by agents, and campaigns to be managed by WFM. The reason for having so many queues is that we have agents with different skills, trained on different tasks.
i.e. currently, we have a queue and campaign for task A, a queue and campaign for task B and a queue and campaign for task C
Ideally, we would like to set things up differently, so that there is one queue and one campaign for a group of tasks (A, B & C). However, we can't seem to set skilling up to support this.
Although we can set up call rules to ensure only correctly skilled agents get each type of task, the issue in implementing a test for this has been that if there is no agent with the skills in place to handle the next interaction, the campaign stops until an agent with the correct skills logs in and takes an interaction.
In action, this would mean that we could have multiple agents trained on tasks A & B idle and waiting for a task, but if the next task in the list is a task C, they will not receive anything.
Is there any way around this? I am aware task diallers are on the roadmap for coming quarters, but wondering if anyone has anything similar in place with the current limitations?
Thanks,
#Outbound#Routing(ACD/IVR)------------------------------
Katie Brassell
Compassion Australia
------------------------------