Priority-Driven SLAs
Set first-response and resolution targets per priority. Typical tiers: Urgent (1 hour first response, 4 hour resolution), High (2 hour / 8 hour), Medium (4 hour / 24 hour), Low (1 business day / 3 business days). Calibrate to what customers actually expect, not what feels aggressive. The single most common SLA mistake is matching marketing claims rather than capacity — a 1-hour Urgent target with 8 agents covering 24/7 globally requires roughly 12-15 FTEs to maintain reliably. Underpromise on the SLA, overdeliver on response, and CSAT goes up without burning out the team.
Business Hours
Configurable per team, per group, or globally. Common shapes: 24x5 (weekdays only, around the clock), 24x7 (always), business hours only (9-5 in a regional time zone), and follow-the-sun handoff between regional groups. The SLA timer pauses outside business hours when the SLA is configured to honor them. Configure at Admin -> Workflows -> Business Hours. Each business-hours profile carries its own holiday calendar — load the calendar a year in advance so SLAs don’t tick on Diwali and December 25 by accident.
Escalations
Breach notifications fire as soon as the SLA timer crosses a threshold. Configure escalation tiers: at 50% of remaining SLA notify the agent, at 80% notify the group manager, at 100% (breach imminent) auto-reassign to a senior agent or escalation queue. Don’t wait for a post-breach review to act — the in-flight escalation is what saves CSAT. Configure under Admin -> SLA Policies -> Escalations. Each tier can fire an email, an in-app notification, a Slack message via Freshdesk Marketplace integration, or a webhook to your on-call system.
// Pull tickets at risk of SLA breach in the next hour
fetch(`https://${domain}.freshdesk.com/api/v2/search/tickets?query="due_by:<'2026-04-24T15:00:00Z' AND status:2"`, {
headers: { Authorization: auth }
});Multi-Tiered SLAs
Different SLAs per customer segment is a common requirement. Enterprise customers contractually expect tighter targets than SMB customers on a self-serve plan. Assign SLA via a custom field on the contact or company (sla_tier: gold | silver | bronze) and bind each tier to its own SLA policy. Reports segment by tier so you can prove contractual compliance — and so the team sees which segment is straining capacity. Without segmentation, a flood of low-tier tickets eats response time that gold-tier customers paid for.
Reporting
SLA attainment rate per team, per agent, per customer, and per priority. Publish weekly to support managers and monthly to leadership. Dropping attainment is a leading indicator: it signals process drift, staffing shortfall, or a product issue producing unusual ticket volume. Pair the attainment number with first-response time distribution (P50, P90) so the conversation is about the long tail, not the average. The average can stay green while the worst 10% of tickets blow past the SLA badly enough to cost a renewal.
Common Failure Modes
Three. First, SLA timer running during the customer-pending state — most teams want it paused while waiting on the customer; check the “Pause SLA when waiting on customer” toggle per policy. Second, business-hours profile not updated for a new office; the team in Sydney runs on the New York calendar and SLAs drift by 14 hours. Third, holidays not loaded for the year — the SLA breaches on January 1 and the on-call gets paged at 3 AM for what should have been an off-hours queue.
Cost Considerations
SLA Policies are available on all paid Freshdesk tiers. Multi-tier SLAs and advanced escalation rules require Pro+. The decision: if you have any contractual SLA commitments, the Pro tier upgrade is required — there is no clean way to enforce per-customer SLAs on the Growth tier without manual workarounds.
What to do this week
Pull last month’s breach report and group breaches by reason: customer-pending miscount, holiday misconfig, capacity, and process. The biggest bucket tells you the next fix. Don’t try to fix all four at once.
