Macha
Helpdesk Concepts

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.

Also known as: SLA rulesservice-level policySLA target

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.

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