A support manager is given budget for three temporary staff for a six week peak. She is pleased, and then she works out the calendar.
Recruitment takes two weeks. Equipment and access take a few days. Training takes a week during which two of her permanent staff are unavailable. The temporary staff become genuinely useful in week five.
For weeks one to four she is effectively down two experienced people. The peak is hardest in week two, and that is precisely when her team is smallest.
The first failure: the calendar does not work
Recruiting, equipping and training take longer than most peaks last. The maths of this is rarely done before the budget is requested and it decides the whole outcome.
The second failure: training consumes the experienced staff
Every hour of training is an hour of the best people not handling contact, taken during the busiest period, which is the opposite of what was intended.
The third failure: the new people cannot answer the hard questions
They handle the routine, which is fine, except that the routine is exactly what could have been handled without them, and the complex work still queues behind one or two people.
The fourth failure: the ramp cost is never counted
Recruitment fees, equipment, licences, access provisioning, supervision and the errors made while learning. The wage is the smallest component and it is the only one in the business case.
The fifth failure: the knowledge leaves in January
Six weeks of accumulated understanding walks out of the door, and it will be rebuilt from scratch next year, which is the ground in onboarding new support staff faster.
The sixth failure: quality drops at the worst moment
Customers contacting during peak meet the least experienced people in the organisation, during the period when the business most wants to impress them.
The seventh failure: the spike is not evenly distributed
Peaks have peaks. A particular fortnight, particular days and particular hours carry the load, and a fixed temporary headcount is idle for most of the period and insufficient during the worst of it.
The eighth failure: the same questions dominate every year
The seasonal mix is highly predictable and almost nobody writes it down while it is happening, so next year begins with the same blank page.
The ninth failure: the evening and weekend hours are worst
Peak demand shifts later and into weekends, which is the coverage problem in weekend and holiday cover questions.
The tenth failure: the permanent team burns out anyway
Long days across a peak, followed immediately by the returns and complaints period, is how good support people are lost in February.
The eleventh failure: the ecommerce version is identical
Merchants face precisely the same arithmetic, which is set out in peak season support without hiring.
The twelfth failure: nobody prepares the answers instead of the people
The alternative to hiring bodies is documenting answers, and the second is faster, cheaper, reusable next year and available at every hour.
The fix: scale the answers rather than the headcount
An assistant that handles the predictable seasonal volume from the moment the peak begins, with no ramp, no recruitment and no training cost, keeps the experienced team on the work that needs them. That approach is set out in the support playbook for seasonal traffic spikes. Start at try, see features, and the sector view sits under small business.