How-To: Targeted Routing with Custom ACD

I was teaching a Customer Interaction Center handler developer class recently when one of my students gave me a scenario that had been causing them some head-scratching. The call center in question is not a typical one. In this case, when people call in they are prompted for an identifier (customer/case number). The requirement was that the system should look up the number in a database, retrieve the identity of the agent that “owns” the particular customer and route the call appropriately.

So far so good. If the agent concerned is not available, then the call should be directed to another member of their team. Still not too bad, until…

There are some agents who should not be offered calls from certain callers due to what the student referred to as a “conflict of interest.” Now it gets interesting.

The solution we came up with may not be the only, or even the best way to achieve this, however this was what we did:

1. We started up by creating a database with two tables. The first table mapped customer IDs to the corresponding “owning” agent and the second table mapped customer IDs to “conflicting” agents.

2. Next, we created a single workgroup with a queue of type “Custom.”

3. We created a skill for each agent. (This part is the most time consuming.) The agent themselves is then given their own skill with a proficiency score of 100. The other members of their team are also given the skill, but with a lower proficiency, say 50. (Note, we wouldn’t normally recommend using the numbers, but this is an example of when it can help).

4. Interaction Attendant was then set up to prompt the caller for their ID and store the result in a call attribute before routing the call to the Workgroup.

5. A handler was written and called from CustomIVRWorkGroupQueue that queries the database tables. In the case of the first table (the “owning” agent) the corresponding skill was added to the interaction. In the case of the second table (“conflicting” agents) the relevant agent’s skill was also added, but with a maximum proficiency set at 90. The call was then routed to the workgroup for processing, but ignoring agent availability time.

Let us consider an interaction coming in. Five agents are available – A, B, C, D & E. The customer enters an ID number that identifies them as belonging to agent A and having a conflict with agents D & E. The handler adds A’s skill to the interaction along with D & E’s skills, but the latter with a maximum proficiency score of 90. The automatic call distribution (ACD) engine will rule out agents D and E since they don’t have the necessary skills. Agents A, B & C all have all three skills but since A has a higher proficiency in their own skill they will end up with the highest score and get the interaction.

Now, same scenario, but A is not available. In this case, B or C will get the call. If A, B & C are all unavailable, then the call will wait in queue for one of them.

This could be expanded to include a form of bull’s eye routing where agents could all have differing levels of skills thereby setting up a preference system of who should get the call if the designated agent is not available. This was beyond what the student had asked for, but when I proposed it, his eyes lit up with the possibilities!

Let me know what you think. How would you solve this particular problem?

Paul

Paul Simpson

Paul Simpson

I joined Interactive Intelligence in January 2008 as a Training Consultant in the Education Department. Based initially in the Amsterdam office, I transferred to Indianapolis in 2010, where I still work in Education. My formal areas of interest are Interaction Dialer and Interaction Process Automation, however I can usually be found experimenting with various abstract parts of the product and love to make it do cool things! I’m always playing around with scripting and automation. Anyone who has attended one of my classes will tell you that my theories of troubleshooting can involve chickens and I am passionate about the correct pronunciation of the word “router.” Prior to Interactive Intelligence, I worked as a school teacher (mathematics and computing), a network engineer (mostly Novell), a hardware support engineer and a developer. I can trace my computing history back to the days of the Z80 and 6502. I have a keen personal interest in home media and automation. I am also developing an interest in Animatronics and would like, one day, to create a haunted-house walk-through for Halloween. I can be quite opinionated and hope that my blog posts will spark some healthy debate.