serviceMob used its proprietary methodology and algorithms to help a healthcare unicorn forecast its contact demand better than the Erlang C model that's widely used by other call centers
Auctor purus, aliquet risus tincidunt erat nulla sed quam blandit mattis id gravida elementum, amet id libero nibh urna nisi sit sed. Velit enim at purus arcu sed ac. Viverra maecenas id netus euismod phasellus et tempus rutrum tellus nisi, amet porttitor facilisis aenean faucibus eu nec pellentesque id. Volutpat, pellentesque cursus sit at ut a imperdiet duis turpis duis ultrices gravida at aenean amet mattis sed aliquam augue nisl cras suscipit.
At elit elementum consectetur interdum venenatis et id vestibulum id imperdiet elit urna sed vulputate bibendum aliquam. Tristique lectus tellus amet, mauris lorem venenatis vulputate morbi condimentum felis et lobortis urna amet odio leo tincidunt semper sed bibendum metus, malesuada scelerisque laoreet risus duis.
Ullamcorper pellentesque a ultrices maecenas fermentum neque eget. Habitant cum esat ornare sed. Tristique semper est diam mattis elit. Viverra adipiscing vulputate nibh neque at. Adipiscing tempus id sed arcu accumsan ullamcorper dignissim pulvinar ullamcorper urna, habitasse. Lectus scelerisque euismod risus tristique nullam elementum diam libero sit sed diam rhoncus, accumsan proin amet eu nunc vel turpis eu orci sit fames.
“Sit enim porttitor vehicula consequat urna, eleifend tincidunt vulputate turpis, dignissim pulvinar ullamcorper”
Nisi in sem ipsum fermentum massa quisque cursus risus sociis sit massa suspendisse. Neque vulputate sed purus, dui sit diam praesent ullamcorper at in non dignissim iaculis velit nibh eu vitae. Bibendum euismod ipsum euismod urna vestibulum ut ligula. In faucibus egestas dui integer tempor feugiat lorem venenatis sollicitudin quis ultrices cras feugiat iaculis eget.
Id ac imperdiet est eget justo viverra nunc faucibus tempus tempus porttitor commodo sodales sed tellus eu donec enim. Lectus eu viverra ullamcorper ultricies et lacinia nisl ut at aliquet lacus blandit dui arcu at in id amet orci egestas commodo sagittis in. Vel risus magna nibh elementum pellentesque feugiat netus sit donec tellus nunc gravida feugiat nullam dignissim rutrum lacus felis morbi nisi interdum tincidunt. Vestibulum pellentesque cursus magna pulvinar est at quis nisi nam et sed in hac quis vulputate vitae in et sit. Interdum etiam nulla lorem lorem feugiat cursus etiam massa facilisi ut.
Our client was being penalized and did not have a predictable model for forecasting contact demand. The business lacked the ability to understand how many agents were needed to meet demand, but moreover, what were the accurate shifts needed, accounting for growth/detraction factors beyond the standard Erlang model used today.
Client: Healthcare Organization with around 25,000 contacts (customer interactions) per month
Channels Supported: Voice | Chat | Email
serviceMob worked with our customer to rationalize and understand their service operation capabilities as it pertained to WFM (Workforce Management). Our customer was utilizing software based on the standard Erlang-C model to predict traffic/agent line requirements for their Voice Channel.
Erlang-C is based on the assumption that the incoming call rate follows a Poisson distribution and that the length of each call follows an exponential distribution.
The model takes into account the average call duration, the call arrival rate, and the number of agents in order to calculate the probability that a call will be answered in a certain amount of time (e.g. within 20 seconds).
The model (Erlang-C) takes into account the average call duration, the call arrival rate, and the number of agents in order to calculate the probability that a call will be answered in a certain amount of time (e.g. within 20 seconds).
However, Erlang-C is not equipped to forecast demand based on drivers such as growth or detraction, as it is primarily concerned with predicting the number of agents/contacts needed to handle a given volume of calls. It does not account for factors such as changes to the customer base, changes to product lines, or intensive marketing tactics, which can all affect the demand for contact centers.
However, Erlang-C is not equipped to forecast demand based on drivers such as growth or detraction, as it is primarily concerned with predicting the number of agents/contacts needed to handle a given volume of calls.
Additionally, Erlang-C does not take into account repeat contact demand, as it is based on the assumption that each call is independent of the others. This means that the model is not well-suited for predicting demand of customer service and support centers in growth stage businesses, where changes to the customer base and product lines may lead to an increase in contact demand.
Moreover, the additional improvement of precision in forecasting accuracy for mature contact centers or businesses with stable queues still shows promise for improvement, given the above-mentioned issues which plague WFM teams. Using our proprietary methodology and algorithms, we were able to reduce the recommended headcount significantly.
Using our proprietary methodology and algorithms, we were able to reduce the recommended headcount significantly.
With greater precision of forecasting, serviceMob then initiated our SHOP (Shift Optimization Pattern), identifying what were the recommended shifts given the new forecast and what was the optimized schedule vs. the incumbent schedule, which was based on a generalized Erlang-C pattern. In conjunction with accounting for repeat contacts, growth, and using real-world data based on agent performance and customer wait tolerance, we were able to deflect over $7M in cost savings.
In conjunction with accounting for repeat contacts, growth, and using real-world data based on agent performance and customer wait tolerance, we were able to deflect over $7M in cost savings
Regardless of the systems utilized, no matter the channels supported, or the technology franken-stack you have – serviceMob can ensure you have the analytics needed to make better/faster decisions about your contact center.