After-Hours & On-Call Support

For two years the three technicians at Tollgate Foods carried a phone in turns, every third week. Somebody senior had once said the business needed twenty-four-hour support, and nobody had asked what for. When the desk finally counted, the phone had rung forty-one times in those two years. Nine of the calls were about something that could not wait. Thirty-two were passwords, printers and a man who wanted to know if the office would be open on the bank holiday. The technician on the phone that night had been woken for each of them. They had been paid for none of them, and had started, quietly, to look at other jobs.

This series is about the phone and who carries it. It covers whether you need after-hours cover at all, which is a question the ticket data can answer. It covers coverage models for small teams, drawn as week grids. That makes the load on each person visible before anyone signs up. Then comes the on-call rota people accept, with swaps that are easy and a week after that is lighter. It covers compensation and recovery time as principles, because the fair rota is the only one that stays staffed. It covers what counts as an after-hours call and the single route in. And it covers measuring and reducing the after-hours load until the phone rings for the nine, not the forty-one.

Articles in This Series

• Do You Need After-Hours Cover at All? Ask the Tickets First
  What actually breaks at night read from the ticket data, availability against support, the expectation nobody set, what the organisation really needs, and the need assessment.
• Coverage Models for a Small Team: Who Carries the Phone, and When
  The simple rota, the primary and secondary pair, escalation-only, and monitoring-driven coverage, drawn as week grids. Also covers why follow-the-sun is not available to three people, and the comparison.
• The On-Call Rota People Accept: Frequency, Swaps and Fair Weeks
  Frequency, easy swaps, the holiday rule, and the week after a bad week. Also covers the new starter never alone, the manager in the rota, publishing it far ahead, and the rota rules.
• Compensation and Recovery Time: Principles That Keep a Rota Staffed
  Paid for being available, paid more for being called, time back after a night, and the next morning protected. Also covers rules that vary by place and contract, and the agreement outline.
• What Counts as an After-Hours Call, and How It Is Raised
  Business-stopping only with examples, the single route in, the ticket logged first thing, the eleven-at-night password call, the manager calling on behalf, and the definition and route.
• Measuring and Reducing the After-Hours Load, Month by Month
  Calls per month, the time-of-day pattern, the recurring cause, the proactive fix that removes a class of call, the rota-fatigue signal, and the on-call log and monthly review.

Explore More Topics

This series is part of the QuerySolv helpdesk topic library. It covers the foundations, processes, communication, knowledge, tooling, metrics, classic ticket domains, people and strategy behind a support desk that works. The library pairs well with the software we build: QuerySolv. It is a self-hosted help desk that runs as one Windows service on your own network. It is licensed once per installation, not per agent per month.