3 ms·
The calculator at the bottom of the page is doing some weird calculations. If you have no incidents a year, it still costs you money. So do incidents that take
by jmholla 3y ago
The calculator at the bottom of the page is doing some weird calculations. If you have no incidents a year, it still costs you money. So do incidents that take zero minutes to resolve. I took apart the code, and this seems to be the equation in use:
(revenueTarget / 8760) * resolutionTimeTarget * numIncidentsTarget * resolutionTimeTarget + numEmployeesTarget * avgEmployeeTargeRate
This means revenue lost is correlated to the square of the lost time and the cost from employees is a static yearly cost.
There are a couple things wrong with it. The third * should be switched with a + and the last term need to be multiplied by the number of incidents.
(revenueTarget / 8760) * resolutionTimeTarget * numIncidentsTarget + resolutionTimeTarget * numEmployeesTarget * avgEmployeeTargeRate * numIncidentsTarget
Which if anyone at Call Stacking is here, just means changing
o = (n / 8760) * e * t * e + i * r;
to
o = (n / 8760) * e * t + e * i * r * t;
or more succinctly
o = t * e * (n / 8760 + i * r)
I'm assuming that's minified, so
numIncidentsTarget * resolutionTimeTarget * (revenueTarget / 8760 + numEmployeesTarget * avgEmployeeRateTarget)
Edit: With the correct math, the example is wildly different. It should be $37,277.81, not $87,991.23.
- xmcqdpt2 3y agoMaybe there is a tool that can help them trace where this bug is coming from in their cost calculator?