Freshdesk Business Hours and SLA Maths
Freshdesk business hours look like an admin detail until you realise they're the denominator in every SLA calculation you report on.
What Freshdesk business hours actually control
A business hours record in Freshdesk is a weekly schedule, a time zone and a list of holidays. You can have more than one, and you attach them to groups.
They do two jobs. They decide when the SLA clock runs, and they decide when out-of-hours automations and escalations behave differently.
That first job is the important one. If your first response target is four hours and your business hours are 9 to 5, an email arriving at 4:55pm on Friday isn't due at 8:55pm on Friday. It's due at 12:55pm on Monday. Same policy, completely different promise, and the only difference is this setting.
Calendar hours or business hours
Every SLA policy makes this choice, and it's worth making deliberately rather than accepting the default.
A common sensible split: urgent tickets on calendar hours because you really do have someone paged, everything else on business hours.
Multiple schedules and the follow-the-sun trap
If you've teams in different regions, give each group its own business hours record in its own time zone. That is what the per-group attachment is for.
The trap is thinking multiple schedules give you follow-the-sun coverage. They do not. They give you accurate clocks for separate teams. Coverage still requires a routing rule that moves the ticket to whichever region is awake, and a handover convention so the incoming team knows what the outgoing one did.
Without that, you have three groups each with beautifully accurate business hours, all of them nine hours behind the customer who's waiting.
The December mistake
Here's the one that catches teams every single year.
Holidays are a list you maintain. Nothing populates it for you, and last year entries don't roll forward.
The pattern is always the same. Somebody set up business hours in year one and typed in that year public holidays. Nobody has touched it since. The office closes for Christmas, tickets keep arriving because customers don't know or don't care, and the SLA clock runs through the whole shutdown because the 25th, 26th and 1st aren't in the list any more.
The team returns in January to a queue where a large share of tickets are already breached before anyone has read them. The breach report for December is meaningless, the January report inherits the mess, and if you have escalation automations they fired into an empty office for ten days.
The fix takes ten minutes. Add next year holidays to every business hours record in November, including the days between Christmas and New Year if you actually close them. Do it for every record, not just the main one, because the second and third schedules are the ones people forget.
While you're there, add an out-of-office auto-reply that states the closure dates and the real return date. A customer who knows nobody is reading until the 5th doesn't send three chasers, and those chasers are pure duplicate volume landing on a team that's already behind.
Testing it before you rely on it
Two checks, both quick.
Then check your reporting is filtering on the same schedule assumptions. A dashboard that mixes calendar-hour and business-hour tickets in one average is producing a number that means nothing.
Frequently asked questions
How do holidays affect Freshdesk operating hours?
Freshdesk holidays are exceptions on top of your Freshdesk working hours, and SLA clocks pause on them. Teams that set Freshdesk operating hours and forget the holiday list spend every January explaining a breach report.
Do Freshdesk business hours apply to SLAs automatically?
Only if the SLA policy is set to business hours rather than calendar hours. Each policy makes that choice independently, so check every one of them.
Can different teams have different business hours?
Yes. Create a schedule per region or function and attach it to the relevant group. Each has its own time zone and its own holiday list.
Do holidays roll over to the next year?
No. The holiday list is manual and dated. Add next year entries in November or the SLA clock will run straight through your Christmas shutdown.
Which plans include business hours?
Business hours and SLA management sit on the paid tiers rather than the free plan. It's one of the most common reasons teams upgrade.
What happens to tickets that arrive out of hours?
They are created normally. The SLA clock simply doesn't start until the next working period begins, assuming the policy uses business hours.
The post-holiday pile-up
Closures produce chasers, and chasers produce duplicate tickets. Ticket Merger collapses them before the team starts digging.
Start free trial14-day free trial. No credit card required.