Atlas Knowledge
Back to search
Customer SupportUpdated 1/1/2026·2,871 views

SLA Breach Communication

Quick answer

Notify the customer within 30 minutes of any SLA miss with root cause and ETA.

Full procedure

  1. 1Review the SLA Breach Communication standard on the department portal before you begin.
  2. 2Confirm you have the required access, PPE, or tooling for the task.
  3. 3Notify the customer within 30 minutes of any SLA miss with root cause and ETA.
  4. 4Complete each step in sequence — do not skip or reorder.
  5. 5Record completion in the system of record (log, ticket, or checklist).
  6. 6Escalate any deviation from the standard through the escalation path.
  7. 7Debrief the team lead at handoff on anything unusual.

Common mistakes & exceptions

  • Skipping the WMS/system logging step — every action must have a system record.
  • Not photographing exceptions before escalating.
  • Assuming verbal approval is enough — always capture the ticket or form ID.

Escalation path & subject matter expert

Escalate to
Customer Support Shift Lead
Ext. 4128 · Slack #customer-support
Subject matter expert
Priya R. — Customer Support

Frequently asked questions

Required forms

  • SLA Breach Communication Log
    CS-412

My private notes

slabreachmisscommunicationcustomer supportproceduresopatlas

Revision history

  1. 2026-01-01
    Version 2.0 republished by Meera Iyer.
  2. 2025-10-15
    Reviewed for annual compliance.
  3. 2024-11-04
    Initial publication.
Was this helpful?
Your feedback improves the knowledge base.