Hi Vikram,
as Geoff is saying you should not implement them for IPCC, for most of the other ACDs it should be all autoconfiguration.
Here is what I wrote about subs some time ago:
Subskillgroup enablement:
I think the main benefit of sub-skill groups is that it provides the ability to have a built in overflow group.
Some set of agents would be in the primary group, if no one is available for x amount of time, the script would try the overflow group.
In this way, you can see when a secondary agent takes a call what skill group it was meant for when looking at skill group or agent skill group reports.
You can do this because the overflow group is specific to the skill group.
The other way to do it is to have one catch all skill group which serves as an overflow for all skill groups.
If any skill group does not get serviced in x amount of time, dump out to the overflow which all agents are a member of. This works functionally, but you lose a level of detail in reporting.
If you have 5 skill groups in contact center and one catch all overflow group, when an agent takes a call on the overflow, you lose track at a skill group level what the call was intended for.
You really can't tell which skill groups are understaffed by looking at the catch all overflow.
Having a distinct overflow for each skill group will let you know which types of calls a particular agent took, or how many calls did or did not get handled by a particular primary group.
You can do the same thing today by using skill groups and enterprise skill groups instead of subgroups and skill group roll ups.
It just requires about 6 more steps to add a separate overflow skill group and then add an enterprise skill group, and then set up an appropriate report.
With sub-groups, these steps are pretty much built in.
Another place where I see sub-skill groups being useful is when you are trying to set up language support for different skills."
Regards,
Riccardo
PS. Please remember to rate useful posts
