Compensation Claim Check Agent · Use case
How can an airline use an AI agent to check passenger compensation claims on its own infrastructure?
A compensation claim check agent reads one claim for a delay, a cancellation or a missed connection, sets it against the passenger rights rules the company has indexed and the operational record of the flight or service, says which condition the claim meets or fails, with the rule, and drafts the decision note. The claims handler accepts, rejects or pays every claim. The agent decides nothing, pays nothing, offers nothing and sends nothing to the passenger.
The claim takes a minute to read.
The rules and the record take an hour.
- ✗ 01After a disrupted day, claims arrive in their thousands, and each means reading the passenger's papers, the rules that apply to that route, and the record of what happened to that flight.
- ✗ 02Decisions vary from handler to handler, replies fall behind while the queue grows, and a claim wrongly refused becomes a complaint or a case.
Where it stops for a person
Always. The claims handler accepts, rejects or pays every claim.Always. It compares a claim with the rules and the record, it does not judge: whether a cause was outside the company's control, what is owed and what the passenger is told are the claims handler's decisions. A claim that points to an injury, a legal letter or a regulator is marked for a person first. The rules as your legal team has set them out, not the agent's reading, are what the company relies on.
It drafts the decision note.
The claims handler decides.
Step · 01
A claims handler uploads the claim and its supporting papers.
Step · 02
The agent reads what is claimed: the booking, the flight or service, the dates and the amount.
Step · 03
It reads the operational record through your own APIs: scheduled and actual times, the recorded cause, and the notices and rebooking the passenger was given.
Step · 04
It sets the claim against each condition in the rules, citing the rule, and says which it meets or fails and what the record does not show.
Step · 05
It drafts the decision note, and the claims handler decides, edits and sends the reply.
Reads from · connectors
Your own APIs
The claim and its papers, as uploaded files; the flight or service record and the booking, read through your own APIs with the operations that change something left out; and the passenger rights rules, your claims procedure and approved wording, indexed as a knowledge source. No card numbers.
Acts through · MCP servers
Nothing. It accepts no claim, offers no compensation or voucher, makes no payment and sends nothing to the passenger.
What you set up
- Index the passenger rights rules that apply to your routes, as your legal team has set them out, with the claims procedure and approved wording.
- Import the description of the API that holds flight or service records and bookings, and keep only the operations that read.
- Build the agent in Katonic Studio and test it on claims your handlers have already decided.
- Publish it to the claims team, one route group first.
Where it runs
The agent, its knowledge store and the model run on infrastructure you own or control. You choose the model and serve it yourself, so questions, documents and answers are not sent to a public AI service. Claims name passengers, bookings and amounts and stay inside the company.
How you get it today
This page is labelled Use case: the agent is built in Katonic Studio. You describe the job, connect what is named above, add test questions and release the agent once it passes them. When the Catalog holds a tested template for this job, this page will carry the Template label and show how to take it.
Does it accept or reject claims?
No. It sets out which conditions the claim meets or fails, with the rule. The claims handler decides.
Does it pay compensation or offer a voucher?
No. It has no tool that pays or offers anything. Any payment follows your own approval process.
Does it reply to the passenger?
No. It drafts the decision note. The claims handler edits, approves and sends the reply.