Customer Support Coverage During Public Holidays: Rotas and Follow-the-Sun

On a public holiday, some customers vanish and others appear. A business customer in the same country is probably closed too. A consumer at home with a free day may finally get round to the problem they have been putting off. A customer in another country is having a completely normal Tuesday. Your support team, meanwhile, is entitled to its own day off. Planning holiday coverage means balancing those facts without guessing.

Step one: forecast holiday demand from your own history

Holiday demand varies too much by business to rely on rules of thumb. Some companies see volume drop sharply on national holidays; others see it rise. The only trustworthy guide is your own data.

• Pull ticket, chat and call volumes for the same holidays in previous years, by hour.
• Split volume by customer country or region where you can, since customers in other countries will not be on holiday.
• Look at the day after the holiday too. Work that was not raised on the holiday often arrives the next morning.
• Note anything unusual about past years, such as a product launch or outage, that would distort the comparison.

If you have no history, start with a conservative estimate, staff a little above it, and record what happens so next year is easier.

A worked example: staffing a holiday shift

Suppose your history suggests that on a particular national holiday you will receive about 30 contacts an hour between 9:00 and 17:00 local time, and that an agent can handle around 6 contacts an hour once breaks and follow-up work are taken into account. These figures are illustrative; use your own.

The basic staffing need is 30 / 6 = 5 agents an hour. Over an eight-hour window that is 5 x 8 = 40 agent-hours. If shifts are eight hours, you need five people, plus some allowance for sickness or a busy spell. Many teams add a buffer of around one person in five for this, which would make six.

Now compare a normal weekday with 60 contacts an hour. That needs 60 / 6 = 10 agents an hour, or 80 agent-hours. The holiday shift therefore needs about half the usual staffing, not none, and not the full team. The day after, if you expect a backlog of perhaps 100 extra contacts, that is 100 / 6, or roughly 17 more agent-hours, which is about two extra people for a full shift.

Step two: decide how cover will be provided

Holiday rotas

The most common approach is a rota in which a minority of the team works the holiday and takes time off on another day, or is paid a premium, depending on the employment terms. A rota is only fair if it is visible and balanced over time. Keep a running record of who worked which holidays, and rotate the most valued days, such as Christmas Day or a major national holiday, so the same people do not always draw them.

Ask for volunteers first. Some people prefer to work a holiday that does not matter much to them and take a day that does. People who observe religious holidays outside the national calendar may be glad to swap.

Follow-the-sun

If you have support teams in several regions, you can route contacts to whichever team is in its working day. A typical arrangement uses three hubs roughly eight hours apart, for example in Australia, Ireland and Canada. On a holiday in one country, the other hubs can absorb some of the work, but only if they have the product knowledge, system access and language skills to do so.

Follow-the-sun works well for holidays that are national. It is less helpful for holidays shared across many regions, such as 25 December or 1 January, when most of your hubs are off at the same time. For those days, you still need a rota somewhere.

The team overlap tool helps you see which hubs are working on which days. Compare it with country pages such as public holidays in Ireland and public holidays in Australia, which also notes where states differ.

Reduced service

Sometimes the right answer is to offer less on a holiday: email only, no phone line, or a limited priority queue for urgent issues. That is a legitimate choice if you are honest about it.

Step three: set and publish expectations

Customers are generally more tolerant of reduced holiday service when they know about it in advance. Tell them:

• which channels are open, and at what hours, in their time zone;
• what counts as urgent and how to reach help in an emergency;
• whether response-time commitments are paused or measured in working days.

If your service agreements define response times in business days, check how they treat public holidays and in which country's calendar. "Two business days" for a customer in the United States and a support team in Ireland can mean different things in the week of Thanksgiving or St Patrick's Day. The add business days tool shows where a deadline lands under a specific calendar.

Looking after the people who cover

Holiday shifts tend to be quieter in some ways and harder in others. There are fewer colleagues to ask, managers are often away, and escalation paths can be thinner. A few steps help:

• Name an on-call lead or escalation contact for each holiday shift.
• Make sure holiday staff have the access they need before the day, not on it.
• Compensate holiday work as the contract and local rules require, and record it accurately.
• Do not schedule the same person on consecutive holidays unless they have asked to be.

Holiday coverage checklist

1. List next year's holidays for every country where you have customers or support staff.
2. Forecast holiday and day-after volume from your own history.
3. Convert the forecast into agent-hours and people per shift, with a buffer.
4. Choose rota, follow-the-sun, reduced service, or a mix, for each holiday.
5. Publish holiday hours to customers in their time zone.
6. Track who worked which holiday so the rota stays fair from year to year.