How to Set Up Business Hours and Out-of-Hours Auto-Replies

Your customers don't operate on your schedule. They have questions at midnight, problems on weekends, and urgent requests during lunch. Your team, meanwhile, works set hours and deserves to actually use them.

Setting up business hours and out-of-hours auto-replies in your helpdesk isn't just filling a configuration checkbox. It's setting clear expectations for customers, protecting agents from burnout, and making sure your SLA tracking reflects reality instead of penalising your team for tickets that arrived while they slept.

Why business hours matter in your helpdesk

Accurate SLA tracking

Here's the problem most helpdesks have: if your SLA promises a first response within 4 business hours, the clock should only tick during business hours. A ticket submitted at 5 PM on Friday should not breach its SLA by Saturday morning. Without business hours configured, your helpdesk treats every hour the same — 3 AM on Sunday counts the same as 10 AM on Tuesday.

This distorts everything. Your SLA reports become meaningless. Agents look like they're missing targets when in reality the ticket arrived at 2 AM. Your metrics lie, and you can't trust them.

Once you set business hours, the math works. A ticket created at 11 PM that gets a response at 9:15 AM the next morning shows as a 15-minute response time, not a 10-hour one. Suddenly, you can tell whether your team is actually hitting targets or whether your schedule is the problem.

Fair agent workload

Agents deserve a clear definition of when they're supposed to be available. When your helpdesk has business hours configured, overnight tickets don't count against the morning agent's response time from the moment they were created. The clock starts when the working day begins. This also aligns with UK working time rules — your agents can't be expected to respond to tickets they don't know about.

Without this, you create a perverse incentive: the agent who checks Slack at 6:30 AM looks more responsive than one who takes a proper lunch break. Neither is the goal.

Customer clarity

Customers who know your hours can plan accordingly. Those who contact you at 2 AM receive an immediate acknowledgement and a clear timeline for when they will hear back. This is vastly better than silence. No uncertainty. No duplicate messages. No assumption that you're ignoring them.

How to set business hours

Define your schedules

Start with what actually applies to your team:

Standard hours — Monday to Friday, 9 AM to 6 PM (or whatever your team actually works)
Extended hours — If you offer weekend support, define those hours separately
Holiday schedule — Public holidays and company closures when your team is genuinely unavailable
Regional variations — If you have teams in multiple time zones, each gets its own schedule

Most helpdesks let you create named schedules (like "Standard UK Hours" or "US Central Time") and assign them to different teams, channels, or customer tiers. The key: configure what's true, not what you'd like to be true.

Assign schedules at the right level

You typically have options:

Global default — Applies to all tickets unless overridden
Per team — Different teams can work different hours
Per channel — You might offer extended live chat support but standard hours on email, or add SMS for emergency contact
Per customer tier — Premium customers might get 24/7 support while free-tier customers get business hours only

For most small businesses, a global default with overrides for specific high-priority channels is the practical choice.

Time zone handling

If your customers span multiple time zones, you have three options:

Option 1: Your time zone. All SLAs are calculated based on your team's local time. Simple to configure, and customers are clearly told your hours in their timezone.

Option 2: Customer's time zone. SLAs are based on the customer's local time. More customer-friendly, but complex to configure and nearly impossible to report on.

Option 3: Follow-the-sun. Multiple teams in different time zones provide coverage across a wider window. Tickets route to whichever team is currently on shift.

For most small teams, Option 1 with clear, transparent communication is the only sensible choice.

Setting up out-of-hours auto-replies that actually work

When a customer contacts you outside business hours, silence is the worst response you can give. An auto-reply fills the gap with acknowledgement and clear expectations.

What to include

Acknowledgement. "Thank you for reaching out" or "We've received your message." Simple, but it matters.

Your hours. "Our team is available Monday to Friday, 9 AM to 6 PM GMT." Be specific.

Timeline. "We will respond when we return" or "You can expect a reply by 9:30 AM tomorrow." Manage expectations.

Self-service option. Point to resources. "In the meantime, our help centre at [link] may have the answer." (Most customers won't use it, but some will, which saves you a ticket.)

Urgency path, if you have one. "If this is urgent, contact [phone/email/on-call method]." Be honest — if you don't have emergency cover, don't mention it.

Keep it brief. Two to four sentences. A novel-length auto-reply signals disorganisation.

Example auto-replies

Basic version:

Thanks for your message. Our support team is available Monday to Friday, 9 AM to 6 PM GMT, and we will respond as soon as we're online. Check our help centre at [link] if you need immediate help.

With urgency path:

We've received your message. Our team is currently offline and will respond during business hours (Monday–Friday, 9 AM–6 PM). If this is an emergency, call our on-call team at [number].

Weekend-specific:

Thanks for reaching out over the weekend. Our team returns Monday at 9 AM and will get to your message first thing. For immediate help, try our help centre at [link].

Channel-specific approach

Different channels need different tones:

Email — Can be slightly longer; customers expect async communication
Live chat — Short and direct; the customer is waiting on screen
Social messaging — Conversational and brief; match the platform's tone
Phone — Voicemail with business hours and callback timeline
IVR menus — Route urgent calls to an emergency contact or voicemail

Holidays, special closures, and who covers emergencies

Managing public holidays

Add your regional public holidays to your business hours schedule each year. GOV.UK publishes the official UK bank holidays by nation. Most helpdesks let you block out specific dates as non-working days. Tickets received during holidays follow the same out-of-hours rules as weekends.

Planned closures

If your company closes for Christmas, a summer shutdown, or a company retreat, update your auto-replies in advance. "We are closed from December 23 to January 2 and will respond to all messages on January 3" is far better than a generic "currently closed" message.

Emergency coverage

Define what happens when a genuinely urgent issue arrives outside business hours. Options:

On-call rotation — A designated person monitors an urgent-only channel
Automated escalation — The helpdesk alerts the on-call person when an urgent ticket arrives
Third-party coverage — An outsourced team handles critical issues during your off hours

Not every business needs this, but those that do should plan it deliberately rather than having agents informally check Slack on their own time.

How business hours reshape your metrics

Once business hours are configured, your metrics become trustworthy.

First response time now reflects only the hours your team was available. A ticket at 11 PM with a 9:15 AM response shows 15 minutes, not 10 hours.

Resolution time is similarly adjusted. The clock pauses overnight and weekends.

SLA compliance becomes meaningful. Targets are achievable because they're measured against working hours, not calendar hours. You can now tell the difference between "we're slow" and "we get tickets outside our hours" — critical for reporting.

Agent utilisation reflects actual working time, giving managers a realistic picture of capacity and workload.

Platforms like Relentify Helpdesk support multiple business hour schedules with holiday calendars, per-team overrides, and SLA calculations that automatically account for your working hours.

Common mistakes to avoid

Not updating your holiday schedule

If you set up your holiday calendar once in 2022 and haven't touched it since, your auto-replies are wrong and your SLA calculations are inaccurate every single year. Make it a recurring task — January 5th, every year, update the calendar.

Configuring hours that don't match reality

If you set business hours as 8 AM to 8 PM but only staff until 6 PM, tickets arriving between 6 and 8 PM count against your SLA but nobody's there to handle them. Your configured hours must match your actual staffing. (They should also respect the UK's Working Time Regulations and equivalent labour rules in your region.)

One schedule for everything

If you offer live chat only during core hours but email during extended hours, configure separate schedules per channel. A single schedule applied everywhere creates mismatches and confusion.

Not testing before going live

After setting up auto-replies, test them. Send a message to your own support channels outside business hours. Verify the reply arrives promptly, reads well, and contains accurate information.

FAQ: Business hours and out-of-hours replies

Q: What if my team works non-traditional hours (shifts, overnight, weekends)? A: Configure the schedule that reflects your actual hours. If you have day and night shifts, create separate schedules for each team. If you work 24/7, you may not need business hours configured at all — but you'll still benefit from SLA management to define expected response times per channel or tier.

Q: Should I send auto-replies if I have a large team that covers multiple time zones? A: Yes. Even with 24/7 coverage, auto-replies set expectations and acknowledge receipt. "Thanks for reaching out. Our team will respond within 2 hours during your local business hours" works globally.

Q: Can I use macros or templates to speed up out-of-hours responses? A: Absolutely. Use macros for standard out-of-hours replies, then let agents personalise them during working hours. This ensures consistency and reduces agent workload.

Q: What if a customer contacts me outside business hours but their issue is genuinely urgent? A: That's what your emergency contact path is for. Define "urgent" clearly (security breach, service down, payment failed — not "I need this today"). Route urgent contacts to your on-call person; route everything else to the auto-reply queue.

Q: Do I need different auto-replies for different support channels? A: Yes. Email can be longer; live chat must be short. SMS should be brief. IVR phone menus work well for voice. Match the channel's norms.

Q: How do holiday schedules affect SLAs? A: If a ticket arrives on December 24 and you're closed until January 2, the SLA clock doesn't start until January 3. Your first-response SLA (e.g., 4 business hours) is measured from when your team returns. This is why holiday schedules matter: without them, your metrics are rubbish.

Q: What's the best way to handle customer escalations that arrive outside my business hours? A: Set clear boundaries. If a customer escalates a ticket at 10 PM, they get the standard out-of-hours auto-reply. The escalation is prioritised in the queue, but it doesn't bypass your business hours configuration. Urgency is a separate concept from after-hours.

The customer experience payoff

From the customer's side, an immediate auto-reply that says "we will get back to you tomorrow at 9 AM" is vastly better than silence. No uncertainty. No duplicate messages. No assumption that you're ghosting them.

Business hours and auto-replies are not just operational mechanics. They're customer experience tools. They communicate that your business is professional, organised, and respectful of both your customers' time and your team's right to a life outside work.

Set them up, test them, and update them once a year. That's it.