Generic selectors
Exact matches only
Search in title
Search in content
Search in posts
Search in pages

Weighted averages

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #32523 Reply
    Lee H.
    Guest

    I am a supervisor in a multi-queue call center. Currently, our department that calculates the total call center service level for all queues uses a add and divide method to calculate service levels.

    Example, if our queues end the day with a 75%, 63%, 97% and 84% service leveI, the overall call center ends up with a 79.75% service level for the day. I understand there is a “weighted average” formula that takes into account the total number of calls per queue, plus the service level in each queue in calculating an overall service level.

    What is the pro’s and con’s of using either method for caulculating overall service level? Any information would be greatly appreciated.

    Thanks.

    #32524 Reply
    Lester Bromley
    Guest

    The accepted method is to total all the calls that were answered within the SLA target and divide this by the total number of calls answered to produce the overall SLA percentage. Some switches will report this figure directly, e.g. the Lucent Definity defines the variable ACCEPTABLE in the VDN and Skill tables to count the number of calls answered within SLA. Otherwise multiply the number of calls answered in a queue by the SLA percentage for that queue to get the acceptable calls figure, add these together and divide by the total answered.

    This method is also used to calculate the monthly average from the daily figures for that month.

    (Note that some switches report the SLA as a percentage of offered calls rather than answered calls in which case use the offered calls figure instead)

    #32525 Reply
    KSG
    Guest

    The service level philosophy in our call center is simple. You can’t just keep adding staff to solve customer contact issues/problems. I think you ‘ve got to look at more effective solutions, by combining the skills ,technology and operational efficiencies to mangage a complex inbound service. In our skills-based routing environment, we have specialized groups, so we run interactive calculations. The Erlang-C method remains an accurate tool and it will probably always be around for teaching people queuing dynamics.

    #32526 Reply
    Knute
    Guest

    By following the method you are today, you are “averaging averages” which will not give you an accurate number. You must use a “weighted” average to accurately calculate your true call center service level for all Queues.

    Hope this helps.

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Weighted averages
Your information:




<a href="" title="" rel="" target=""> <blockquote cite=""> <code> <pre class=""> <em> <strong> <del datetime="" cite=""> <ins datetime="" cite=""> <ul> <ol start=""> <li> <img src="" border="" alt="" height="" width="">