Freshdesk SLA Policies, Set Up Right

A Freshdesk SLA is a promise with a clock attached. Most SLA problems, once you dig into them, turn out to be clock problems rather than promise problems.

Start free trial All Freshdesk guides

How the Freshdesk SLA model works

You define targets for first response, next response and resolution, usually varying by priority. Policies can apply to specific companies, products or groups. That's how you give a premium customer a tighter promise without changing anything for everyone else.

Business hours decide when the clock runs. Escalation rules decide who gets told when a target is at risk or already missed.

The settings that decide your numbers

Business hours or calendar hours. This one choice decides what a four-hour first response actually means at 11pm on a Saturday. It's a very different promise either way.

Pausing while waiting on the customer. Without it, you breach on their delay, and your report ends up describing their behaviour rather than yours.

Escalation before the breach, not after. An escalation that fires on breach isn't a warning. It's a notification about something you can no longer prevent.

Targets you can actually hit

Set the target you can meet 95% of the time on your worst week, not your average one. Targets built on averages break every time volume spikes. And a target the team routinely misses isn't really a target any more, it's background noise.

How duplicates corrupt the report

Two tickets for one problem. One gets answered quickly, the other just sits there. The customer's happy because they got a reply, so nobody escalates, and the forgotten twin ages quietly until it breaches.

Now your report shows a breach nobody complained about. Meanwhile the quickly-closed duplicate counts as a compliant ticket and flatters your attainment. Both distortions disappear once duplicates are merged on arrival.

FAQ

Frequently asked questions

How do Freshdesk business hours and SLA reminders interact?

Freshdesk business hours are the clock your SLA runs on, so a target set in calendar hours behaves very differently. A Freshdesk SLA reminder fires before the breach, and it's only useful if it goes to somebody who can act.

Should the SLA clock pause when waiting on the customer?

Yes. Otherwise you're measuring their response time, not yours.

Should merged tickets count in Freshdesk SLA reporting?

No, exclude them. Otherwise you're taking credit for compliance on work you never did.