The Menu Nobody Rehearsed: Auditing Your Phone Tree Before the 2026 Christmas Break

Most UK businesses have a phone menu that nobody has listened to in full since the day it was commissioned. It was built carefully, recorded politely and signed off by someone who has since moved on. It now sits between your customers and your staff, quietly doing a job that no one supervises.

For fifty weeks of the year this passes unnoticed. The six weeks around Christmas are different. Offices empty, cover thins out, and the number of people ringing to ask a simple question rises rather than falls. If the menu is out of step with reality, December is when it becomes visible — usually in the form of a complaint in the second week of January, by which time the caller has already formed a view.

Why the menu drifts without anyone noticing

An auto-attendant is not a static object. It is a set of routing rules sitting on top of a directory that changes constantly. Every leaver, every extension swap, every new starter and every reorganised team alters the underlying structure, while the menu above it stays exactly as it was.

The failure modes are rarely dramatic. They are the small, cumulative kind:

• Option 2 still points to a hunt group that was dismantled when two departments merged.
• Option 4 reaches a voicemail box that is technically monitored, in the sense that someone occasionally remembers to check it.
• A recorded prompt announces opening hours that were correct in a previous year, or names a colleague who left in the spring.
• A time-of-day rule installed in haste last December was never reverted, so calls after 17:30 have been going straight to an unattended line ever since.
• Holiday schedules were entered for one year only and have quietly lapsed.

None of these produce an error message. The system behaves exactly as configured. That is the difficulty: a misconfigured menu is indistinguishable from a correct one until a customer runs into it.

Walk the tree as a stranger would

The most useful audit technique is also the simplest. Pick up a mobile phone — not a desk handset, which may bypass external routing rules — and call your own main number. Work through every branch. Time how long each level takes. Note where you are asked to repeat yourself, where the options run out, and where the call terminates.

Then do it again outside working hours, and once more from a different network. Internal testing flatters a phone system, because internal calls often avoid the very routing logic your customers meet.

It is worth asking a colleague who does not normally answer the phones to run the same exercise. They will hear the menu fresh, and they will notice the assumptions an insider has stopped seeing.

The seasonal layer: closures, cover and the days in between

The 2026 Christmas period is unusually awkward in calendar terms. Christmas Day falls on Friday 25 December, with Boxing Day on Saturday 26 and the substitute bank holiday on Monday 28. New Year's Day follows on Friday 1 January 2027.

That arrangement creates a scattering of working days when some of your staff are in, some are not, and the phones ring regardless. A menu that offers a binary choice between normal service and full closure will misrepresent the business for most of that fortnight.

Before the break, confirm four things:

1. The holiday schedule carries the correct dates for 2026 and 2027. Annual schedules that recur annually are a frequent source of error, particularly where a system was configured for a single year and never revisited.
2. The closure message names the date you actually reopen. "We reopen in the New Year" is less helpful than "We reopen on Monday 4 January 2027." If that date changes, the prompt must change with it.
3. The between-Christmas routing reflects real cover. If only two people are working on 30 December, the menu should not present the same options as a normal Wednesday.
4. Out-of-hours callers have somewhere to land. An emergency line, a monitored mailbox with an accurate greeting, or a clear instruction to call back — but not silence, and not a loop back to the start of the menu.

Who can change it, and when

A phone menu that nobody can edit is a phone menu nobody will fix. Before December, confirm who holds administrative access to the platform, who can record and upload a new prompt, and what the approval route is for changes.

Equally, be wary of last-minute edits. Telephony changes made on 23 December, with no opportunity to test, are a reliable way of converting a small problem into a large one. Make the changes in the first week of December, test them externally, and record what the previous configuration looked like so it can be restored if needed.

Diarise the return now

Holiday routing is easier to apply than to remove. Every year, a number of businesses discover in mid-January that their closure message is still playing, or that their after-hours rule is still diverting calls to a mobile number that has since been switched off.

Put the reversal in the diary for the first working day of 2027, alongside the prompt removal and a second full walk-through of the menu. Treat it as a task with an owner, not an intention.

The audit in summary

An auto-attendant audit takes an afternoon. It requires a mobile phone, a notepad, someone with administrative access and the willingness to hear your own business as a customer hears it. Done in late November, it protects the busiest fortnight of the year. Done in January, it explains a complaint you would rather not have received.