Skip to content
ObligaAI

SLA leakage

Claim the service credits you have already earned.

ObligaAI compares service performance with the SLA terms in your contracts, helping your team identify missed targets and review potential credits before they expire.

April availability

99.4%

Target 99.9%

Credit due$1,000

MetDegradedOutage
Claim within 30 days

Try it on your contracts

See what is leaking in your own contracts.

Start free, bring a few real agreements and see what ObligaAI finds before you change anything about how you work.

  • Free to start, no credit card
  • Works beside the tools you already use
  • Your team approves every finding

Start your free trial

No credit card required

By signing up, I agree to ObligaAI's Terms and Conditions.
Please also see ObligaAI's Privacy Statement.

Claim window

A valid credit can still expire.

Service credits often come with a limited claim period. Move the slider to see how a missed deadline affects the credit.

18days left
12
  1. Month endsDay 0
  2. Report arrivesDay 4
  3. Breach flaggedDay 5
  4. Claim sentDay 9
  5. Window closesDay 30

$1,000 credit still claimable. 18 days remain.

Illustrative example based on a 30-day claim window.

What ObligaAI catches

Credits are earned automatically and claimed almost never.

Follow a contract through its four stages. The number on each stage is how many things typically go wrong there. Pick one, or step through them.

01

Commit

The service levels and credits are agreed, along with the carve-outs that limit them.

1 thing typically leaks here

Exclusions misapplied

Maintenance and force majeure carve-outs checked against the clause.

e.g.Planned maintenance counted against uptime it should be excluded from.

Trace the credit

The SLA was missed. Was the credit claimed?

01 / 04

What the SLA requires

The contract requires 99.9% availability and provides a 5% service credit when performance falls below the agreed threshold.

Contract · SLA99.9 % target
Report · Month99.4 % actual
Invoice · Fee$20,000 billed
$1,000service credit due · SLA-0422

Illustrative example with sample figures.

Timing

The same problem, found at two different moments.

  1. 1

    A month passes below target

  2. 2

    The report is filed and nobody compares it

  3. 3

    The claim window quietly closes

  4. 4

    The credit is lost

Found months later. Recovered in part, if at all.

How the check runs

Three kinds of record go in. One answer comes out.

  • Contracts and SLA schedules
  • Service reports and tickets
  • Monthly invoices

ObligaAI
match

  • The clause and the breach
  • The credit due in dollars
  • The date to claim by
SLA leakage, in detail: technical details
Matches against
Contracts, SLA schedules, service reports, ticket exports and invoices
Clause types
Availability, response and resolution times, credit rates, exclusions, claim windows and caps
Match streams
Report to SLA, ticket to SLA, credit to invoice
Tolerance
Set per contract, with exclusions and measurement periods applied as written
Output
The clause, the breach, the credit due, its dollar value and the date to claim by

Your clauses, interpreted

Service levels, read the way your contract means them.

ObligaAI turns service-level and credit clauses into plain-language obligations with a confidence score and a link to the exact passage. Low-confidence readings go to a person first.

  • Works beside your tools. Reads contracts and service reports from where they already live.

  • Advisory first. A breach is flagged with the clause attached. You decide what to claim.

  • Deadlines tracked. Every claim window is calendared so earned credits are not lost to timing.

Schedule 5 · Service levels

Services agreement

The Provider shall maintain monthly availability of at least 99.9%. If availability falls below this level, the Customer is entitled to a credit of 5% of the monthly fee, provided it is claimed within 30 days.

ObligaAI reads

Availability below 99.9% in a month earns a 5% credit on that month's fee, but only if it is claimed within 30 days of the month ending.

Confidence

High · owner to confirm

Questions, answered.

Where does the service data come from?

From the reports and ticket exports your suppliers already send you. ObligaAI reads them against the SLA in the contract.

Does it claim credits for us?

No. It shows the breach, the clause and the amount, and reminds you of the deadline. Your team makes the claim.

What if a credit clause is ambiguous?

It is marked low confidence and sent to a person to confirm before anything is flagged as a breach.

Find the difference before it is paid.

Start with a few contracts of your own. See your baseline in days, then turn it into controls that run every day.