SLA Breach Communication Writer
The SLA Breach Communication Writer generates professional, transparent communications for situations where your team has missed a service level agreement. It produces breach notification messages, root cause explanations, remediation plans, and follow-up communications that acknowledge the failure honestly while preserving the customer relationship and demonstrating accountability.
Support managers handling escalations, account managers communicating service failures to enterprise clients, and operations leads who need to notify multiple stakeholders about a breach use this template. It covers the full communication arc: the initial acknowledgment, the detailed explanation, the remediation offer, and the follow-up that confirms the issue is resolved and preventive measures are in place.
The prompt works because SLA breach communication is high-stakes writing where tone, timing, and specificity determine whether the customer relationship survives. Generic apologies ("We apologize for the inconvenience") damage trust further. This prompt forces you to provide specific details about what happened, why it happened, and exactly what you are doing to prevent it from happening again, which is the only communication approach that rebuilds credibility after a service failure.
This prompt is just the starting point
Score it with AI, optimize it with one click, track versions, and build your prompt library.
The Prompt
Write SLA breach communications for the following situation: **Customer**: [CUSTOMER NAME AND CONTEXT, e.g., "Acme Corp, Enterprise plan ($8K/month), 2-year customer, primary contact is VP of Operations"] **SLA That Was Breached**: [SPECIFIC SLA COMMITMENT, e.g., "P1 tickets: first response within 15 minutes. Guaranteed 99.9% uptime monthly.", "Delivery within 5 business days of order confirmation"] **What Actually Happened**: [THE FACTS, e.g., "P1 ticket sat unassigned for 2 hours and 14 minutes due to a routing error in our helpdesk system. Customer's production environment was down during this time."] **Root Cause**: [WHAT WENT WRONG AND WHY, e.g., "An automation rule was misconfigured during a helpdesk migration last week. Tickets tagged as 'infrastructure' were routed to a deprecated queue that no agent monitors. QA on the migration missed this edge case."] **Impact on Customer**: [BUSINESS IMPACT, e.g., "Customer's e-commerce checkout was down for 2+ hours during peak traffic. Estimated revenue loss of $15K based on their average hourly volume."] **What Has Already Been Done**: [ANY IMMEDIATE ACTIONS TAKEN, e.g., "Issue was resolved within 30 minutes of discovery. Routing rule has been fixed. All deprecated queues have been audited."] **SLA Remediation Terms**: [YOUR CONTRACT TERMS FOR BREACHES, e.g., "10% service credit for each SLA breach", "No contractual penalty but customer expects proactive communication", "Penalty clause: customer can terminate with 30 days notice after 3 breaches in a quarter"] **Communication Channel**: [HOW TO DELIVER THIS, e.g., "Formal email from our VP of Customer Success", "Slack message in shared customer channel followed by email", "Phone call followed by written summary"] Generate the following communications: ### 1. Immediate Acknowledgment A brief, honest message to send within the first hour of the breach being identified: - Acknowledge the breach directly (no hedging or minimizing) - State what you know so far - Commit to a timeline for the full explanation - Provide a direct contact for questions - Keep it under 150 words ### 2. Detailed Breach Report A thorough follow-up communication (send within 24 hours): - **Subject line**: Clear, professional, no corporate jargon - **Opening**: Direct acknowledgment of the breach with specific SLA metric and actual performance - **Timeline of Events**: What happened, when, in chronological order - **Root Cause**: Honest explanation of why this happened (not "technical difficulties" but the actual reason) - **Customer Impact**: Acknowledge the specific business impact to the customer - **Immediate Actions Taken**: What has already been fixed - **Preventive Measures**: 2-4 specific steps being taken to prevent recurrence, with timelines for each - **Remediation**: Any service credits, compensation, or contractual actions being applied - **Next Steps**: When the customer will hear from you next and who their point of contact is - **Closing**: Accountability statement from a named person (not "the team") ### 3. Internal Incident Brief A summary for internal stakeholders (account team, management, engineering): - What happened and the business risk - Customer relationship context (how important this account is, current satisfaction trajectory) - Remediation cost - What needs to change in process or tooling - Who owns each follow-up action ### 4. Follow-Up Communication (7 Days Later) A message to send one week after the breach: - Confirm all preventive measures have been implemented - Share any relevant metrics showing improved performance since the incident - Reiterate commitment to the SLA - Offer a brief check-in call if the customer wants to discuss further ### 5. Talking Points If the customer escalates or wants a call: - 5-7 bullet points covering key messages to convey - 2-3 questions the customer is likely to ask, with prepared answers - What NOT to say (phrases that make it worse: "It was an isolated incident", "Our systems are usually very reliable", "This has never happened before")
Usage Tips
- Be specific about root cause: "A misconfigured routing rule" is credible. "Technical difficulties" is not. Customers can tell when you are being vague, and vagueness after an SLA breach signals either incompetence or dishonesty. The more specific your input, the more credible the output.
- Include the customer's business impact: Saying "we understand this affected your checkout flow during peak hours" shows you grasp the real cost, not just the technical failure. This detail transforms a generic apology into a communication that demonstrates accountability.
- Send the immediate acknowledgment fast, even if incomplete: The first message does not need to explain everything. It needs to arrive quickly and show that you know there is a problem. Silence after a breach is worse than an incomplete update.
- Use the internal brief to drive process improvement: The internal incident brief is not just for documentation. Bring it to your next operations meeting and assign owners to each preventive measure. Unowned action items do not get done.
- Keep the 7-day follow-up on your calendar: Most teams send the apology but forget the follow-up that proves things are better. The follow-up is what actually rebuilds trust, because it shows the remediation was not just words.
Get more from this prompt
Save it, score it with AI, optimize it, and track every version. Free to start.