Skip to main content
customer-supportholiday-coverageescalationsupport-operationsoutsourcing

Holiday Support Coverage: Who Decides in December

By IMMIDO Team7 min read

Christmas Day 2026 is a Friday. Boxing Day, 26 December, is normally a bank holiday, one of the UK's official holidays, and in 2026 it falls on a Saturday. GOV.UK, the UK government's site, gives the rule for that case: if a bank holiday is on a weekend, a substitute weekday becomes a bank holiday, normally the following Monday. So the UK bank holiday is Monday 28 December, though GOV.UK also notes that employers do not have to give paid leave on bank holidays. In France, Service-Public, the French government's site, says that among the public holidays, only 1 May is a compulsory day off for all private-sector employees, except in businesses that cannot stop work, such as hospitals and public transport. Whether the others are days off is set by a collective, branch or company agreement or, if there is none, by the employer.

So "the holidays" is not one set of dates. Your customers, your support team, your engineers and anyone working for you from another country can each be off on different days. Holiday support coverage is the plan for who answers on each of those days, and for what happens to the tickets nobody can close until the new year.

Holiday support coverage starts with a calendar per group

Before anyone is asked to work a shift, write the dates down. One row per group: the countries your customers are in, your first line (the team that answers tickets first), the people the first line escalates to, and any outside team. For each date, mark who is working, who is reachable, and who is off.

The step is easy to skip if each team assumes its own calendar is everyone's. In a business-to-business queue a client can be back at work on a day your engineer has off, and the ticket arrives either way.

A staffed queue still needs the people it escalates to

A holiday plan that covers only the first line gets the visible part right: someone is on shift, tickets get a reply. The failure sits one step behind it. A ticket the first line cannot close goes to someone else: an engineer for a fault, a person who can approve a refund or release a payment, the account manager who looks after that client, for anything in the contract. If that person is off, the ticket is answered and then waits.

In the support we run for business clients, the work is checking cases and transactions in the client's systems and handling incidents, and the first line can only close what it is allowed to decide. Everything else is an escalation, and over the holidays an escalation needs a name.

incident.io's guide to on-call holiday coverage across time zones has it on its holiday on-call readiness checklist: every shift slot for the full holiday block has a named primary and a named secondary, which means a main person and a backup, by name. That checklist is written for engineers on call; the same rule fits every escalation path behind support. A shared inbox is not a name, and neither is "the engineering team".

Escalation pathA ticket that goes thereNamed for each holiday date
EngineeringA fault that stops a customer workingA main person and a backup, with a way to reach them on a holiday
Payments and refundsA stuck transaction, a refund to approveA person allowed to approve, and a stand-in
Account managerA question about access, the contract or the priceThe account manager or a stand-in, and the date they are back

Decide what waits, and say until when

Not every ticket needs a person on 25 December. The plan sorts them in advance: what is escalated on any day, because the customer cannot work until it is fixed, and what waits until a named date.

In a December 2024 post on how it was running its own business-to-business support over that holiday season, the company Plain said it would keep its response-time commitments and a way to escalate its most urgent issues, and that it was trying to be fine with slower replies on everything else. It planned to send customers its holiday support hours and response times in advance, by email and Slack, with guidance on how to escalate an urgent issue.

A waiting ticket with a date is a plan. Without a date, the customer has to keep asking.

If the holidays also bring more tickets than usual, that is a capacity question rather than a coverage one, and our article on support ticket spikes deals with it.

Freeze changes before the break

Fewer people at work means fewer people to fix what breaks, so the holidays are the wrong time to release new versions of your product. PagerDuty's engineering blog says its own teams take their holiday change freeze seriously, with no releases while it lasts. incident.io's guide also recommends defining a deployment freeze window, a set of days when non-essential deployments and maintenance are paused.

For support, a freeze means the first line answers questions about the same product during the break as before the break.

If you are starting late

incident.io's guide advises planning the holiday on-call schedule at least six to eight weeks ahead, and the same lead time is a fair target for the escalation list. For a break that starts on 24 December, six weeks ahead was 12 November. PagerDuty's teams meet in early November to review who is on call when, check their written incident procedures and share the dates they will be away.

If those dates have passed, the short version still fits before the break:

  1. The calendar. Every group, every date: who is working and who is reachable.
  2. A name for each escalation path on each date. A main person and a backup, with a way to reach them that works on a holiday.
  3. What waits. Which tickets wait, and until which date.
  4. The message to customers. Holiday hours, reply times, and how to escalate something urgent.
  5. The freeze. The first and the last day with no releases.

When the first line is an outside team

An outside team can cover every holiday date. What it cannot do is approve what only your people may approve, so its holiday plan is only as good as the escalation list you give it.

Agree three things before the break: the names for each path and each date, what the team may tell a customer whose ticket waits, and the date both sides go through what waited. For its own support, Plain planned a version of that last step: once the holidays ended, it would review support load and response times to plan the next holiday season better.

How IMMIDO fits

We run 24/7 first-line support inside your own tools, as a fixed monthly team, not per ticket. The work is checking cases and transactions and handling incidents in Jira and your own systems, and what the first line cannot decide goes to your people. That is why, in December, the escalation list matters to us as much as the shift plan. How we run the first line is described on our technical support page, and how to staff the clock in general is in our guide to 24/7 support coverage.

If your holiday plan covers the first line but not the people behind it, book a call and we will go through your escalation list with you before the break.

Sources: GOV.UK, UK bank holidays (Christmas Day, Boxing Day substitute day, paid leave) · Service-Public, Jours fériés et ponts dans le secteur privé (1 May and its exception, the other public holidays) · incident.io, On-call holiday coverage across timezones (six to eight weeks, named primary and secondary, deployment freeze window) · PagerDuty, Holiday Readiness Guide for On-Call (early November, change freeze) · Plain, How we're managing B2B support over the holidays (December 2024; holiday support hours, escalation, the review afterwards).