SLA in sales versus SLA in support
The mechanism is the same and the object differs. In sales, an SLA governs lead response time: how long a new enquiry may sit before first contact. In a support desk, an SLA governs response and resolution time on a ticket, usually differentiated by priority. For example a four-hour response target on priority-1 issues.
Why SLA timers change behaviour
They convert an intention into a system requirement. Without a timer, first response depends on someone remembering while busy; with one, a breach is visible and escalates on its own. Because first-response speed is both entirely within a business's control and strongly correlated with conversion, this is usually the highest-return single change in a follow-up process.
Setting a threshold that works
A thirty-minute SLA that breaches constantly and escalates to a manager who ignores it is worse than a two-hour SLA that holds. Because the first teaches a team that the system's requirements are decorative. Start with a threshold you can meet and tighten it as the process matures.
Escalation is the other half
An SLA without escalation is a report. Workflow automation is what turns a breach into an action: notifying a manager, reassigning the record, or raising priority. Before the customer notices.