CADB SolutionsJoin the pilot

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.

Claim And Don't Blame. For European tour operators, France first.

Reclamations DeskExample claim. Sample data, not a customer case.

ARV-77310

Crete, 7-night package, flight and hotel

To approve
  1. Intake09:14
  2. Evidence09:15
  3. Law09:15
  4. Draft09:16
  5. Decisionnow
TravellerFrench09:14
« Bonjour, notre vol aller pour Héraklion est arrivé avec plus de quatre heures de retard et nous avons perdu la première soirée de notre forfait… »
carte-embarquement.pdf
Evidence
+4h12 Flight data confirms arrival 4h12 late
Law
Directive (EU) 2015/2302 and Code du tourisme applied

Analysis Internal

Outbound flight 4h12 late, confirmed by flight data. First evening of the package not provided. Basis: Directive 2015/2302, Code du tourisme. Confidence: high.

Reply FR

Madame, Monsieur, nous vous remercions de votre message et sommes sincèrement désolés pour le retard de votre vol aller…

Decision: manager [name]

Waiting for the manager. Nothing has been sent.

How it works

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.

  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

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.

Example claim. Sample data, not a customer case.

One queue, sorted by what needs you first

The law applied and the evidence on every claim

Analysis and reply kept apart: only the reply can leave

One decision bar, with your name on it

Agents

  • Claims arrive already investigated and drafted
  • Ask the traveller for what is missing
  • Send the approved reply from your mailbox

Managers

  • Approve, edit or reject from one desk
  • Hold the authority over money
  • Approve in their own signed-in session, never by a forwarded link

Traveller data, kept to a minimum.

Security
  • 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.

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

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