Zendesk Business Hours and Schedules (2026): How Do You Set Them Up for SLAs?

A Zendesk schedule is a time zone, weekly business hours set in 15-minute increments, and a list of holidays, created in Admin Center under Objects and rules → Business rules → Schedules. SLA targets measured in business hours pause when the schedule says you're closed, which is why a missing or wrong schedule produces 3 a.m. breaches. Suite Growth and Professional get one schedule; multiple schedules need an Enterprise plan. Mechanics here are checked against Zendesk's own documentation.

What is a Zendesk schedule?

In Zendesk's own words: "Create schedules with your business hours, time zones, and holidays. Apply schedules to tickets using triggers… Your default schedule applies to any ticket without one."

Unpacked, a schedule bundles three things:

• A time zone. The reference clock everything else is measured against. A "9 to 5" schedule means nothing until Zendesk knows which 9 to 5. On Growth and Professional, the hours are relative to your account's time zone; only Enterprise lets a schedule use a different zone.
• Business hours. Your weekly operating window, set per day in 15-minute increments (each interval is at least an hour). An interval can't cross midnight, so a shift that runs past midnight has to be split into two intervals, one per calendar day. You can be open 9 to 5 Monday to Friday, split a day around lunch, or run staggered weekend hours.
• Holidays. Named date ranges when you're closed: public holidays, company shutdowns, the week between Christmas and New Year. Zendesk lets you add them up to two years in advance, so you're not editing the schedule every December.

Once defined, a schedule becomes a clock that your business rules read from to decide what "an hour" or "a day" means: triggers, automations and especially SLAs. (If business rules are new to you, start with the Zendesk business rules overview, which ties triggers, automations, SLAs and schedules together.)

Why do schedules matter for SLAs and out-of-hours replies?

You can run Zendesk without ever touching a schedule. But two things break in ways that are hard to spot until they bite.

1. Business hours vs. calendar hours in SLAs

This is the big one. When you build an SLA policy, every target (first reply time, next reply time, resolution time) is measured one of two ways:

• Calendar hours count all elapsed time. A 4-hour first-reply target in calendar hours starts ticking the moment the ticket arrives and never stops: nights, weekends and holidays included.
• Business hours count only the time inside your schedule. The same 4-hour target, in business hours, pauses when you close and resumes when you reopen. A ticket that lands at 4:45 p.m. with a 4-hour business-hours target isn't due until mid-morning the next working day, not at 8:45 p.m. while the office is dark.

The catch: business-hours SLAs only make sense if a schedule exists and is correct. Without one, "business hours" has nothing to pause against, and you get 3 a.m. and Sunday breaches that aren't your team's fault. The clock was wrong. A schedule with the right time zone and holidays is what makes business-hours SLAs fair and your breach numbers trustworthy.

2. Different behavior in vs. out of hours

The second reason is customer-facing. Triggers can branch on whether a ticket arrived inside or outside your hours, using the condition "Within business hours?" (Yes/No), and there's a matching "On a holiday?" condition that stays true for the whole day of the holiday. Zendesk won't let you combine "On a holiday?" with "Within business hours?" in the same trigger, so build them as separate triggers. Neither condition exists on Team plans. With them you can send different auto-replies depending on the clock:

• In hours: "Thanks, we've got your message and a member of the team will reply shortly."
• Out of hours / holiday: "Thanks for reaching out. Our team is offline until 9 a.m. Monday; we'll get back to you first thing."

Setting expectations honestly when you're closed is one of the cheapest CSAT wins available, and the schedule is the switch that powers it. (See how triggers work for the condition-and-action mechanics.)

One thing to keep straight: Support business hours (the schedule we're discussing) are separate from Chat operating hours. Zendesk's docs say plainly that "Zendesk Support schedules do not apply to Chat operating hours." If you run live chat, set both.

How do you set up a schedule in Zendesk?

Schedules live in Admin Center under Objects and rules → Business rules → Schedules. Click Add schedule (or open your existing one), then:

1. Name it and pick the time zone. Choose the zone your team primarily works in. This anchors every business-hours and holiday calculation, so get it right before anything else. Below Enterprise, the schedule follows the account time zone, so check that setting too.
2. Set your business hours. In the Weekly schedule section, enter the open window for each day in 15-minute increments. Leave a day blank to mark it closed; split a day into two intervals if you close for lunch. Aim for what your team actually covers, not what you wish you covered. The SLA clock believes you.
3. Save, then add holidays. Open the Holidays section and give each holiday a name and a start and end date. Add the whole year (and next year) at once so the schedule stays accurate without monthly babysitting. Save again.

On a single-schedule plan, this one schedule becomes the clock every ticket uses.

How does a ticket get a schedule when you have several?

If you support different regions or run teams with different hours (say a 24/5 Tier 1 and a 9 to 5 Billing desk), one schedule can't represent everyone. That's where multiple schedules come in, and the rules for which one a ticket uses matter:

• The default schedule. The first schedule in the list is the default, and it "applies to all tickets" that haven't been assigned anything else. Every ticket gets a schedule whether or not you do anything.
• Assigning a different one via trigger. To put a ticket on a non-default schedule, you build a trigger. As Zendesk puts it, "You can create triggers to apply different schedules to tickets." The trigger's conditions decide which tickets qualify (e.g. Organization is EU-Customers, Group is Billing, or a brand), and the action is "Ticket: Set schedule", pointing at the schedule you want. You create one such trigger per schedule you route to.

This is how regional SLAs work in practice: European tickets ride a European schedule, US tickets ride a US one, and each SLA target pauses and resumes against the right local clock. On multi-schedule accounts, Zendesk confirms that "triggers, SLA policies, views, and automations based on business hours will use the schedule applied to the ticket." Enterprise also adds a "Within (schedule)" condition, which checks the update time against any schedule rather than only the one on the ticket.

Which Zendesk plans include schedules?

This is the part most teams discover at the worst moment. Per Zendesk's documentation, schedules are available on Suite Growth, Professional, Enterprise and Enterprise Plus, and on Support Professional and Enterprise. Team plans don't get them. The split, as in the table at the top:

• Suite Team and Support Team: no schedules, and no "Within business hours?" condition.
• Suite Growth, Suite Professional, Support Professional: one schedule, on the account time zone.
• Suite Enterprise, Enterprise Plus, Support Enterprise: multiple schedules, each with its own time zone, plus the "Ticket: Set schedule" action.

In short: a single schedule comes with the mid-tier plans, but multiple schedules are an Enterprise feature. If you're on Professional and need different hours per region or team, you have one schedule to work with. That usually means picking the most representative window and accepting that some teams' SLAs won't reflect their local hours, or upgrading. Zendesk changes packaging from time to time, so confirm in your own Admin Center before committing to a design.

What mistakes break Zendesk schedules?

A schedule is simple to set and easy to get subtly wrong. The recurring traps:

• No schedule at all, with business-hours SLAs. The classic. Your SLAs are set to business hours but there's no schedule to define them, so you rack up phantom overnight and weekend breaches.
• The wrong time zone. A schedule in the wrong zone is off by hours for every ticket, quietly and consistently, in a way that's hard to see from breach numbers alone. Below Enterprise that means checking the account time zone. Double-check this first.
• Forgetting holidays. The most common ongoing failure. Without holidays, the SLA clock runs straight through every public holiday and company shutdown, and your team comes back from a long weekend to a wall of breached tickets. Load the full year ahead of time.
• A shift that crosses midnight entered as one interval. Zendesk won't accept it; split it at midnight into two intervals.
• Assuming Chat hours follow Support hours. They don't. Set Chat operating hours separately.
• Building multiple schedules but forgetting the routing trigger. On Enterprise, a second schedule does nothing on its own. Every ticket stays on the default until a "Ticket: Set schedule" trigger moves it.
• Treating it as set-and-forget. Hours change, offices move, you add a region. Revisit schedules at least yearly (and whenever you change SLAs), and roll holidays forward before they lapse.

How do you cover tickets that arrive outside business hours?

Schedules exist because humans have hours. They keep your metrics honest about those hours, but they don't extend them. Out of hours, the customer still waits.

An AI agent layer can close that gap. Macha runs on top of Zendesk (it's not a help desk and not a Zendesk replacement) and answers from your knowledge base and connected systems 24/7. A customer who writes in at 2 a.m. on a holiday can get a real answer to a routine question, not just a "we're closed" auto-reply, and anything it can't handle becomes a normal ticket waiting for your team when the schedule reopens. The schedule still governs your human SLAs and reporting; the AI narrows how much has to wait for working hours.

On the billing model: Macha bills per ticket (one thread with one person, charged once however many messages, lookups and drafts it takes), starting at $299/mo for up to 750 tickets, never per resolution. Per-resolution pricing ties your bill to an outcome definition the vendor controls. Macha is another integration to maintain, and it only performs as well as the knowledge you connect to it. If after-hours volume is your pain point, that's the gap it fills. We walk through the patterns in how to automate Zendesk with AI, and you can try it with $50 of free usage, no credit card required.

Frequently asked questions

What is a schedule in Zendesk? A schedule defines when your support team is open: a time zone, your weekly business hours, and your holidays. Zendesk uses it as the clock for business rules, most importantly SLA policies, which can pause outside your hours. Triggers can branch on whether a ticket arrived inside or outside that window.

What's the difference between business hours and calendar hours in a Zendesk SLA? Calendar hours count all elapsed time, including nights, weekends and holidays. Business hours count only the time inside your schedule, so an SLA target pauses when you're closed and resumes when you reopen. Business-hours targets only work if a schedule with the right time zone and holidays is set up. See Zendesk SLA explained.

How does a ticket get a schedule in Zendesk? Every ticket uses the default schedule (the first one in your list) unless a trigger assigns a different one. On multi-schedule accounts, you create a trigger whose conditions match the tickets you want (by organization, group, brand and so on) and use the action "Ticket: Set schedule".

Can I have multiple schedules in Zendesk? Yes, on Enterprise. Suite Growth, Suite Professional and Support Professional allow one schedule; Team plans have none. Multiple schedules let you run region- or team-specific hours and SLAs, each in its own time zone.

How do I set up holidays in Zendesk? In Admin Center → Objects and rules → Business rules → Schedules, open the schedule, go to the Holidays section and add each holiday with a name and a start and end date. You can schedule holidays up to two years ahead. During a holiday, business-hours SLAs and "within business hours" logic treat your team as closed.

Are Zendesk Support business hours the same as Chat operating hours? No. Support business hours (your schedule) and Chat operating hours are separate settings configured in different places. If you offer live chat, set both; they don't sync.

Can a business-hours interval run past midnight? No. An interval can't cross a date boundary, so a 10 p.m. to 2 a.m. shift becomes two intervals: 10 p.m. to midnight on one day and midnight to 2 a.m. on the next.

What should you set up first?

Start with the time zone, then business hours, then a full year of holidays. Almost everything time-sensitive in Zendesk reads from that clock: SLA pauses, out-of-hours auto-replies, "within business hours" logic. Get the time zone and holidays right and your business-hours SLAs become fair; skip the schedule and Zendesk will count the hours you were never open. One schedule is enough if your plan allows only one and it covers you; reach for multiple schedules (Enterprise) plus "Set schedule" triggers when regions or teams differ. The schedule only describes your hours, so closing the after-hours gap itself is a separate job. From here, go deeper on SLAs, triggers, and the business rules that tie them together.

Schedule, trigger-condition and plan behavior checked against Zendesk's official documentation on 24 September 2026. Zendesk updates plans and packaging periodically, so confirm specifics in your own Admin Center before relying on them.