The operational workflow
Persisted booking and offer records, separate purchase and cancellation consent, partner roles, supplier exception handling and an illustrative financial ledger.
Product & pilot scope
Explore what the prototype demonstrates today, and the work needed before a live traveller programme.
Persisted booking and offer records, separate purchase and cancellation consent, partner roles, supplier exception handling and an illustrative financial ledger.
Facts linked to source lines, conflicting or missing evidence flagged for investigation, and a saved operator assessment. The interactive mode uses a deterministic parser.
An optional model connection and evaluation harness are implemented locally. Live model performance, source accuracy and time savings have not been measured.
All booking checks, programme binding, cancellation execution, payments and payouts in the demonstrations are fictional. No live cover is issued.
Supported supplier access, a contracted risk arrangement, approved product terms, payment integration and production operational controls. None is implied by the demo.
A proposed path to a pilot
Map a recent cancellation, the systems involved, the costs and the decision-makers.
Choose supported bookings and define authority, failure handling, funding and success criteria.
Use evidence from the sandbox to decide whether to contract a limited paid pilot, revise the proposition or stop.
No. It uses a fictional booking and stores its steps only in your browser session.
No live cover or guarantee is available through this website. The product structure, provider responsibilities and terms must be agreed before any live pilot.
The local MVP has a proposed partner API and hosted checkout pattern. A real connection requires supported access, the supplier’s specification, testing and a commercial agreement.
The proposed model role is evidence extraction. Traveller approval, eligibility rules, arithmetic and servicing controls remain separate. Human review is required.