CADBSolutionsJoin the pilot
Chart of the example claim's route to Heraklion, CreteA route crosses the Sea of Crete through Intake at 09:14, Evidence at 09:15, Law at 09:15, Draft at 09:16 and lands at Heraklion: Decision, Waiting for the manager. Nothing has been sent.09:14Intake09:15Evidence09:15Law09:16DraftDECISIONnowWaiting for the manager.Nothing has been sent.

Every claim prepared. Every decision yours.

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

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.

  • Strikes
  • Cancellations
  • Storms
  • High season
  1. 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
  2. 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
  3. 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
  4. 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
  5. 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

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.

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.

Join the pilot

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