SLA Policy
Definition
An SLA policy is the configured set of rules inside a help desk that assigns service-level targets — like first-response and resolution times — to tickets based on conditions such as priority, channel, or customer tier.
How it works
You define conditions (for example, "priority is urgent AND customer is enterprise") and attach time targets to them ("first response within 30 minutes, resolution within 4 hours"). When a ticket matches, the help desk starts SLA timers and tracks them against those targets, usually counting only business hours.
If a target is missed, the ticket registers an SLA breach, which can fire alerts, escalate the ticket, or reassign it. Timers commonly pause when a ticket is pending on the customer, so agents aren't penalized for delays outside their control.
Why it matters
The SLA policy is where a service-level agreement stops being a document and becomes operational. It turns contractual promises into live timers, alerts, and escalations that agents actually see — the difference between hoping you hit your commitments and being systematically nudged to meet them.
Frequently asked
What is the difference between an SLA and an SLA policy?
An SLA (service-level agreement) is the commitment itself — the promised response and resolution times. An SLA policy is the help-desk configuration that enforces it by matching tickets to targets and tracking timers.
Do SLA timers run around the clock?
Only if you configure them to. Most teams tie SLA timers to their defined business hours, so the clock pauses outside working times unless they offer 24/7 support.
Related terms
Service Level Agreement (SLA)
A Service Level Agreement (SLA) is a defined commitment to respond to or resolve support requests within a set time, often varying by priority, channel, or customer tier..
SLA Breach
An SLA breach occurs when a support team fails to meet a target defined in a Service Level Agreement — for example, not sending a first response or resolving a ticket within the promised time window..
Business Hours
Business hours are the working schedule a help desk defines — days, times, and time zone — that determines when SLA timers count and when the team is expected to respond..
Ticket Priority
Ticket priority is a field that ranks how urgently a support ticket needs attention — commonly low, normal, high, and urgent — so agents and automations can work the most important issues first..
Escalation
Escalation is the process of moving a support ticket to a higher tier, a specialist, or a manager when the current agent can't resolve it or when it risks breaching an SLA..
Put these ideas to work
Macha is an AI agent layer that sits on top of the help desk you already run — Zendesk, Freshdesk, Front, Intercom, or Gorgias.
Start Trial
Zendesk
Freshdesk
Gorgias
Front
Shopify
Stripe
Slack
Notion
Google Workspace
Confluence