When you have skill based routing, the agent's skill profile, and not his geographical location, decides which queues for incoming and outbound calls, email and chat, he will be serving. You can trim the routing - to sort, prioritize, and distribute all kinds of contacts to the appropriate destination. Contacts can be routed by criteria combinations, such as
- Skills
- Groups
- Queue length
- Contact data
- Customer profile
- Last agent to serve the customer
- Number of logged in agents
- Time of the day
Contacts in ACE are either routed to a queue, or to a waiting list. When queues and waiting lists are created in ACE Admin, the administrator at the same time determines the required combination of skills, and/or groups for serving this very queue or waiting list. By routing the contacts to the appropriate queue or waiting list, you indirectly route to agents with the correct skill profile.
Contacts
It is possible to configure the routing of the following types of contacts:
- Incoming calls
- Incoming calls to an IVR connected to the ACE solution.
- Incoming email
- Incoming emails to a mail server included in the ACE solution.
Incoming work items are routed in the same way as email, using the same mechanisms. Work items can be anything from messages about work tasks from an open interface, forwarded to the agents for actions in various support systems, to conversations in social media. - Callback calls
- Outbound calls to a customer who has asked to be called. The customer’s request is normally registered via an automatic mechanism, for example in an IVR dialogue or on a web page.
- Incoming chat
- On a company’s web page a customer can be offered to chat with the customer service. A web link leads to a specific web server where a chat engine communicates with the ACE solution, which in turn creates a chat contact.
Routing and escalation work in the same way for all types of contacts above. The exception, routing of campaign calls, is handled in the windows where the campaign is created, under the Media | Outbound telephony menu choice.
Contact data
For each contact, an amount of information known as contact data is automatically created. The basis for the contact data can come from e.g. a call’s IVR dialogue or a sender’s address in an incoming email.
Contact data are used in several ways in an ACE solution, for example in statistics. The interesting point here is that contact data are used to route contacts to appropriate agents.
Contact data for a particular contact comprise values for a number of parameters that are important for the current type of contact.
Here is an example...
An IVR dialogue is often designed to give the calling party a number of menu choices, e.g. 1 (for orders) and 2 (for support).
Menu choices can be viewed as a parameter which, for a particular contact, can assume the value 1 or 2.
Another name for this type of parameter is “contact data key”, or just “key”. A particular contact has a particular set of contact data keys, each with a special value.
All contacts of a particular type (in a particular ACE installation) normally have the same set of contact data keys. All contacts of the “incoming calls” type can have ANIS among their contact data keys, for example. However, a contact of the “incoming email” type does not have any such contact data key.
The value of a contact data key does not have to be numerical. In principle, any text string can be processed, for example the word “support” instead of the digit 2.