Your questions.
Clear answers.

Claims and customer-care teams at European airlines and other carriers operating into Europe. Operations, legal, IT and finance teams help assess the fit and the requirements for a pilot.

AI assists with classifying messages, extracting facts, translating and drafting replies. Versioned rules assess the claim. Your authorised team reviews decisions and exceptions; AI does not independently approve compensation, send a response or execute a payment.

Passenger.care fits around your existing claims operation. Your CRM and authoritative flight operations data are the starting point. We map the booking, journey and other case facts needed for your scope, along with approved hand-offs. Additional sources and specific connectors are agreed for the pilot.

EU261 / 2004: Rule development includes different levels of scenario coverage. UK261: Rule development includes different levels of scenario coverage. US DOT: Rules are implemented; the applicable scenarios and rule versions are confirmed for your pilot. Israel: Israeli passenger-rights rules are in development. Vietnam: Vietnamese passenger-rights rules are in development. We agree the claim types, rule versions and airline interpretations for your pilot before operational activation.

Yes. Start with one claim type, a defined evidence path and approved historical or synthetic cases. Agree the baseline and success measures first, then use the findings to decide whether to extend the pilot.

Passenger.care supports fully on-premises deployment, including local AI models. Passenger data stays within your organisation and is not sent to external AI providers. Approved external flight, weather and NOTAM data can be brought in without sending passenger data out. An isolated deployment uses locally available or approved imported evidence.

Passenger Care supports preparing, reviewing and handing off finance instructions. Your authorised payment system executes the transfer. A successful hand-off is kept separate from confirmation that funds have settled.

This website is for airline teams evaluating software. Passengers should use their airline’s official claims channel. Please do not send passenger records or booking documents through this website.

Passenger Care is in development and testing for airline adoption. We have not yet agreed a production deployment with an airline. A pilot is intended to validate a specific workflow, its integrations and its operating requirements.

Commercial terms depend on the workflow, expected volume, integrations, deployment requirements and support scope. A first conversation defines these inputs; pilot and wider implementation terms are agreed separately.

Yes. The proposed approach combines software with hands-on help defining the workflow and reviewing the results. Any ongoing operational support is scoped separately, with clear responsibilities and data-use terms.

Yes. Passenger.care is EU AI Act Ready and GDPR Ready. The platform combines local processing options, controlled access, versioned rules, traceable decisions and human oversight. Deployment-specific policies, responsibilities and operating requirements are defined with your airline.

Yes. Passenger.care supports multiple airlines and outsourcing organisations in one system, with access tied to assigned roles and work. Each airline can maintain its own workflows, language capabilities and review responsibilities.

Yes. Configure airline-specific workflow stages, responsibilities and approval paths, and connect them to your existing systems. Operational workflows and legally reviewed rule profiles are versioned and governed separately.