This is a companion Lab to What Is the Exponential Distribution?. The original article uses AI-to-human handoffs to explain exponential waiting times, Poisson thinning, memorylessness, and M/M/c queues. Here, change the numbers directly.
The default scenario has 100 incoming contacts per hour, a 20% human handoff rate, and a 12-minute average handle time. Humans receive 20 contacts per hour, while one agent completes five per hour on average. The offered load is four Erlangs. Four agents match mean demand but leave no capacity to clear a queue. With seven agents, this simplified model answers about 96.1% of contacts within five minutes.
Change the handoff rate and staffing
The values below are educational assumptions, not an estimate for a particular company or contact center. Arrivals are independent Poisson events, handling times are exponential, customers do not abandon, and every agent has the same skill and service rate.
THE ARCHIVE / LAB 03
Turn AI handoffs into a queue
Compare human handoff rate, average handle time, staffing, and target answer time in one view.
The queue is stable under this simplified model.
STAFFING COMPARISON
How much can one more agent change service level?
ONE ILLUSTRATIVE HOUR
A mean interval is not a timetable
These marks show one simulated hour of handoff times at the same mean rate. Regenerating changes the pattern, not the mean arrival rate.
Illustrative model · Assumes independent Poisson arrivals, a constant handoff probability, exponential handling times, no abandonment, and interchangeable agents. Actual workforce planning also needs interval demand, abandonment, shrinkage, skill mix, and schedule constraints.
Why 80% AI containment does not imply an 80% staffing cut
Lower the handoff rate from 20% to 10%. With every other input unchanged, human arrivals fall from 20 to 10 contacts per hour and the mean interval grows from three to six minutes. That is a meaningful improvement.
It does not mechanically halve the required team. A six-minute average interval can still contain two arrivals in one minute or none for a while. An average is not a timetable. And after AI resolves routine tracking and information requests, human agents may face more exceptions, cancellations, and disputes. If average handle time rises, the offered load does not fall as much as the handoff rate suggests.
Stable is not the same as meeting a service target
At 20 human contacts per hour and a 12-minute average handle time, one agent has a service rate of five contacts per hour. Offered load is:
With agents, this simplified queue is stable only when . Four agents match mean capacity and cannot recover from a queue. Yet stability does not guarantee an adequate experience: five agents are stable in the default scenario, but answer only about 63.5% of contacts within five minutes. Seven reach about 96.1%.
In this Lab, staffing is not a universal cost-minimizing answer. It is an operating decision for meeting a chosen waiting-time target.
What the model leaves out
- Arrival rate may change by time of day, day of week, and incident state.
- The AI handoff rate can vary with the model, knowledge base, contact type, and customer preference for a person.
- Handling times may have a longer tail than an exponential distribution, and vary by agent and case type.
- Customers can abandon while waiting; Erlang A may then be a more suitable model.
- Real operations include breaks, training, after-contact work, absence, shift constraints, and skill-based routing.
This Lab is therefore a starting point for reasoning, not a workforce-management system. Its purpose is to connect the AI-resolved share with the arrival rate, handling time, variability, and service objective of the work left for humans.
Discussion
Discussion
Have a question, correction, counterexample, or another interpretation?