HOW IT WORKS
See how Passenger.care brings the case, flight evidence, rules and reviewer together — and keeps each next action connected to its decision.
Follow an illustrative caseINSIDE PASSENGER.CARE
This is the actual flight decision review screen. An operator can inspect the proposed outcome, see the linked claims and identify passenger exceptions before approving the next step.
Development UI with synthetic test data. Figures and outcomes are examples, not customer results or a live eligibility assessment.
See the flight, proposed outcome and reasons together.
Separate shared flight facts from passenger-specific circumstances.
Return the proposal for more work or send it through the defined approval path.
Collect what the reviewer needs.
Bring the relevant claim, flight and operational context together. Keep the source of each fact clear. Your airline’s authoritative records and approved mappings determine what the workflow can rely on.
A result you can trace back.
Structured assessments identify the rule version, facts and reasoning behind an outcome. Missing inputs and unsupported scenarios stay visible for further review.
Put responsibility at the right point.
An authorised person reviews the common flight assessment. Where configured, independent approval adds a second set of eyes. The decision retains its evidence and version history.
Use common context with care.
Apply the reviewed flight context to ordinary claims while keeping passenger-specific circumstances on a separate review path. Changes to relevant evidence can trigger reassessment.
Keep the decision connected to the action.
Prepare reviewed communication and finance instructions through their defined approval paths. Preserve acknowledgements and reconcile uncertain delivery outcomes.
DEPLOYMENT & CONTROL
Passenger.care supports fully on-premises operation, including local AI models. Passenger data stays within your organisation. External operational evidence can come in without passenger data going out.
Run in an isolated environment using local evidence, or bring in approved flight, weather and NOTAM feeds. External enrichment does not require sending passenger records to those providers.
Controlled model routing, input and output validation, access restrictions and human approval keep AI assistance separate from claim decisions and financial authority.
Trace decisions to evidence and versioned rules. Define access, review responsibilities and data-handling policies for your deployment, with human oversight throughout the workflow.
See the controls to demonstrate in your pilot
YOUR PROCESSES & SYSTEMS
Configure airline-specific process stages, responsibilities and approval paths. Versioned workflows keep each case connected to the process that governs it; legally reviewed rule profiles are managed separately.
Your CRM and authoritative flight operations data are the integration starting point. Booking, journey and other case-specific facts may be available through those systems or require an additional source. We map the required facts and hand-offs for your pilot.
Weather and NOTAM data provide supporting evidence. Missing or conflicting facts remain visible for review.
AIRLINES, PARTNERS & JURISDICTIONS
Manage multiple airlines and outsourcing organisations in one system, with access tied to assigned roles and work. Define each airline’s workflows, language capabilities and review responsibilities.
Multilingual communication can follow your airline’s tone, terminology and local communication standards. Language and model quality are evaluated for the tasks in scope.
RULE COVERAGE
Agree the claim types, rule versions and airline interpretations before operational activation.
European passenger rights
Scenario coverage variesRule development includes different levels of scenario coverage.
For your pilot: Agree the claim types, evidence and applicable rule versions for your operation.
UK passenger rights
Scenario coverage variesRule development includes different levels of scenario coverage.
For your pilot: Confirm the UK rule package and airline interpretation for the cases in scope.
Aviation Consumer Protection
ImplementedRules are implemented; the applicable scenarios and rule versions are confirmed for your pilot.
For your pilot: Confirm which US DOT scenarios apply to your routes and workflow before activation.
Aviation Services Law
In developmentIsraeli passenger-rights rules are in development.
For your pilot: Discuss the required scenarios and availability before including this jurisdiction in a pilot.
Passenger rights
In developmentVietnamese passenger-rights rules are in development.
For your pilot: Discuss the required scenarios and availability before including this jurisdiction in a pilot.
WHAT WE AGREE BEFORE A PILOT
Define the on-premises environment, local AI models, access permissions and approved inbound evidence sources for your airline.
Define legal review, airline interpretation, evidence ownership and the approval roles for the workflow.
Map your source systems and hand-offs. Test the expected results and failure cases before operational use.
A CLEAR NEXT STEP
Let’s find a useful starting point for your airline.
