Picture it. It’s the evening of 23 December. A customer who has been waiting on an order sends your business a message: Is it arriving before Christmas?

Your manager is on the road. Your accountant is offline. The one person who knows how delivery exceptions work has started her leave. The message sits unread. The next morning the customer sends another, less polite. By the time anyone replies, they’ve already ordered from someone else.

Nothing dramatic went wrong. No system failed. The business simply had no plan for holiday customer service, and nobody noticed until a customer paid the price.

This is one of the most predictable problems in the year, and it is solved in November, not December. Black Friday falls on 27 November and starts the busy trading period. The festive close follows within weeks. This article gives you a plan you can build over the next few weeks and test before your team leaves.

What actually breaks over the holidays

When teams go on leave, three things usually fail, and they are different problems.

Silence. Messages arrive and nobody sees them. The customer doesn’t know whether you’re closed, busy or ignoring them.

Knowledge that lives in one head. The answer to the customer’s question exists, but only one person knows it, and she is away. This is the same hidden work we describe in our article on why automation projects fail: the judgement and shortcuts nobody has written down.

Stalled decisions. A refund, a discount or a supplier payment needs an approval, and the approver is on leave or has no signal. The request waits, and so does the customer.

Different problems need different fixes, which is why the plan below has four layers rather than one tool.

Build “holiday mode” in four layers

1. Acknowledge every message at once

The first goal is not to answer everything. It is to make sure nobody is met with silence.

Most business messaging tools can do this automatically. The WhatsApp Business app, for example, offers automated greeting and away messages, quick replies and labels. Email has out-of-office replies. Set them up properly, because most automatic replies are written badly.

A weak one says: We are currently closed.

A useful one says what the customer needs to know: Thanks for your message. Our team is on leave from 22 December to 4 January. We’ll reply to every message when we return, starting on 5 January. For urgent delivery problems, call [number] between 10am and 2pm on 27 and 30 December.

A good acknowledgement confirms the message was received, says when a person will respond, and gives a route for genuine emergencies.

2. Prepare answers to the questions you already know are coming

Most customer messages repeat. Open your last year’s December messages and list the twenty questions that came up most: delivery dates, opening hours, prices, payment problems, order status, refund rules.

Write one approved answer for each, in plain words, with the correct details. These become saved replies anyone can send, and they are the source material for any AI assistant you use.

This is where it helps to be honest about what AI adds. For the ten questions with fixed answers, saved replies are enough, and AI would add nothing. AI becomes useful for the long tail: the same question phrased a dozen different ways, messages that mix two questions, or a message that needs a draft reply from your approved information. It can also do something simple and valuable: read the overnight messages and prepare a short morning list, sorted by urgency, for whoever is on call.

If you use an assistant to answer customers, give it strict rules:

• It answers only from your approved information.
• If the answer isn’t there, it says a person will follow up, and flags the message.
• It never invents prices, delivery dates, discounts or refund decisions.
• It hands over to a person for complaints, disputes and anything involving money going out.

If you’re weighing whether to hand more than replies to an AI, our article on AI agents vs traditional automation explains the difference in what each can do on its own.

3. Keep decisions moving while the boss is away

Customers can wait for an answer. They don’t like waiting for a decision.

List the decisions that normally need someone senior: refunds, discounts, replacements, supplier payments, exceptions to policy. For each one, decide in advance:

• Who can approve it while you’re away, and who is the backup if that person doesn’t respond.
• What limit applies. A named person can approve refunds up to a set amount. Anything above that waits, with the customer told so.
• How the approval happens. A request that goes to a group chat gets lost. A simple approval flow, where the request goes to one named person with the details attached, doesn’t. If your team uses Microsoft 365, approvals like this can be set up inside the tools you already have, and our Microsoft 365 and Power Apps solutions work covers that.

Write the rules on a single page, called an approval card, and share it with everyone who might need it.

4. Hand over the work nobody wrote down

For each process that matters over the holiday (order fulfilment, payments, customer follow-up), the person who runs it writes a one-page handover:

• Where things stand now, and what is waiting
• What is likely to happen in the next two weeks
• Who to contact for what, with phone numbers
• The two or three things that go wrong most often, and how to fix them
• What not to do

Keep passwords out of the handover. Give the backup person proper access through your normal system for shared access, so they never need to ask for a login on holiday.

What should stay with a person

Automation covers the routine. Keep a named person for what it shouldn’t touch: complaints and disputes, refunds above the limit, any message mentioning safety or legal action, and your most important customers.

That doesn’t mean someone is working all through the holiday. A realistic arrangement is a short check twice a day by whoever is on call, working from the morning list and the flagged messages. Agree it in advance, and give that person a day off in return.

A five-week plan

• Week of 9 November: List last year’s twenty most common questions and the decisions that need approval.
• Week of 16 November: Write the approved answers, set up the auto-replies, and fill in the approval card.
• Week of 23 November: Test everything (see below). Black Friday on the 27th will give you real traffic to learn from.
• Week of 30 November: Fix the gaps the test showed up, and write the handover notes.
• Week of 7 December: Brief the whole team on who covers what. Then stop changing things.

How to test it before you rely on it

An untested holiday plan is a guess. Spend an hour on it:

• Message your business at an odd hour, such as 9pm on a Friday, and check what you receive and when.
• Ask a colleague to play a customer and send a question that isn’t on your list. What happens?
• Send a refund request above the limit, and follow it through. Does it reach the right person? Does the customer get told what to expect?
• Check what happens if the phone running your messages is switched off or loses its connection.

Every gap you find now is one a customer won’t find in December.

Frequently asked questions

Plan the cover now, enjoy the break later

A quiet December isn’t the result of luck. It comes from deciding in November who answers, who approves and what gets handed over. If you’d like help setting up the automation for your own business, from auto-replies to AI-assisted answers to approval flows, our AI Automation service covers that work, and you can contact us to talk it through before the rush begins.

If you’re also deciding what else is worth automating next year, our guide to the 10 business processes every growing company should automate first is a good place to start.