The back office for every traveller claim.
CADB Solutions reads each traveller claim, gathers the booking, the flight data and the law, and drafts the reply. Then it stops. A named manager decides.
- A named manager approves every outcome
- EU, French, German and UK package-travel law
- Replies in the traveller's own language
- Identifiers removed before any AI sees them
Everything a decision needs, on one screen.
| Destination | Claim | Status |
|---|---|---|
| Crete | Flight 4h12 late | To approve |
| Puglia | Room not as booked | Drafted |
| Corsica | Boat excursion cancelled | Info requested |
| Lisbon | Charged twice | Sent |
Example claim. Sample data, not a customer case.
The Reclamations Desk shows the queue, the law applied, the evidence and both texts side by side, with one bar to decide. French first, also in English.
How it works
Intake
The claim arrives in your existing mailbox. Its message and PDFs are read, the booking reference, dates, travellers and request are pulled out, and the language is detected.
- Tied to its claim by an explicit reference, never guessed from headers
- Understands “dossier”, “forfait”, “séjour”, “circuit” and “croisière”
- Traveller identifiers replaced before any AI model sees the text
Evidence
Before a word is drafted, the booking is matched and the facts are checked: flight data for delays and cancellations, official weather records and Météo-France alerts for storms.
- Lookups send a flight number and a date, never a traveller's name
Law and drafts
The applicable law is found in a curated corpus: the Package Travel Directive with French, German and UK layers. Two texts follow: an analysis for your team and a reply for the traveller.
- Cites only the law it holds; weak grounding raises a flag
- The reply is written in the traveller's language
Decision
A named manager is told the claim is ready, then approves it, edits it, asks the traveller for more, or rejects it. Nothing leaves and no money moves before that.
- Notified by email, Slack or Teams
- Compensation is decided by the manager, never by the AI
Record and remember
The decision is written to an audit trail with the manager's name. How your team decided becomes precedent for the next similar claim, with personal details removed.
- A claim can wait days for a decision without being lost
- A follow-up after closing opens a linked case; the decision stays as made
Traveller data, kept to a minimum.
- Each operator's data is isolated by the database itself, with PostgreSQL row-level security
- Identifiers are replaced before any text reaches an AI model
- Evidence lookups carry no traveller names
- Personal data is encrypted at rest
- An append-only audit trail names the person behind every decision
- Nothing reaches a traveller without a named manager's approval
- A new operator is a configuration, not custom code
No ISO 27001 or SOC 2 certification is claimed at this stage.
Join the pilot
The first operators shape what comes next.
CADB Solutions runs end to end on a staging server and is being demoed. We are looking for the first tour operators to pilot it on their own claims.
A call
We learn how your team handles claims today.
Your setup
Your mailbox, booking data, languages and jurisdictions, set up by configuration.
Real claims
The system prepares, your managers decide every outcome.
Review together
We look at the results with you. No figures are published before the pilot measures them.
Pilot pricing on request.
The legal corpus is under review by a jurist. Commercial availability follows that review; a supervised pilot does not wait for it.