Details
-
Story
-
Status: Resolved
-
Major
-
Resolution: Done
-
None
-
None
-
CRM Connector (CRMCONNECT)
-
Sprint 5 CTI 23 May - 5 Jun
-
5
Description
EWT Implementation Concerns
Following questions need to be addressed before proceeding to implement EWT Calculation
- Average Talk Time Calculation:
- What is time bracket to calculated Average Talk Time? e.g. 24 hours, 1 week, 1 month or start of time (full historical data)
- Where it should be maintained? e.g. fetching Avg Talk Time from Reporting DB upon every new task arrival, maintenance and calculation of Avg Talk Time in MRE's memory
- need to check how Cisco manages EWT
Implementation
A CSQ’s EWT = (Position of task in queue * CSQ’s average talk time in seconds)/Total number of working resources in CSQ
where:
- Total number of working resources in CSQ = sum of resources in RESERVED, ACTIVE, BUSY, PAUSED and WORK state
- If task is currently not queued, the position in queue = length of queue + 1
- If either the CSQ’s average talk time or the total number of working resources is 0, the EWT is –1
Example
if
- Total number of working resources = 5
- Position of Task in Queue = 8
- Average talk time = 15 minutes ~ 900 seconds
then
(8*900)/5 = 1440 seconds ~ 24 minutes
if
- Total number of working resources = 5
- Position of Task in Queue = 8
- Average talk time = 7 minutes ~ 420 seconds
then
(8*420)/5 = 672 seconds ~ 11 minutes 12 seconds
This formula addresses Voice calls, for Chat / Non-Voice MRD tasks we might need to reconsider it as one resource can handle more than 1 task simultaneously, affecting estimated wait time.
Customer Gadget should have a configurable parameter x time and should poll MRE for EWT after x time