How to Set Up SLA Policies in Freshdesk

What an SLA policy actually controls

A Service Level Agreement policy in Freshdesk is a set of time targets attached to tickets that match certain conditions. Each policy governs three kinds of clock. The first response time measures how long a customer waits before an agent's first reply. The resolution time measures how long the whole ticket takes from creation to resolved. And on higher plans, an every response (or next response) target holds agents to a pace on every reply in a back-and-forth, not just the opening one.

Crucially, you set each of these targets separately for each of the four priorities — Urgent, High, Medium, and Low — so an urgent outage gets a tighter clock than a low-priority feature question. You also decide whether the timer counts Business hours (the working calendar you've defined) or Calendar hours (a flat 24×7). That single choice quietly determines whether a ticket that lands at 6pm on a Friday is already burning time or paused until Monday morning, which is why business hours and SLAs are so tightly coupled — a topic we go deeper on in Freshdesk business hours explained.

Step 1: Open the SLA Policies module and set your targets

Everything lives in one place. Per Freshworks' Understanding SLA Policies documentation, you configure policies under Admin → Workflows → SLA Policies.

1. Go to Admin → Workflows → SLA Policies. You'll see a Default SLA policy that applies to every ticket unless a more specific one matches.
2. Click into the default policy (or New SLA policy, on plans that allow multiple) and find the "Set SLA target as" table.
3. For each priority row — Urgent, High, Medium, Low — enter a First response time and a Resolution time. On plans that support it, also set an Every response time.
4. For each row, choose Business hours or Calendar hours (24×7). Urgent rows are usually 24×7; lower priorities usually follow business hours.
5. Save.

Note that the floor for a target on Freshdesk Standard is 5 minutes across all priorities, while Freshdesk Omni can go as low as 30 seconds in 15-second increments — so if you're modelling a very tight response promise, confirm your plan supports the granularity you want.

Step 2: Target the right tickets with conditions and order

The default policy is a fine start, but real teams want different promises for different customers. On Pro and above you can create multiple SLA policies and scope each one with conditions — by company (e.g. customers on a priority-support plan), group, product, source, or ticket type.

Order is the part people miss. For a new ticket, the first policy in the list whose conditions match is the one that applies — Freshdesk stops at the first match. So put your most specific, highest-stakes policies (VIP companies, urgent-only rules) at the top and leave the catch-all default at the bottom. Get the order wrong and a broad policy near the top will "swallow" tickets that should have hit a stricter one below it.

Step 3: Configure reminders so agents act before a breach

A target you only find out about after it's blown isn't much of a target. From the Pro plan onward, Freshdesk can nudge agents as a deadline approaches. Inside the SLA policy, under the reminder settings, you can enable a separate reminder for the first response, the next response, and the resolution target, choose who it goes to (the assigned agent, or other team members), and set how far ahead it fires — anywhere from 5 minutes to 4 hours before the deadline.

A sensible pattern:

1. First-response reminder to the assigned agent, 15 minutes before the deadline.
2. Resolution reminder to the assigned agent and their group, 1 hour before the deadline.
3. Keep reminders sparing — one or two well-placed nudges beat a wall of alerts everyone learns to ignore.

Step 4: Set up escalations for when a target is missed

Reminders are the warning; escalations are what happens when the deadline passes anyway. Also available from Pro onward, escalations send an email up the chain when a target is violated. The two clocks behave differently here, and it's worth knowing the shape of it:

• For a missed first response, you get a single escalation level — one email to whoever you nominate (assigned agent, manager, team lead).
• For a missed resolution, you can stack up to four escalation levels, each firing after a further interval — so a ticket that keeps slipping climbs from agent, to team lead, to manager, and beyond.

You wire the actual notification toggles under Admin → Workflows → Email Notifications → Agent Notifications, where the First Response SLA violation and Resolution Time SLA violation notifications live. Freshworks documents the reminder-and-escalation setup in Setting up SLA reminders and escalations.

A worked example: P1 vs P2 targets

Here's how a mid-sized support team might translate its promises into a policy. Think of P1 as an Urgent, service-affecting incident and P2 as a High-priority problem that hurts but isn't on fire.

The pattern to copy isn't the exact numbers — it's the shape: tighter clocks and 24×7 timing for the incident that can't wait, business-hours timing and a shallower escalation ladder for the one that can.

The honest limits — and where an AI layer picks up

Freshdesk's SLA engine is genuinely good at what it does: it's deterministic, transparent, and reliable. It will always know exactly how much time is left and who to email when it runs out. But notice what it can't do. An SLA policy measures and enforces time — it does not produce the reply that stops the clock. It can tell you a first-response deadline is 10 minutes away; it can't read the ticket, understand the customer's actual problem, and draft the answer that satisfies the target. Every escalation still lands on a human who has to do the reading and writing.

It also enforces the priority you assigned, not the priority a ticket deserves. If intake mislabels an urgent outage as Medium, the SLA clock faithfully applies the wrong, laxer target. And when the underlying question is "what's the status of order #4471?", the policy can't fetch that from your systems — it just counts down while an agent goes and looks.

This is the seam where an AI agent layer fits, and it's worth being clear-eyed about the build-versus-buy tradeoff before you reach for one. The broader category of AI agents for customer service exists precisely to do the reasoning-heavy work an SLA timer 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 or its SLA policies. You connect Macha to Freshdesk with your subdomain and API key, and it reads and writes the same tickets your SLAs already time: drafting or posting grounded first replies (so the first-response clock is beaten with a real answer, not just a placeholder), triaging by intent so priority is set correctly before the timer starts, and looking up order or account status through a custom tool that turns a REST API into something the agent can call. (Macha's connector is for Freshdesk specifically — not Freshchat, Freshservice, or Freshcaller. And credits are consumed per AI action, not per resolution — see the pricing breakdown.)

The clean division of labour: keep Freshdesk's SLA policies as the source of truth for what's promised and what's overdue, and layer an agent on top for the part the clock can't do — actually answering fast enough to keep the promise. If your timers are firing at surprising moments before you even get to any of this, the usual culprits are business hours and status configuration, which we untangle in why your Freshdesk SLA isn't calculating correctly.

FAQ

Where do I set up SLA policies in Freshdesk? Go to Admin → Workflows → SLA Policies. There you'll find a Default SLA policy that applies to all tickets, and — on Pro and above — the option to create additional policies scoped by conditions like company, group, product, or source.

What targets can an SLA policy enforce? A first response time, a resolution time, and (on supporting plans) an every/next response time — each set separately for the four priorities (Urgent, High, Medium, Low), and each calculated on either your business hours or a flat 24×7 calendar.

Are SLA reminders and escalations available on every plan? No. Reminders and escalations are available from the Pro plan onward, and multiple SLA policies require Pro-and-above as well (for recent signups, multiple policies are available on Growth, Pro, and Enterprise). Reminders can fire from 5 minutes to 4 hours before a deadline. Confirm the exact behaviour against your own plan.

How many escalation levels does Freshdesk support? For a missed first response you get a single escalation level. For a missed resolution you can configure up to four escalation levels, each firing after a further interval so the ticket climbs the management chain.

Can I add AI to Freshdesk SLAs 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 and its SLA policies — it doesn't replace them. It helps meet the targets by drafting or sending grounded first replies and triaging tickets by intent, while Freshdesk stays the system of record for what's promised and what's overdue.

Ready to help your agents beat the clock instead of just watch it? Start a free trial of Macha and connect it to your Freshdesk in minutes.