FlightCompensations.com

Preliminary EU261 eligibility check for a booking that itself had a connection or several flights, or whose first airport differs from the disrupted flight's departure. Judges the whole booked journey to its final destination, never one leg in isolation. Returns a verdict (Likely eligible or Likely not eligible), one short reason and, if needed, the one document required next. A point-to-point booking, even one described in a dossier or rerouted, uses check_flight_compensation instead. Computes from the supplied facts only; stores nothing.

analyze_multileg_eu261_scope

For an airline's rejection pasted on its own, without the facts needed for an eligibility check. It does not judge the airline's stated reason: it returns a cautious preliminary verdict until the booking is checked, offers a manual review, and names the one document needed next (the original booking). When the route and disruption are known, use check_flight_compensation instead.

analyze_airline_denial

Checks a postal address with an address-validation service: whether it was found, a corrected or completed version when there is one, and what is missing (for example a postcode or street number). Advisory only; it never blocks a claim and stores nothing.

verify_postal_address

Tells the passenger the one item most likely still needed for a claim about a delay, cancellation, denied boarding, missed connection or baggage problem (for example the original booking, or the airline's cancellation message). Read-only.

check_claim_readiness

Use this when someone asks whether a flight is owed compensation, including questions about notice periods, short delays, extraordinary circumstances, an airline's refusal, or another flight later in the same conversation. It applies the current EU261, UK261, Israeli and Canadian rules, and the answer opens in the FlightCompensations.com claim form at the result card, so the passenger can claim from there. Checks whether a delayed, cancelled or overbooked flight is owed compensation under EU261, UK261, Israel's Aviation Services Law or Canada's APPR, and how much per passenger. Takes the facts in plain words: airports as IATA codes or city names, the airline's name or code, the delay in hours, the cancellation notice in days, or a flight number and date, which is looked up for whatever is missing. When a fact is still needed it returns the one question to ask (needsAnswer). Covers a point-to-point booking (one flight), including one described in a full dossier. Returns a verdict (Likely eligible or Likely not eligible), the estimated compensation per passenger and in total when the rules give one, one short reason and the fee. An airline-imposed move to a different departure airport is assessed as a cancellation of the original route (originAirportChanged=true). For a booking that itself had a connection or several flights, use analyze_multileg_eu261_scope. Computes from the supplied facts only; stores nothing.

check_flight_compensation

Use this when the passenger asks about the status of their FlightCompensations.com claim, with or without its reference. With a reference it returns that claim; without one it returns their most recent claims, newest first, so no reference has to be found first. Only the signed-in passenger's own claims, never another customer's, their documents or internal notes. Read-only.

get_my_claim_status

Looks up a flight's record (route, scheduled and actual times, status) from our flight-data provider by flight number and date. Use it when the route and disruption are known and a time or status is missing, or when the passenger asks for the flight to be checked; with only a flight number and date, open the claim form first. A provider record does not show what the passenger booked, so it never decides which rules apply. Read-only.

look_up_disrupted_flight

Use this when the passenger attaches a booking confirmation, e-ticket or boarding pass. Reads an uploaded booking confirmation, e-ticket or boarding pass (PDF or photo) and returns what it states: flight number, date, route, every passenger's name, the booking reference and the e-ticket number. Fields the document does not show come back empty; nothing is guessed and nothing is stored.

read_booking_document

Use this when someone wants to claim compensation for a delayed, cancelled or overbooked flight or a missed connection, attaches a booking to claim, or opens the app without a question. Opens the FlightCompensations.com claim form in the chat: the passenger finds the flight, sees the eligibility result, answers the claim questions with buttons, signs the Letter of Authorization and submits, all in the form. With no arguments it opens at the first step, finding the flight. With partial facts, every fact passed in is prefilled and the form opens at the first thing still missing; with a flight and what happened it shows the result straight away. Opening it assesses, saves and submits nothing.

start_flight_claim

Creates the passenger's claim with FlightCompensations.com, which then pursues it with the airline, and emails the passenger a confirmation. Use only after a final review that showed the flight, the passengers, the estimated compensation and, separately, the fees: €39 per passenger for the compensation claim and €39 per passenger for each expense, baggage or replacement-travel item, each invoiced separately and only once recovered (the passenger keeps 100% of the compensation; nothing is deducted from it). Expenses need itemized receipts and proof of payment. Requires the passenger's typed SUBMIT MY CLAIM, their answer to whether the flight was already claimed for, a typed signature with their full name, and the boarding pass or booking confirmation (bookingFile). Works without an account. Asking whether a flight is eligible is never consent to submit.

submit_flight_compensation_claim