Join the pilot

CADB Solutions

Same claim, same answer, whoever opens it.

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.

Join the pilotSee a claim decided

For European tour operators, France first

Claim And Don't Blame

  1. Art. 1 A named manager approves every outcome.

    see Art. 8, 10, 13

  2. Art. 2 EU, French, German and UK package-travel law.

    see Art. 7, 11

  3. Art. 3 Replies in the traveller's own language.

    see Art. 5, 7

  4. Art. 4 Identifiers removed before any AI sees them.

    see Art. 5, 15

Book I

Book I. How it works

Today, the answer depends on who opens the claim.

The booking sits in one system, the flight record in another, the weather nowhere, and the law in someone's head. Two people give two answers to the same complaint.

And claims never arrive one at a time. A strike, a cancelled flight or a storm in high season brings a whole departure into the inbox at once.

  1. Art. 5 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.

    1. Tied to its claim by an explicit reference, never guessed from headers.
    2. Understands “dossier”, “forfait”, “séjour”, “circuit” and “croisière”.
    3. Traveller identifiers replaced before any AI model sees the text.

    see Art. 3, 4, 7

  2. Art. 6 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.

    1. Lookups send a flight number and a date, never a traveller's name.

    see Art. 16

How it works

  1. Art. 7 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.

    1. Cites only the law it holds; weak grounding raises a flag.
    2. The reply is written in the traveller's language.

    see Art. 2, 3, 5

  2. Art. 8 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.

    1. Notified by email, Slack or Teams.
    2. Compensation is decided by the manager, never by the AI.

    see Art. 1, 10, 13

  3. Art. 9 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.

    1. A claim can wait days for a decision without being lost.
    2. A follow-up after closing opens a linked case; the decision stays as made.

    see Art. 13, 18

Claim and don't blame.

The same facts and the same law are gathered for every claim, so the same case gets the same answer. Every decision carries the name of the manager who made it, and the record cannot be rewritten.

see Art. 1, 2, 6

Book II

Book II. The Desk

Everything a decision needs, on one screen.

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.

  1. Art. 10 One queue, sorted by what needs you first.

    see Art. 1, 8, 13

  2. Art. 11 The law applied and the evidence on every claim.

    see Art. 2, 7, 12

  3. Art. 12 Analysis and reply kept apart: only the reply can leave.

    see Art. 7, 11

  4. Art. 13 One decision bar, with your name on it.

    see Art. 1, 8, 9

The Desk

Example claim. Sample data, not a customer case.
CaseMatterStatus
CreteFlight 4h12 lateTo approve
PugliaRoom not as bookedDrafted
CorsicaBoat excursion cancelledInfo requested
LisbonCharged twiceSent

ARV-77310Waiting for the manager. Nothing has been sent.

Book III

Book III. Security

Traveller data, kept to a minimum.

  1. Art. 14 Each operator's data is isolated by the database itself, with PostgreSQL row-level security.

  2. Art. 15 Identifiers are replaced before any text reaches an AI model.

    see Art. 4, 5

  3. Art. 16 Evidence lookups carry no traveller names.

    see Art. 6

  4. Art. 17 Personal data is encrypted at rest.

Security

  1. Art. 18 An append-only audit trail names the person behind every decision.

    see Art. 9, 13

  2. Art. 19 Nothing reaches a traveller without a named manager's approval.

    see Art. 1, 8, 10

  3. Art. 20 A new operator is a configuration, not custom code.Note

No ISO 27001 or SOC 2 certification is claimed at this stage.

Schedule

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.

  1. A call

    We learn how your team handles claims today.

  2. Your setup

    Your mailbox, booking data, languages and jurisdictions, set up by configuration.

  3. Real claims

    The system prepares, your managers decide every outcome.

  4. 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.

Join the pilot

Join the pilot

This form is not connected yet, so nothing is sent.