Creating Holiday Auto Replies in Autotask

MSP Workflow Automation for Business Hours and Holidays

One of the quieter wins in MSP workflow automation isn't AI triage or smart dispatch — it's making sure clients get the right message the moment they submit a ticket outside of business hours or during a holiday. Done right, it sets expectations, reduces follow-up calls, and keeps your help desk running smoothly even when your team isn't at their desks.

Autotask PSA has everything you need to build this out properly: Holiday Sets, Internal Locations, and Workflow Rules (WFRs). Set these up once, maintain them annually, and your auto-responder system runs on autopilot — a small but meaningful piece of your overall Autotask automation software stack.

Here's the full setup, plus context on how it fits into a broader helpdesk automation strategy.

Why Holiday Auto-Replies Matter for MSP Help Desk Efficiency

When a client emails your help desk at 6pm on Christmas Eve and hears nothing back, they don't assume you're closed — they assume their ticket got lost. That generates a follow-up call, sometimes an angry one, and puts your dispatcher in a reactive position first thing when the team returns.

A well-configured auto-reply does three things that directly support MSP help desk efficiency:

• Sets accurate expectations — clients know their ticket was received and when to expect a response.
• Communicates holiday rates or on-call availability — no surprises on the invoice, no confusion about emergency coverage.
• Reduces inbound call volume — clients who get a clear auto-reply don't call to check in. That protects your on-call tech from unnecessary interruptions.

This is exactly the kind of low-effort, high-impact configuration that separates MSPs running a tight operation from those still putting out fires manually.

Step 1: Configure Your Holiday Sets

Holiday Sets are the foundation. Autotask won't know which days are holidays unless you define them here, and your Workflow Rules won't trigger correctly without accurate holiday data.

1. Go to (A) → Admin → Account Settings & Users
2. Navigate to the Resources/Users (HR) sub-page
3. Click Holiday Sets
4. Edit Company Holidays
5. Click the Holidays tab
6. Add all company holidays for the next 12 months
7. Click Save & Close

Pro tip: Don't rely on remembering to update this every year. Set up a recurring Autotask ticket — or use a Rocketship automation rule — that fires once every 12 months to remind your admin to refresh the holiday list. It takes two minutes to set up and saves you from a December where your holiday WFRs are firing based on last year's dates.

Step 2: Link Your Holiday Set to an Internal Location

Holiday Sets only do their job when they're correctly linked to an Internal Location. If you have multiple offices or service teams observing different holidays, this step becomes especially important — each location can have its own Holiday Set, which means your Workflow Rules fire correctly regardless of which team is handling the ticket.

Still in the Account Settings & Users page:

1. Go to Your Organization
2. Click Internal Locations
3. Open your default location (usually named "Headquarters")
4. Confirm the correct Holiday Set is selected
5. Click Save & Close

By default, Autotask links the default Holiday Set to your default Internal Location automatically — but it's worth verifying this is still accurate, especially if your configuration has changed over time.

Step 3: Set Up Your Workflow Rules for Inside and Outside Business Hours

This is where the MSP dispatch automation logic lives. You need two separate Workflow Rules: one for tickets that arrive inside business hours, and one for tickets that arrive outside business hours (including holidays). Most MSPs already have a default auto-responder WFR — you'll duplicate it and configure each copy for its respective time window.

Auto Responder — Inside Business Hours

In your existing auto-responder WFR (or a copy of it renamed "Auto Responder – Inside Business Hours"), enable the Time Sensitive feature and set the condition to fire during business hours. This is your standard acknowledgment: ticket received, expected response time, contact information.

Make sure this WFR is set to Inside Business Hours in the time condition, with your Holiday Set factored in so it doesn't fire on holidays.

Auto Responder — Outside Business Hours

Create a copy of your inside-hours WFR and rename it "Auto Responder – Outside Business Hours." Update the time condition to Outside Business Hours.

This WFR needs its own Notification Template — one that sets different expectations. A strong outside-hours template typically covers:

• Confirmation that the ticket was received
• Your normal response time for next business day
• Whether you have on-call coverage and how to reach it for emergencies
• Holiday-specific language if applicable (e.g., "We are currently observing a company holiday and will respond on [date]")
• Any after-hours rate information if emergency support carries different billing

This is one of the most underused communication tools in Autotask. A clear outside-hours template dramatically reduces the "just checking if you got my ticket" calls that create unnecessary MSP ticket backlog the next morning.

How This Fits Into a Broader Autotask AI Automation Strategy

Holiday auto-replies are a form of Autotask automation software — lightweight, rule-based, and highly reliable. But they're also a useful illustration of how MSP workflow automation works in layers:

• Layer 1: Basic WFR automation — Holiday auto-replies, SLA notifications, ticket acknowledgments. Rules-based, always-on, no AI needed.
• Layer 2: Intelligent triage and routing — AI ticket automation for MSPs that classifies incoming tickets, scores priority against SLA tiers, and routes to the right tech without dispatcher intervention.
• Layer 3: Predictive operations — MSP AI automation tools that identify patterns in ticket volume, flag potential SLA breaches before they happen, and recommend staffing adjustments.

Holiday auto-replies live at Layer 1, and they're non-negotiable — if your basic WFR configuration isn't solid, the higher layers of AI Autotask automation won't perform reliably either. Clean configuration at the foundation is what makes AI + Autotask integration trustworthy.

Common Mistakes to Avoid

A few things that break this setup in practice:

• Forgetting to update Holiday Sets annually — Last year's holidays won't match this year's dates. Set a recurring reminder or automation rule to handle this.
• Using the same Notification Template for both WFRs — Inside and outside business hours should deliver different messages. Clients expect different things depending on when they reach out.
• Not testing after setup — Send a test ticket outside business hours before you rely on this in production. WFR conditions are easy to misconfigure, and you don't want to find out during an actual holiday.
• Skipping the on-call details — If you have emergency coverage, your outside-hours template needs to say so explicitly. Clients in a genuine P1 situation need to know how to escalate, not just that you're closed.

The Bottom Line

Holiday auto-replies aren't glamorous, but they're a core part of MSP help desk efficiency — and they're a good example of how thoughtful Autotask PSA configuration reduces manual work and client friction simultaneously. Get the Holiday Sets, Internal Locations, and Workflow Rules right, and this runs entirely on its own.

If you're ready to go beyond WFR-level automation and add AI ticket triage, smart dispatch, and real-time SLA management to your Autotask setup, schedule a demo with Rocketship to see how it all fits together.