Complaints as a workstream: why they break your staffing model
Not just a longer call
Complaints get folded into the general queue as if they were ordinary contacts that happen to take a bit longer. They aren’t, and treating them that way quietly distorts both your service and your staffing. A complaint has a different handle time, a different skill requirement, a regulatory clock, and a tail of follow-up work that never appears in a simple inbound model. Plan for it as “a call, but slower” and you will mis-size the team and miss the deadlines that actually carry risk.
Why the normal model doesn’t fit
Three things break. First, handle time is long and highly variable — a complaint might be ten minutes or two hours, and that variance wrecks an Erlang assumption built for tight, predictable calls. Second, much of the work is deferred: the live contact is only the opening: investigation, callbacks, letters and case-handling stretch over days, so the real workload is a case backlog, not a call queue. Third, the clock is regulatory, not operational — in UK financial services, complaints carry defined response and resolution deadlines, and a breach is a compliance event, not just a poor experience. So the right service measure isn’t average speed of answer; it’s the share of cases resolved within the regulatory window, planned and resourced as deliberately as any frontline target.
How to plan it
Carve complaints out as their own workstream with their own people, skills and measure. Size it as deferrable case work against the regulatory deadlines — how many cases arrive, how long each takes across its whole life, and how much resource clears them inside the window with margin — the same logic as any backlog, but with a compliance clock instead of a service one. Protect that capacity from the live queue, because the moment complaints handlers get pulled onto calls, the cases age and the breaches start. And feed the volume back upstream: a rising complaint rate is a demand signal and a process signal at once, and the planner is often the first person positioned to see it. Handled as a workstream, complaints are controllable; handled as long calls, they’re a standing risk.
Pair this with managing non-real-time work, Consumer Duty for planners, and planning for vulnerable customers.