Hello experts!
Just scratching my head about one task I was given by our worldwide customer and I'm looking for an easiest way to do it. Any suggestions would be greatly appreciated.
Here is the background:
Worldwide call center customer with hundreds of sites, a lot of agents and few call centers. There is an existing Avaya CC mix of Avaya CM (current version 6, plan to upgrade to 8), Avaya IPO and AACC. The voice part of the call center is handled directly by Avaya CM with over 750 vectors currently present.
The example scenario:
Lets say a group of 10 agents who are taking calls for department A, English speaking customers.
In this group there are 2 agents speaking English AND Italian. There are thousands of calls in English, but only a handful of calls in Italian per month. The service level is 20s.
When there is an outage, all the 10 agents are already busy with English speaking customers, and the few Italian customers can't get hold of anyone speaking Italian => the Service level is broken and kills the stats for the month.
The task:
The task is to reserve somehow the Italian speaking agents, for the few customers calling in such outage scenario (which occurs very rarely), so they can be answered within 20s, but still have them available to take the English speaking calls.
At the same time I would like to avoid checking/tampering with all the 750+ vectors and would like to do this on some more simple and "global" level, if such option exists.
There are dozens, if not hundreds, of such groups with similar design. This is just an example.
Basically the goal is, to have the Italian customer who is calling in 0.5% of the cases ALWAYS answered by an Italian speaking agent.
Of course we could break all this CC routing apart, re-design the skills and groups, re-write the vectors etc. but this we want to avoid, or have it as a last resort option.
If you could suggest some concept, way of doing this, a feature in the CM we should utilize...
Hope that is clear enough, excuse my English.
Should you need more info, please ask.
regards
Jou
Just scratching my head about one task I was given by our worldwide customer and I'm looking for an easiest way to do it. Any suggestions would be greatly appreciated.
Here is the background:
Worldwide call center customer with hundreds of sites, a lot of agents and few call centers. There is an existing Avaya CC mix of Avaya CM (current version 6, plan to upgrade to 8), Avaya IPO and AACC. The voice part of the call center is handled directly by Avaya CM with over 750 vectors currently present.
The example scenario:
Lets say a group of 10 agents who are taking calls for department A, English speaking customers.
In this group there are 2 agents speaking English AND Italian. There are thousands of calls in English, but only a handful of calls in Italian per month. The service level is 20s.
When there is an outage, all the 10 agents are already busy with English speaking customers, and the few Italian customers can't get hold of anyone speaking Italian => the Service level is broken and kills the stats for the month.
The task:
The task is to reserve somehow the Italian speaking agents, for the few customers calling in such outage scenario (which occurs very rarely), so they can be answered within 20s, but still have them available to take the English speaking calls.
At the same time I would like to avoid checking/tampering with all the 750+ vectors and would like to do this on some more simple and "global" level, if such option exists.
There are dozens, if not hundreds, of such groups with similar design. This is just an example.
Basically the goal is, to have the Italian customer who is calling in 0.5% of the cases ALWAYS answered by an Italian speaking agent.
Of course we could break all this CC routing apart, re-design the skills and groups, re-write the vectors etc. but this we want to avoid, or have it as a last resort option.
If you could suggest some concept, way of doing this, a feature in the CM we should utilize...
Hope that is clear enough, excuse my English.
Should you need more info, please ask.
regards
Jou