MSA: SLA & Remedies — Service Levels and the Credit Trap
On this page
SLA-REMEDY
The SLA Trap
"99.9% uptime" sounds like a real commitment. It is a real commitment — to a remedy worth a fraction of one month's fee, claimable only if you file within 30 days of the incident, applicable only to platform availability and not to AI feature quality. The SLA uptime guarantee is real. What it is worth is defined by the remedy clause, not the headline number.
How It Works
A standard SLA designates service credits as the exclusive remedy for downtime. UCC § 2-719(1)(b) permits commercial parties to make a specified remedy exclusive, and most SLAs do exactly this:
"Service credits are Customer's sole and exclusive remedy for any failure by Vendor to meet the Service Level Commitments set forth in this SLA."
The credit formula typically produces a recovery of a small fraction of one month's fee:
| Uptime achieved | Credit (typical) |
|---|---|
| 99.0%–99.9% | 10% of monthly fee |
| 95.0%–99.0% | 25% of monthly fee |
| Below 95.0% | 50% of monthly fee |
For a $200K/year contract ($16,667/month), a qualifying outage at the worst tier generates a credit of $8,333. If that outage caused a day of lost operations — customer-facing downtime, employee productivity loss, emergency response costs — the credit is likely a small fraction of the actual harm.
[UCC § 2-719(1)(b), https://www.law.cornell.edu/ucc/2/2-719 (parties may agree that a remedy is exclusive; if expressly agreed to be exclusive, it is the sole remedy).]
The 30-Day Claim Window
Most SLAs require the customer to submit a credit request within 30 days of the incident. This window is easy to miss:
- During an outage, your team is focused on remediation, not paperwork
- The credit request process often requires technical documentation of downtime duration
- The 30-day window runs from the incident date, not from when the incident is resolved
- Missing the window typically waives the credit entirely — most SLAs contain a "no credits for claims submitted outside the request window" provision
If the outage caused losses an order of magnitude above the credit amount, those losses are also excluded as consequential damages under the MSA. You have no recourse outside the SLA remedy.
The AI Version
AI features are typically excluded from SLA coverage in two ways.
First, most SLAs define "downtime" as the platform being fully unavailable or unavailable above a threshold error rate. AI feature degradation — the model producing lower-quality outputs, slower response times, increased hallucination rates — does not meet the definition of "downtime." The platform is up. The AI is underperforming. No credit applies.
Second, some vendors explicitly exclude AI features from SLA coverage:
"The Service Level Commitments in this SLA do not apply to: (a) AI Features, (b) Beta features, or (c) features that Vendor identifies as experimental or subject to change."
AI features, beta features, and experimental features often overlap significantly. If the AI functionality your company has integrated into its workflows is classified as any of these, the SLA provides no remedy when it fails.
Both Sides of the Table
If you're the buyer:
- Read the "exclusive remedy" language in the SLA — confirm that service credits are not your only recourse for outages that cause business-level harm.
- Extend the credit request window to 60 or 90 days — the standard 30 days is operationally unrealistic during an incident.
- Push for AI features to be covered under the SLA, or negotiate a separate AI availability commitment with financial teeth.
- If the vendor won't move on the SLA remedy, make sure the consequential damages exclusion in the MSA has a carve-out for major outages or data incidents.
If you're the vendor:
- The service credit structure is your risk management mechanism — predictable, capped, actuarially priced.
- The 30-day window protects against long-tail claims; extending it to 60 days has minimal financial impact but improves customer goodwill.
- Excluding AI features from SLA coverage is defensible for early-stage AI functionality; it becomes a negotiating liability as AI features mature into core product.
The Pattern Signal
The SLA trap co-occurs with:
- The Illusory Protection — the SLA commitment is the warranty; the service credit is the exclusive remedy. Same structure as the warranty-remedy mismatch in the main MSA.
- The Liability Cap and consequential damages exclusion — the credit is your remedy inside the SLA; business losses from the outage are excluded outside it.
- The 30-day window — a procedural Silence Trap: failure to file within the window waives the credit, even if the underlying outage was real and documented.
MSA: The SLA Trap
The SLA Trap
"99.9% uptime" sounds like a real commitment. It is a real commitment — to a remedy worth a fraction of one month's fee, claimable only if you file within 30 days of the incident, applicable only to platform availability and not to AI feature quality. The SLA uptime guarantee is real. What it is worth is defined by the remedy clause, not the headline number.
How It Works
A standard SLA designates service credits as the exclusive remedy for downtime. UCC § 2-719(1)(b) permits commercial parties to make a specified remedy exclusive, and most SLAs do exactly this:
"Service credits are Customer's sole and exclusive remedy for any failure by Vendor to meet the Service Level Commitments set forth in this SLA."
The credit formula typically produces a recovery of a small fraction of one month's fee:
| Uptime achieved | Credit (typical) |
|---|---|
| 99.0%–99.9% | 10% of monthly fee |
| 95.0%–99.0% | 25% of monthly fee |
| Below 95.0% | 50% of monthly fee |
For a $200K/year contract ($16,667/month), a qualifying outage at the worst tier generates a credit of $8,333. If that outage caused a day of lost operations — customer-facing downtime, employee productivity loss, emergency response costs — the credit is likely a small fraction of the actual harm.
[UCC § 2-719(1)(b), https://www.law.cornell.edu/ucc/2/2-719 (parties may agree that a remedy is exclusive; if expressly agreed to be exclusive, it is the sole remedy).]
The 30-Day Claim Window
Most SLAs require the customer to submit a credit request within 30 days of the incident. This window is easy to miss:
- During an outage, your team is focused on remediation, not paperwork
- The credit request process often requires technical documentation of downtime duration
- The 30-day window runs from the incident date, not from when the incident is resolved
- Missing the window typically waives the credit entirely — most SLAs contain a "no credits for claims submitted outside the request window" provision
If the outage caused losses an order of magnitude above the credit amount, those losses are also excluded as consequential damages under the MSA. You have no recourse outside the SLA remedy.
The AI Version
AI features are typically excluded from SLA coverage in two ways.
First, most SLAs define "downtime" as the platform being fully unavailable or unavailable above a threshold error rate. AI feature degradation — the model producing lower-quality outputs, slower response times, increased hallucination rates — does not meet the definition of "downtime." The platform is up. The AI is underperforming. No credit applies.
Second, some vendors explicitly exclude AI features from SLA coverage:
"The Service Level Commitments in this SLA do not apply to: (a) AI Features, (b) Beta features, or (c) features that Vendor identifies as experimental or subject to change."
AI features, beta features, and experimental features often overlap significantly. If the AI functionality your company has integrated into its workflows is classified as any of these, the SLA provides no remedy when it fails.
Both Sides of the Table
If you're the buyer:
- Read the "exclusive remedy" language in the SLA — confirm that service credits are not your only recourse for outages that cause business-level harm.
- Extend the credit request window to 60 or 90 days — the standard 30 days is operationally unrealistic during an incident.
- Push for AI features to be covered under the SLA, or negotiate a separate AI availability commitment with financial teeth.
- If the vendor won't move on the SLA remedy, make sure the consequential damages exclusion in the MSA has a carve-out for major outages or data incidents.
If you're the vendor:
- The service credit structure is your risk management mechanism — predictable, capped, actuarially priced.
- The 30-day window protects against long-tail claims; extending it to 60 days has minimal financial impact but improves customer goodwill.
- Excluding AI features from SLA coverage is defensible for early-stage AI functionality; it becomes a negotiating liability as AI features mature into core product.
The Pattern Signal
The SLA trap co-occurs with:
- The Illusory Protection — the SLA commitment is the warranty; the service credit is the exclusive remedy. Same structure as the warranty-remedy mismatch in the main MSA.
- The Liability Cap and consequential damages exclusion — the credit is your remedy inside the SLA; business losses from the outage are excluded outside it.
- The 30-day window — a procedural Silence Trap: failure to file within the window waives the credit, even if the underlying outage was real and documented.
mail Subscribe to MSA: SLA & Remedies — Service Levels and the Credit Trap email updates
Primary sources. No fluff. Straight to your inbox.