Day-level SLA-based routing
A system for day-level SLA-based routing, comprising a statistics server configured to collect, store, and provide service level agreement data; and a routing server configured to receive at least a customer interaction via a network, and configured to compare an interaction against service level agreement data provided by the statistics server, and configured to produce an interaction priority based at least in part on the comparison, and configured to route the interaction based at least in part on the interaction priority.
1. A system for day-level service level agreement-based routing, comprising:
a statistics server computer comprising at least a processor, a memory, and a plurality of programming instructions stored in its memory that, when operating on its processor, causes its processor to provide day-level service level compliance data for each of a plurality of interaction types based on the received event data; and
a routing server computer comprising at least a processor, a memory, and a plurality of programming instructions stored in its memory that, when operating on its processor, cause the processor to:
receive an interaction via a network;
determine an interaction type for the interaction;
retrieve day-level service level agreement compliance data for the interaction type from the statistics server;
establish a priority for the interaction by comparing the day-level service agreement compliance data for the interaction type to the day-level service agreement compliance data for each other interaction type from the plurality of interaction types; and
route the interaction based on the established priority for the interaction;
wherein the day-level service agreement compliance data for a specific interaction type is determined by computing, on a per-day or per-shift basis, a percentage of interactions of the specific interaction type that have been answered within a specific time limit.
2. The system of claim 1 , wherein the service level agreement compliance data further comprises an interaction count threshold, the interaction count threshold comprising at least a quantity of interactions of the interaction type required before considering the interaction type in day-level service level agreement routing decisions.
3. A method for day-level service level agreement-based routing, comprising the steps of:
receiving, at a routing server computer comprising at least a processor, a memory, and a plurality of programming instructions stored in its memory and operating on its processor, an interaction;
determining the interaction's
retrieving day-level service level agreement compliance data for the interaction type from a statistics server computer comprising at least a processor, a memory, and a plurality of programming instructions stored in its memory and operating on its processor;
establishing a priority for the interaction at least by comparing the day-level service agreement compliance data for the interaction type to the day-level service agreement compliance data for each of a plurality of other interaction types; and
routing the interaction based at least in part on the established priority for the interaction;
wherein the day-level service compliance data for a specific interaction type is determined by computing, on a per-day or per-shift basis, a percentage of interactions of the specific interaction type that have been answered within a specific time limit.
4. The method of claim 3 , wherein the service level agreement compliance data further comprises an interaction count threshold, the interaction count threshold comprising at least a quantity of interactions of the interaction type required before considering the interaction type in day-level service level agreement routing decisions.