SLA Breach and Service-Credit Calculator Prompt
Compute customer-facing SLA impact after an incident — downtime windows, affected tenants, breached commitments, and owed service credits — and draft a defensible, contract-aligned breakdown.
- Target user
- SREs, support leads, and account teams quantifying SLA impact post-incident
- Difficulty
- Intermediate
- Tools
- Claude, ChatGPT
The prompt
You are an SRE who works closely with the contracts and support teams to translate raw incident impact into accurate, defensible SLA-credit numbers. I will provide: - The SLA terms (uptime commitment, measurement window, exclusions, credit schedule, claim process) - The incident's confirmed impact window(s) and which components/regions were affected - Tenant/customer mapping (who runs on which affected components) - Any maintenance windows or excluded conditions that may apply Your job: 1. **Establish the measured window** — clarify how the SLA defines uptime (per-minute, per-request, rolling 30-day vs calendar-month) and compute the denominator precisely. State your assumptions explicitly. 2. **Bound the impact** — determine the exact start and end of qualifying downtime per affected component, distinguishing full outage from partial degradation, and note where the data is uncertain. 3. **Apply exclusions correctly** — check each candidate exclusion (planned maintenance, customer-caused, force majeure, third-party) and document why it does or does not apply. Do not silently exclude to lower the number. 4. **Map to affected tenants** — produce a per-customer impact view: which customers were affected, for how long, and against which tier of their commitment. 5. **Compute credits** — apply the contractual credit schedule per customer, showing the math (achieved availability vs target → credit percentage → credit amount). Round per the contract's rules. 6. **Flag edge cases** — multi-region customers, customers below the claim threshold, customers who must proactively claim vs auto-credited, and any commitment already partially consumed this period. 7. **Draft the customer-facing breakdown** — a clear, honest summary per affected customer suitable for support to send, plus an internal ledger for finance. Output as: (a) the availability math with stated assumptions, (b) an exclusions analysis, (c) a per-customer impact and credit table, (d) an edge-case flag list, (e) a customer-facing credit summary template. Bias toward: honesty and defensibility over minimizing payout, explicit assumptions over hidden ones, contract language over guesswork.
Run this prompt with AI
Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.
Related prompts
-
Incident Degraded-Mode Customer Tradeoff Prompt
Decide which features to intentionally shed to keep core service alive during an incident, and frame that tradeoff for customers and the business
-
Vendor SLA Accountability Review Prompt
Review a vendor-caused or vendor-involved incident to determine SLA breach, remedies owed, and corrective commitments to demand
-
Incident Acknowledgment SLA Compliance Audit Prompt
Audit how reliably your on-call program meets page-acknowledgment and first-response SLAs, find where the clock is slipping, and design enforceable targets per severity.
-
Customer Impact Assessment During an Active Incident Prompt
Rapidly quantify who and what is affected during a live incident — segments, transactions, revenue, and SLA exposure — so severity, comms, and prioritization are grounded in real blast radius rather than gut feel.
More Incident Response prompts & error guides
Browse every Incident Response prompt and troubleshooting guide in one place.
Reading prompts? Get all 500 in one free PDF
500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.
- 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
- Instant PDF download — yours free, forever
- Plus one practical AI-workflow email a week (no spam)
Single opt-in · unsubscribe anytime · no spam.