The shop shuts on Friday for a long weekend. The sign goes on the door, the voicemail gets updated if someone remembers, and the website still says "Open Monday to Saturday, 9am to 5pm". On Monday a customer drives over, finds the shutters down and leaves a one-star review from the car park.
Bank holidays and planned closures cause a particular kind of mess. Not because customers are unreasonable, but because the information is correct in one place and wrong in four others. Messages pile up with nobody promising anything, and Tuesday morning starts with forty emails and a queue of people who feel ignored.
Handling holiday closure enquiries well is mostly a matter of preparation. It takes an hour or two, and most of it can be reused every year.
Where customers look for your hours
The first failure is inconsistency. People check whichever source is nearest, and they believe it.
| Place | Who checks it | Easy to forget? |
|---|---|---|
| Website header or footer | Anyone planning a visit or call | Often, because it is hard-coded |
| Contact page | People about to get in touch | Sometimes |
| Map and business listings | People searching nearby | Very often |
| Website assistant's knowledge | Visitors asking "are you open Monday?" | Very often, because it answers from old content |
| Form confirmation and email auto-reply | People who have already sent something | Often |
| Voicemail greeting | Callers | Sometimes |
| Social media profiles | Existing customers | Sometimes |
The website assistant row is the one that catches people out. If it learned your hours from a page crawl three months ago, it will cheerfully tell a visitor you are open on the bank holiday. Update the content it answers from, or add a dated question and answer pair, and check the answer yourself. There is a general routine for this in how to keep your chatbot's knowledge up to date.
A two-week checklist
This is the order that works for most small businesses. Copy it into your calendar for every closure.
- Two weeks before: decide the exact dates and times, including whether the day before closes early. Decide who, if anyone, handles emergencies.
- Ten days before: update your business listings, since those can take time to show.
- A week before: add holiday hours to the website header, contact page and your assistant's knowledge. Post it on social media.
- A week before: tell regular customers with active orders or bookings directly.
- Two days before: write the closure auto-reply and voicemail greeting. Schedule them if your tools allow.
- The day before: test it. Ask your website assistant "are you open on Monday?" in a couple of phrasings, and send yourself a test enquiry.
- Reopening morning: remove or date-limit the holiday content before anything else.
The last step is the one people skip. A "we are closed" message left running into a normal Tuesday costs more enquiries than the holiday did.
Closure messages that actually help
Most closure messages say "We are closed for the bank holiday. Thank you for your patience." That tells the customer almost nothing they can act on.
A useful one answers what the customer is going to wonder next: when are you back, what if it is urgent, and when will someone reply to this. For example:
"We're closed from Friday 28 August and back at 8am on Tuesday 1 September. If you smell gas, leave the property and call the gas emergency line now. Anything else, leave your details and we'll reply by 12pm on Tuesday."
Swap the emergency line for whatever fits your trade. A clinic points to NHS 111 or emergency services for anything urgent or clinical. An online shop points to order tracking. If you struggle with the tone, the AI reply generator can draft a few versions for you to edit.
What the assistant should do while you are away
A closed business still has a website that is open. Visitors arrive over a long weekend with the same questions as any other day, and many of them have more time to look.
Visitor: Can I drop my bike in for a service on Monday?
Assistant: We're closed on Monday for the bank holiday and open again from 9am on Tuesday. I can take your details and what the bike needs, and the workshop will confirm a drop-off time on Tuesday morning. What make of bike is it, and what's the problem?
Visitor: Road bike, gears are slipping and I want a general service.
Assistant: Thanks. Could I take your name, phone number and email? I'll note that it's a road bike with slipping gears and a general service request.
The visitor leaves knowing the date, knowing what happens next and not needing to send a second message. The workshop starts Tuesday with a request that already has the job described. Note what the assistant does not do: it does not promise a slot, because it cannot see the workshop diary. It captures the request, and a person confirms.
For anything that needs a person during the closure, use the capture rather than the transfer. Live handover only works when someone is marked on duty, and on a bank holiday that should usually be nobody.
Making the first day back calm
The difference between a chaotic Tuesday and a manageable one is how much detail arrives with each enquiry. A form that says "please call me" needs a phone call to find out what the person wants. A captured conversation that says "road bike, slipping gears, service, prefers mornings" needs a two-minute reply.
Sort the captured enquiries before you open anything else: urgent issues from existing customers first, then new work, then general questions. The routine in clearing the Monday morning enquiry backlog applies just as well to the day after a bank holiday.
Before the next closure
Look up the next bank holiday or planned closure and put the checklist above into your calendar today, with names against each step. Write your closure message now while nobody is in a hurry, and store it somewhere you will find it next time.
If your website assistant answers questions about opening hours, open it and ask it about the next closure date. If the answer is wrong, fix the content this week rather than the day before. The docs cover adding and editing question and answer pairs.