How to Set Up Business Hours in Freshdesk

What business hours actually control

A business-hours calendar in Freshdesk is three things bundled together: a working schedule (which days and which hours your team is on), a timezone, and a holiday list. Individually none of them is exciting. Together they define the only clock your SLA policies are allowed to tick against.

The distinction that matters most is business hours versus calendar hours. When an SLA is measured in business hours, the timer only advances during the working windows you've defined — evenings, weekends, and holidays are simply not counted. When it's measured in calendar hours, the timer runs around the clock, ignoring your schedule entirely. Freshworks frames it with a neat example in What are business hours and calendar hours?: a ticket due in six hours on a Friday evening is fine to pick up Monday morning if the SLA runs on business hours — but on calendar hours, you'd need to resolve it immediately. Get this choice right per SLA policy and your targets become both fair to agents and honest to customers.

Step 1: Set your default working schedule

Every Freshdesk account ships with one default business-hours calendar. Start there.

1. Go to Admin → Team → Business Hours.
2. Open the default calendar (often named "General working hours") to edit it.
3. Choose your working days — for most teams, Monday to Friday.
4. Enter the working hours for each day, for example 8:00 AM to 5:00 PM.
5. Add break slots if you want lunch or shift gaps excluded from the SLA clock. The gap between two working slots on the same day is treated as a break, and you can add up to five breaks per day.
6. Set the Time Zone for this calendar — this is the anchor Freshdesk uses to interpret every hour above.

That last point is the one people skip. The hours "8:00 AM to 5:00 PM" are meaningless until Freshdesk knows whose 8:00 AM — so the timezone field is not optional cosmetics, it's what makes the schedule real.

Step 2: Add a holiday calendar

Holidays are where business hours earn their keep. Without them, your SLA timers keep counting straight through New Year's Day and your team gets penalised for a day the office was closed.

Inside a business-hours calendar, open the Holidays tab and add each date. A few things worth knowing:

• Every holiday you add is created as a recurring annual holiday — set New Year's Day once and it repeats every January 1 without you touching it again.
• You can build the list manually, or import a country's holiday list so you don't have to hand-enter twelve national holidays.
• Holidays are excluded from SLA calculations entirely — the clock simply doesn't advance on those days, exactly like it doesn't advance overnight.

For a team spread across regions, this is the difference between a holiday calendar that reflects your London office and one that reflects your Bangalore office. Which is precisely why you often need more than one calendar.

Step 3: Create multiple calendars for multiple timezones

A single calendar works fine if your whole team shares one clock. The moment you run support out of two regions — say a Chennai team and a New York team — one calendar starts lying to someone. A ticket that arrives at 9:00 AM New York time is landing at 6:30 PM in Chennai, and if both teams share one calendar, one of them is being timed against hours they don't work.

Freshdesk solves this with multiple business hours — separate calendars, each with its own working schedule, timezone, and holiday list. Per Freshworks' Configuring Multiple Business Hours in Freshdesk, you create additional calendars from the same Admin → Team → Business Hours screen. One important caveat on plan gating, though.

Plan gating (verify against your own tier). The single default calendar is available on every plan. But creating multiple business-hours calendars is a paid feature — currently gated to Pro and Enterprise (historically the Estate and Forest tiers). If you're on a lower plan and need per-region SLAs, this is the upgrade that unlocks it.

Step 4: Assign calendars to groups

Creating a calendar doesn't do anything on its own — Freshdesk applies business hours per group, not per ticket directly. So the final step is wiring each calendar to the team it belongs to.

1. Go to Admin → Team → Groups.
2. Open the group you want to schedule (for example, "NA Support" or "APAC Support").
3. In the group's settings, find the Business Hours field and select the calendar for that region.
4. Save.

From that point on, every incoming ticket assigned to that group has its SLAs executed against that group's business hours. This is the mechanism that makes follow-the-sun support fair: the Chennai group's tickets are timed on Chennai hours, the New York group's on New York hours, and neither team is penalised for the other's overnight.

How business hours drive the SLA math

Here's the whole chain in one line: an SLA policy sets a target ("first response within 4 hours"), the target is measured against a group's business-hours calendar, and that calendar decides which minutes count.

Walk a real ticket through it. An "Urgent" ticket lands in your APAC group at 4:30 PM on a Friday, with a 4-hour first-response SLA measured in business hours, on a Mon–Fri 8–5 calendar. The clock runs 4:30 to 5:00 (30 minutes), then pauses — evenings, the weekend, and any Monday holiday don't count. It resumes at 8:00 AM on the next working day and the remaining 3.5 hours tick from there, giving a real due time of 11:30 AM that morning. Swap the SLA to calendar hours and the same ticket is due at 8:30 PM Friday night. Same policy, wildly different deadline — decided entirely by the business-hours calendar behind it.

The honest limits — and where an AI layer picks up

Freshdesk's business-hours feature is genuinely well-built: recurring holidays, importable country lists, per-group timezone calendars, and clean SLA integration cover the large majority of support operations. For scheduling and SLA accounting, you rarely need anything more.

What business hours can't do is anything about the ticket itself. They decide when the clock ticks — they do nothing to help you actually hit the target once it's ticking. A calendar won't draft a first response, deflect a repeat question, or route a ticket by what the customer meant rather than which group inbox it landed in. If your APAC queue breaches SLAs, it's usually not because the hours are wrong; it's because there aren't enough hands in the working window. And multiple calendars themselves sit behind a plan upgrade, so smaller teams that genuinely operate across timezones can't always get per-region fairness without paying up.

This is the seam where an AI agent layer helps — not by replacing any of this, but by covering the working windows your team can't. It's worth being clear-eyed about the build-versus-buy tradeoff before you commit, and about what AI agents for customer service realistically do. Macha is one such layer: it runs on top of the Freshdesk you already use, as a native connector — it doesn't replace your help desk, and it doesn't touch your business-hours or SLA configuration. You connect Macha to Freshdesk with your subdomain and API key, and it reads and writes the same tickets your calendars and SLA policies already govern.

The practical division of labour is clean. Keep Freshdesk business hours doing exactly what they're great at: fair SLA accounting, holiday exclusions, and per-region scheduling. Layer an agent on top for the after-hours gap — deflecting repeat questions grounded in your help center at 2:00 AM, drafting first replies for an agent to approve when the working window opens, and looking up order or account status through a custom tool that turns a REST API into something the agent can call. Because agents are non-deterministic, Macha lets you batch-grade a candidate against your real historical Freshdesk tickets before it ever touches a live queue. For the wider picture on wiring automation into Freshdesk, see how to automate Freshdesk with AI and the native rules in Freshdesk automations explained.

FAQ

Where do I set business hours in Freshdesk? Go to Admin → Team → Business Hours. Every account has one default calendar you can edit there, and on Pro and Enterprise plans you can create additional calendars. You then apply a calendar to a team under Admin → Team → Groups.

Can I have different business hours for different timezones? Yes — that's exactly what multiple business hours are for. You create a separate calendar per region, each with its own timezone, working schedule, and holiday list, then assign each calendar to the relevant group. This feature is gated to Pro and Enterprise plans (historically Estate and Forest); a single default calendar is available on all plans, so confirm your tier before relying on it.

Do holidays affect SLA timers in Freshdesk? Yes. Holidays added to a business-hours calendar are excluded from SLA calculations — the timer simply doesn't advance on those dates, the same way it pauses overnight and on weekends. Every holiday you add is treated as a recurring annual holiday, and you can import a country's list rather than entering them by hand.

What's the difference between business hours and calendar hours? Business hours only count time during your defined working windows, pausing evenings, weekends, and holidays. Calendar hours run 24/7 regardless of your schedule. You choose which one applies on each SLA policy, so urgent tickets can run on calendar hours while standard ones run on business hours.

Can I add AI to Freshdesk to cover hours my team isn't working? Yes, without changing your help desk. An AI agent layer like Macha connects to Freshdesk as a native connector and works the same tickets your SLA policies govern — deflecting and drafting during and outside working windows — grounded in your knowledge base rather than keyword rules. It runs on top of Freshdesk, not as a replacement; you can review Macha's pricing and the Freshdesk connector for details.

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