Sort flight compensation claims before a handler reads them
EU261 and UK261. Reads each claim for what happened, who files, what they ask and took instead, receipts and court threats. Your rules decide eligibility.
Try it on this example
Disruption the claimant picked on the form: Delay
Claim text from the web form, email or agency letter
- From the claim's own account, what happened to the passenger's flight?Cancellation100%
- Who is submitting the claim?Claims agency100%
- Does the claim ask for the fixed compensation for the disruption?Yes99%
- Does the claim ask for the ticket price to be paid back?No92%
- Does the claim ask for meals, a hotel, transport or other costs to be paid back?Yes99%
- Does the claim say receipts or other proof of what was paid are attached, offered or kept?No88%
- What does the claim say the passenger did instead of the disrupted flight?Flew on a new flight we arranged99%
- What cause does the claim say the passenger was given for the disruption?Crew100%
- Does the claim threaten a card dispute, a regulator complaint or legal action?Yes99%
- Does the claimant say they have contacted the airline before about this same matter?No89%
- Does the claim identify the flight or the booking well enough for code or a person to find it?Yes99%
These are real answers stored from one run on this example.
The prism behind it
Sort flight compensation claims before a handler reads them
Fields
- Disruption the claimant picked on the form
- Claim text from the web form, email or agency letter
Context
We are an airline flying within Europe and to and from the UK. Passengers and their representatives send compensation claims through our web form, by email and through our agency portal. Each claim is read here when it arrives, before a claims handler opens it. The answers land on the claim record next to the flight operations record. Rule sets: Regulation (EC) No 261/2004 (EU261) on the flights it covers, and the UK version of it (UK261) on the flights to and from the UK that it covers. Code decides which applies. Nothing here decides whether compensation, a refund or expenses are owed. Our claims platform joins each claim to the flight record and applies the rules: the distance, how late the passenger arrived, when a cancellation was announced, and whether extraordinary circumstances apply. A person decides every refusal. What a claimant says about the cause is what they say they were told, not a finding. Nothing here extracts the booking reference, the flight number, names or amounts. The web form and agency files carry them as fields; when a claim gives them only in its text, code or a person finds the booking. Claims arrive in several languages. Answer from the meaning, whatever the language. What the words mean here: - Delay: the booked flight operated but left or arrived later than scheduled. - Cancellation: the booked flight did not operate. A passenger moved to another flight because theirs did not operate had a cancellation, even when the claim calls it a delay. - Denied boarding: the passenger presented for a flight that operated and was refused boarding, for example because it was overbooked. - Downgrade: the passenger flew in a lower class than the one booked. - Missed connection: a late first flight made the passenger miss an onward flight on the same booking. - Compensation: the fixed sum per passenger the rules set for a disruption. - Refund: the ticket price paid back. - Expenses: meals, hotels, transport or other costs the passenger paid during the disruption.
Questions
From the claim's own account, what happened to the passenger's flight? Choice
Use the meanings in the context. Judge from what the claim says happened, not from the disruption picked on the form or the words the claim uses for it; code compares the two.
Who is submitting the claim? Choice
Judge from who writes and on whose behalf. A company that says it acts for passengers under a signed authority is an agency, even when it does not call itself one.
Does the claim ask for the fixed compensation for the disruption? Yes / No
Count a request for compensation under EU261 or UK261, "the 250, 400 or 600 euros", "the 220, 350 or 520 pounds", "the money we are owed for the delay", or similar. Yes: The claim asks for fixed compensation. No: The claim asks only for a refund, expenses or something else.
Does the claim ask for the ticket price to be paid back? Yes / No
Yes: The claim asks for the fare, or part of it, to be refunded. No: The claim does not ask for the fare back. Asking for compensation or expenses alone is No.
Does the claim ask for meals, a hotel, transport or other costs to be paid back? Yes / No
Yes: The claim asks for costs the passenger paid during the disruption to be paid back. No: The claim asks for no costs of this kind.
Does the claim say receipts or other proof of what was paid are attached, offered or kept? Yes / No
Read the claim and any attachment names. Count receipts, invoices, bank statements and order confirmations that are attached, offered, to be sent or kept. Yes: The claim attaches or offers proof of what was paid for at least one item or cost, or says it has been kept. No: No such proof is attached, offered or said to be kept, the claim says there is none, or it claims no costs.
What does the claim say the passenger did instead of the disrupted flight? Choice
Choose what the passenger actually did about the journey. Meal or hotel vouchers given during the wait are care, not an alternative.
What cause does the claim say the passenger was given for the disruption? Choice
Record the cause the claim says staff, messages or the airline gave, or the claimant believes. This is what they say, not a finding; code compares it with the operations record.
Does the claim threaten a card dispute, a regulator complaint or legal action? Yes / No
Count a threat to go to court, issue proceedings, pass the claim to a lawyer, complain to a national enforcement body, the Civil Aviation Authority or an ADR scheme, or dispute the payment with a card company or bank. Yes: The claim makes at least one such threat. No: The claim makes none.
Does the claimant say they have contacted the airline before about this same matter? Yes / No
Count an earlier claim, email, call, chat or reference number we gave about the same flight, by the passenger or by anyone acting for them, however it is put ("this is our second letter"). A reference the claimant or its agency gives for its own file is not earlier contact. Do not count earlier contact about other matters. Yes: The claimant says they, or someone for them, contacted us about this disruption before. No: The claim mentions no earlier contact about this disruption.
Does the claim identify the flight or the booking well enough for code or a person to find it? Yes / No
Count a flight number with a date, a booking reference, or a route with a date and a time. Do not check whether a reference is valid; code does that. Yes: The claim gives enough to find the flight or the booking. No: The claim gives too little, such as only "my flight to Spain last summer".
Lens columns
disruption_type, disruption_type_probability, submitted_by, submitted_by_probability, asks_compensation, asks_compensation_probability, asks_refund, asks_refund_probability, asks_expenses, asks_expenses_probability, receipts_mentioned, receipts_mentioned_probability, alternative_taken, alternative_taken_probability, cause_given, cause_given_probability, dispute_or_legal_threat, dispute_or_legal_threat_probability, repeat_contact, repeat_contact_probability, flight_identified, flight_identified_probability
Run it on your own text
Add this prism in the app, change any question, and test it on a file of your own.