Booking platforms plan support headcount around predictable demand: seasonal patterns, average query volumes, standard resolution times. Refund requests do not follow that plan. They arrive in waves, triggered by events outside a support team's control, and each one carries a cost that most platforms have never fully itemised.
The True Cost of a Refund Ticket
Support cost per ticket varies significantly by channel and complexity, but the gap is instructive. Self-service resolution costs as little as $1.84 per contact, compared with $13.50 for an assisted channel handled by a human agent, a 7.3x cost multiplier (Fullview, 2025). Phone support, still the default for anything requiring judgement, such as a refund exception, costs $17-$25 per contact against $1-$4 for a self-service resolution (Unthread, 2026). Retail and e-commerce support sits at the lower end of the market at $2.70-$5.60 per ticket, while SaaS-style and technically complex support runs $18-$35 per ticket (LiveChatAI, 2025). A refund query, which typically requires payment verification, policy interpretation and manual processing, tends to land at the higher end of whichever band a platform falls into.
Demand That Ignores the Staffing Plan
Peak periods compound the problem. Support ticket volume rises 1.5x to 3x above baseline during peak trading windows (StealthAgents, 2026, citing Zendesk and Gartner data), and event ticketing specifically shows an average refund rate of 21.8% of transactions (Gitnux, 2026). Teams staffed for that peak carry roughly 66% of their labour cost as overhead during quieter periods; teams that stay lean and absorb peaks with overtime see turnover rates 23% higher once agent utilisation holds above 85% for six consecutive weeks (Zendesk, 2025). Neither model is cheap. One overpays for idle capacity, the other pays for it in attrition and inconsistent service quality.
A Structural Problem, Not a Staffing One
The underlying issue is not how efficiently a support team processes refunds. It is how many refund requests ever reach an agent in the first place. For booking platforms, every query deflected before it becomes a ticket, and every refund resolved without manual payment processing, is capacity returned to the team and revenue kept. Reducing refund dependency on support is no longer a service-quality initiative; it is a cost-of-operations decision.
