SLA breaches cost $10K+ per incident in contractual penalties — and they happen silently because nobody tracks the clock until it's too late. Manual SLA monitoring in spreadsheets misses 30% of at-risk tickets until the breach is already incurred.

Utilyx models SLA management as an executable workflow: every ticket carries a live SLA timer, predictive alerts fire at 80% of the deadline, and escalations route to the right manager automatically.

The workflow is structured as a decision tree with 4 branches (Priority 1/P2/P3/P4 SLA tiers) and 6 steps end-to-end. Each step is executed by a named actor (SLA engine, sql-query, email service, Escalation manager, Technician, Service owner) and every action is timestamped.

• Step 1 (Start — SLA engine): when a ticket is created, the SLA engine assigns a target_resolution_time based on the priority × impact matrix (P1: 4h, P2: 8h, P3: 24h, P4: 48h) and starts the clock. Fields: ticket_id, sla_tier, target_resolution, paused_during_business_hours flag.

• Step 2 (sql-query): the engine runs a periodic SQL query (every 5 min) against the ticket store to compute elapsed_time / target_resolution ratio per open ticket and flag those crossing the 50%, 80% and 95% thresholds.

• Step 3 (Routing): four conditional branches — Branch A (P1 at 80%): immediate email to IT manager + technician, Slack ping via call-connector, war-room channel auto-created; Branch B (P2 at 80%): email to team lead + technician; Branch C (P3 at 95%): email to technician only; Branch D (P4 at 95%): dashboard flag, no individual notification (low cost of breach).

• Step 4A (email): the escalation email includes ticket context, elapsed time, remaining time, current assignee and a one-click reassign link. The email module sends in the recipient's preferred language.

• Step 5A (Escalation manager): if the ticket still breaches, a post-mortem task is created on the Escalation manager's queue with root-cause fields (breach_reason, contributing_factors, preventive_action). The ticket is flagged 'SLA breached' and the penalty cost is recorded for the monthly SLA report.

• Step 6A (Closure): on resolution, the SLA engine computes the actual resolution time vs target, stores the variance in the sla_metrics table via sql-query, and feeds the monthly SLA compliance dashboard.

Teams that adopt Utilyx report SLA breach rate cut from 18% to under 3%, $10K+ penalties per breach avoided through predictive alerts at 80% of the deadline, and zero manual SLA tracking because the sql-query engine computes every timer in real time.

The 4-tier escalation routing matches each priority to the right level of urgency, the multilingual email module serves global teams without translation overhead, and the SLA variance data feeds directly into contractual reviews — no separate reporting tool required.