Your automations don't know you're closed on Thanksgiving

The Friday after Thanksgiving

Here's a composite small business on the Friday after Thanksgiving. The office closed Thursday and most people took Friday too.

On Thursday morning, the invoicing tool sent eleven overdue reminders, each saying "please contact us today." Nobody was there to take the calls. The help desk auto-reply told customers to expect an answer "within one business day," and the help desk counted Thursday as one. By Friday afternoon, forty tickets showed as overdue. The CRM created follow-up tasks due on Thursday for two salespeople who were at their families' houses. And a weekly report landed in an inbox that won't be opened until Monday, by which point a newer one will be on top.

None of these tools is broken. Each tool has its own idea of what a day is. None of them asked you.

This note is a walk through the four settings that decide what happens on a closed day. Do it once before November 26, and you'll be ready for December too.

1. Is there a holiday calendar, and which one?

Start with a list of every tool that does something on a schedule or counts time: the help desk, the CRM, the invoicing or accounting tool, the email marketing tool, scheduling and booking, any workflow automation platform, and anything a developer set up with a scheduled job.

For each, find out whether it has a business-hours or holiday setting at all. Many help desks and scheduling tools do. Many simple automations don't. They only know the date.

Don't forget the automations that live inside other automations. A form submission that creates a task, which triggers an email, which waits three days and creates another task, is four schedules wearing one name. Follow one chain from start to finish and note every point where time is counted.

Where a holiday calendar exists, check what's in it. It may be a national holiday list the tool picked for you, not your actual closures. It probably doesn't know you close the Friday after Thanksgiving, or between Christmas and New Year. And because each tool keeps its own calendar, you'll need to enter the same closures in each one.

2. Days or business days?

Next, look at every step that says "wait." A follow-up three days after a quote. A reminder seven days after an invoice is due. A task due two days after a ticket comes in.

For each, find out whether it counts calendar days or business days. Calendar days run straight through holidays, so a three-day follow-up sent Tuesday lands on Friday whether anyone's there or not. Business days usually skip weekends, but only skip holidays if the tool knows about them, which takes you back to setting one.

Watch the follow-ups that run in sequence, too. If step one is held for the holiday but step two still counts from the original date, the customer can get two messages a day apart, or the second before the first. Check that delays count from when the previous message actually went out.

Neither is wrong. A payment reminder can reasonably count calendar days. A promise to reply should count working days. The point is to choose, rather than inherit whatever the template used.

3. What happens to anything due on a closed day?

This is the setting most tools don't ask about. When something falls on a closed day, there are three sensible choices.

Hold it until the next working day. Good for anything that asks the customer to do something urgent or contact you. A reminder that says "call us today" should never go out on a day you can't answer.

Send it anyway. Fine for information that doesn't need a reply, such as a shipping update or a receipt.

Skip it. Right for anything that only makes sense on the day, such as a daily summary.

Check the time zone while you're there. A message scheduled for "9 AM" may mean 9 AM where the tool's server is, not where your customers are. If you dealt with the clock change on November 1, you'll have seen how quickly time settings stop being obvious.

4. What does the auto-reply promise, and who's covering?

Finally, read every message that goes out on its own while you're closed: the help desk auto-reply, the out-of-office on shared inboxes, the chat widget's offline message, any AI assistant's answer to "when will someone get back to me?"

Each should say when you're closed and when you'll be back, in plain words, with a real date. "We're closed Thursday and Friday for Thanksgiving and will reply by Monday, November 30" beats "within one business day" every time. If something can't wait, say what to do.

Then make sure the promise matches the clock. If your help desk measures response times, pause or adjust the timer for closed days, or your reports will show a crisis that didn't happen. Our note on acknowledging before the SLA clock starts goes deeper on that.

If someone is covering, name them, and make sure the urgent path reaches their phone rather than a shared inbox nobody checks.

Remember the people side as well. If a salesperson's tasks will be moved to Monday, tell them, so the pile isn't a surprise.

Put this into practice

This week, make the list of tools, then walk each one through the four settings: calendar, day counting, closed-day rule, and the promise in the auto-reply. Enter Thanksgiving, the day after if you close, and your December closures in each calendar now.

Then test it. Schedule a harmless internal reminder for Thanksgiving Day and see whether it holds, sends or skips. Fix what surprises you. Keep the list somewhere central, because the same walk is needed before every long weekend.

After the holiday, spend fifteen minutes looking at what went out while you were closed. Read the sent folder, the help desk's overnight activity and any task lists. Anything that still surprised you is a setting you missed, and December is close enough to fix it before Christmas.

If you'd rather have one calendar that every tool reads from, that's very doable, and it's the kind of business process automation we set up for teams. Talk to us.

Related work: WorkStep.