Uploaded image for project: 'Chat Solution'
  1. Chat Solution
  2. CSN-1129

Queue Position and Estimated Wait time

    XMLWordPrintable

Details

    • Story
    • Status: Resolved
    • Major
    • Resolution: Done
    • None
    • chat 3.9
    • communication server, MRE
    • 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

      1. Average Talk Time Calculation:
        1. What is time bracket to calculated Average Talk Time? e.g. 24 hours, 1 week, 1 month or start of time (full historical data)
        2. 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:

      1. Total number of working resources in CSQ = sum of resources in RESERVED, ACTIVE, BUSY, PAUSED and WORK state
      2. If task is currently not queued, the position in queue = length of queue + 1
      3. If either the CSQ’s average talk time or the total number of working resources is 0, the EWT is –1

      Example

      if

      1. Total number of working resources = 5
      2. Position of Task in Queue = 8
      3. Average talk time = 15 minutes ~ 900 seconds

      then

      (8*900)/5 = 1440 seconds ~ 24 minutes
      

      if

      1. Total number of working resources = 5
      2. Position of Task in Queue = 8
      3. Average talk time = 7 minutes ~ 420 seconds

      then

      (8*420)/5 = 672 seconds ~ 11 minutes 12 seconds
      

      Cisco Community Reference

      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

      Attachments

        Issue Links

          Activity

            People

              awais.aslam Awais Aslam
              adnan.tariq Adnan Tariq (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 1 week, 2 hours Original Estimate - 1 week, 2 hours
                  1w 2h
                  Remaining:
                  Time Spent - 1 week, 2 days, 2 hours, 53 minutes Remaining Estimate - 2 hours, 55 minutes
                  2h 55m
                  Logged:
                  Time Spent - 1 week, 2 days, 2 hours, 53 minutes Remaining Estimate - 2 hours, 55 minutes
                  1w 2d 2h 53m