Freshdesk Business Hours Explained (Multi-Timezone & Holidays)

Business hours vs. calendar hours

The single most important distinction in Freshdesk time-tracking is business hours versus calendar hours, because it decides which clock your SLA runs on.

Business hours are your company's official working schedule. When an SLA is tied to business hours, the timer only ticks during those defined periods — nights, weekends, and holidays are excluded from the calculation. If your support desk works 9 AM to 5 PM Monday to Friday and a ticket arrives at 4:55 PM Friday, the SLA clock pauses at 5 PM and resumes at 9 AM Monday.

Calendar hours are round-the-clock, 24/7 timing. Every hour counts — weekends, holidays, 3 AM, all of it. Freshworks recommends calendar hours for urgent and high-priority tickets that need attention regardless of the day or time. A "respond within 1 hour" promise on a Sev-1 outage should almost never pause overnight.

The practical rule: use business hours for your everyday priorities so your team isn't penalized for time it was never expected to be online, and use calendar hours for the small set of urgent tickets where the customer genuinely expects a 24/7 response.

Where to configure it

Everything lives in one place. Go to Admin → Team → Business hours, then click Add business hours (or Edit an existing set). Inside a business-hours calendar you set three things:

1. Timezone. Each calendar carries its own timezone, so the schedule is interpreted correctly for the team it serves.
2. Working days and hours. Define the working window for each day of the week. Freshdesk supports up to five breaks per day within a calendar, so you can carve out lunch or shift gaps that shouldn't count toward SLA.
3. Holidays. Add holidays manually or import a country's holiday list. Holidays recur every year and are excluded from SLA calculations, just like non-working hours.

That holiday behavior is worth seeing, because it's where a lot of "phantom breach" surprises come from.

Multiple business hours for multiple timezones

If your whole team sits in one city, a single business-hours calendar is all you need. The moment you run support across regions — a London morning shift and an Austin afternoon shift, say, or three centers rotating a 24×7 desk — one global schedule stops making sense. A ticket routed to the Austin group shouldn't have its SLA measured against London's clock.

Freshdesk solves this with multiple business hours: you create a separate calendar for each region or team, each with its own timezone and holiday list, then attach each calendar to the right group. The setup is two steps, per Freshworks' guide to configuring multiple business hours:

1. Create the calendars. In Admin → Team → Business hours, click New business hours for each region, setting the correct timezone and importing that country's holidays.
2. Assign to groups. In Admin → Team → Groups, open a group, pick the matching calendar from the Business Hours dropdown, and save. From then on, every ticket assigned to that group has its SLA executed against that group's schedule.

This is the mechanism that keeps distributed teams from being unfairly penalized. Each region's SLAs run on that region's real working hours and real holidays — no manual timezone math, no shared-calendar compromise.

One gotcha to internalize: a ticket inherits its business hours from the group it's assigned to. If a ticket has no group yet, it falls back to the account-level default business hours. So the whole system only works if your routing actually lands tickets in the right group early. This is why business hours and Freshdesk automation rules are so tightly linked — your Dispatch'r (ticket-creation) rules decide the group, and the group decides the SLA clock.

How business hours actually drive the SLA clock

Here's the part that trips up even experienced admins, especially after a 2025 change to how Freshdesk interprets day-based SLAs.

It used to be that "1 business day" meant the start to the end of one working day. Under the updated logic, Freshworks now interprets "1 day" as 24 business hours — not 24 calendar hours, and not a single working day. The SLA accumulates actual business hours until it reaches 24, which can span several calendar days.

A concrete example straight from the doc: if your business hours run 9 AM–9 PM (12 hours a day) and a ticket is created Monday at 9 AM with a 1-day resolution SLA, it's due Tuesday at 9 PM — because 12 hours Monday plus 12 hours Tuesday equals the 24 business hours the SLA now requires. With a shorter 9-to-5 (8-hour) day, that same "1 day" SLA would take three calendar days to accumulate its 24 business hours.

The takeaways for anyone writing SLA policies:

• Hours-based SLAs are safest. Setting an SLA in hours ("resolve in 8 business hours") is unambiguous and immune to the day-interpretation change.
• Your calendar shapes every deadline. Widen or narrow a group's working window and you silently move every SLA due-date attached to it.
• Holidays and breaks pause the clock. A holiday you added, or a lunch break in the schedule, is time the SLA timer simply doesn't count.
• Priority can switch the clock entirely. Route urgent tickets to calendar-hour SLAs so an overnight outage doesn't get a free pass until morning.

Understanding SLA policies and business hours together is the only way to make your SLA reports trustworthy — the two features are designed to be read as one system.

The honest limits — where business hours stop

Freshdesk's business-hours engine is genuinely good at what it does: it's precise, timezone-aware, holiday-aware, and it wires cleanly into SLAs and groups. Credit where it's due — for scheduling when the SLA clock runs, it's hard to fault.

But it's a scheduling tool, not a workload tool, and there are real edges:

• It's group-and-timezone logic, not demand-aware. Business hours know when your team is theoretically online. They know nothing about whether the queue is 5 tickets or 500, or whether the one agent on the late shift is drowning.
• Plan gating is real. Business hours are available on Growth, Pro, and Enterprise plans (and on Freshdesk Omni for signups after December 2025), but multiple/additional business hours require Pro or above. Smaller teams on lower tiers are stuck with a single schedule. Always confirm against your own plan.
• It doesn't do the work. Business hours decide the deadline; they don't help you hit it. When the London desk closes and the queue keeps filling overnight, the schedule just pauses the clock — nothing is actually getting answered until someone clocks in.

That last point is where an AI agent layer earns its place — not by replacing any of this, but by covering the hours your humans can't.

Where an AI layer fits on top

Business hours are about when the clock runs. An AI agent is about who answers when nobody's at the desk. Those are complementary, not competing — and it's worth being clear-eyed about the build-versus-buy decision, which we cover in building an AI agent from scratch vs. using a platform. The broader category of AI agents for customer service exists to handle exactly the after-hours and overflow work a static schedule can't.

Macha is one such layer: it runs on top of the Freshdesk you already use, as a native connector — it does not replace your help desk, and it changes nothing about your business hours, groups, or SLAs. You connect Macha to Freshdesk with your subdomain and API key, and it reads and writes the same tickets your schedules already govern: drafting or posting replies, adding notes, and resolving repetitive questions grounded in your help center — at 3 AM on a holiday just as readily as at 2 PM on a Tuesday. (To be precise, Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller.)

The division of labour is clean. Keep Freshdesk's business hours doing what they do best: defining working windows, honoring holidays, and running SLA timers per group and timezone. Layer an agent on top to actually cover the off-hours gap — deflecting the common questions that arrive overnight, and looking up order or account status through a custom tool that turns any REST API into something the agent can call. Your SLA clock still governs the deadline; the agent just makes sure the queue isn't cold when your team logs back in.

FAQ

What's the difference between business hours and calendar hours in Freshdesk? Business hours count SLA time only during your defined working schedule — nights, weekends, and holidays are excluded. Calendar hours count around the clock, 24/7, including weekends and holidays. Freshworks recommends calendar hours for urgent tickets that need attention regardless of day or time, and business hours for everything else.

How do I set up different business hours for different timezones? Create a separate business-hours calendar for each region under Admin → Team → Business hours (each with its own timezone and holiday list), then assign each calendar to the matching group under Admin → Team → Groups. Every ticket assigned to that group then runs its SLA on that group's schedule. Note that multiple business hours require the Pro plan or above.

Do holidays affect Freshdesk SLA calculations? Yes. Holidays you add to a business-hours calendar (manually or by importing a country list) are excluded from SLA calculations, the same way non-working hours are. They recur every year, so a ticket that sits over a holiday won't have that time counted against its business-hours SLA.

Does "1 day" mean 24 hours in a Freshdesk SLA? Under Freshdesk's updated logic, a 1-day SLA is interpreted as 24 business hours — not 24 calendar hours and not one working day. Those 24 hours accumulate only during your defined business hours, so with an 8-hour working day a "1 day" SLA can take three calendar days to reach its deadline. Setting SLAs in explicit hours avoids the ambiguity.

Can I add AI coverage for after-hours tickets without replacing Freshdesk? Yes. An AI agent layer like Macha connects to Freshdesk as a native connector and runs on top of your existing help desk — it doesn't change your business hours, groups, or SLAs. It reads and writes the same tickets, answering common questions grounded in your knowledge base even outside working hours. You can review Macha's pricing and see the Freshdesk connector for details.

Ready to cover the hours your schedule can't? Start a free trial and connect Macha to your Freshdesk in minutes.