AI automation for travel agencies, DMCs and cargo agents in the UAE.

The close stops waiting on the settlement, and every difference is named before anyone goes looking for it.

The BSP settlement, the supplier statements and your own booking records are read as they arrive and matched against what was actually sold, ticketed and refunded.

What agrees closes without anyone touching it, and what does not stops at a person with the line, the booking and the reason attached.

Book a meeting

Thirty minutes. Nothing to prepare.

Or email hello@runbook.ae

The work

Four runbooks for a travel business.

The settlement
Matched as it lands, not at the end of the month.
The BSP file, the airline and hotel statements, your own booking records. They rarely tell the same story, and the difference is found by someone holding the systems open side by side. Every line is matched as it arrives. Only the ones that disagree, the ADM among them, reach a person.
The commission and the refund
Tracked to the booking that created them.
Commission arrives late, in pieces and on somebody else’s terms. A refund can sit in a supplier queue long after the customer stopped waiting for it. Each one is held against its own booking. An override that was never paid, or a refund that never landed, is raised while it can still be recovered.
The itinerary costing
Costed on this season’s numbers, not last season’s.
Net rates from suppliers who each answer differently, allocation that moved since the last cycle, margin one person carries in their head. That is what a group or a series means. The gathering and the assembly run on their own. The margin call stays with whoever owns it.
The booking file
Complete before anyone needs it to be.
The reservation system, the supplier confirmation, the visa or insurance document, the invoice. One booking scatters across all of them, and it only gets assembled when something has already gone wrong. The file is built as the booking moves. The whole story of a passenger, a series or a group sits in one place.
The alternative
Travel software ends at the login.
It holds the booking, and the matching still happens in someone’s head. Runbook arrives knowing your business, because writing down how you actually settle a month is where we start.
What you own
You own it. No seat bill.
It runs in your cloud account. If you stop paying us, it keeps running. What stops is us watching it, fixing it and extending it. The model and the data location are chosen by you and written into the build.
What it has to pass
Nothing goes live until it passes your own hardest cases.
We build the test set from the settlements your team argued about, freeze it before the build, and run it again after every change. It is yours, and another team can be measured on it.

What we get asked

Questions travel and DMC teams ask.

A report tells you the two records disagree. The work is deciding which one is right, and that decision comes from the fare rules, the supplier agreement and what your team knows about this account. Runbook encodes that decision, matches everything that can be matched, and puts only the genuine exceptions in front of a person.
Runbook sits underneath your finance team. The matching, the chase for a statement that has not arrived and the assembly of the exception list stop being that team’s week. The judgment on a disputed line, a write-off or an ADM stays with the finance team, and the close stops being the reason the month runs long.
What differs between two itineraries is the combination, not the work behind it. On every programme the same suppliers are approached for net rates, the allocation is confirmed against what has actually moved, the blackout dates are checked and the replies are chased until they arrive. Runbook runs that, so nothing is quoted against a rate nobody confirmed.
That is the normal starting condition, and it is why the data layer gets built before anything else. A PDF statement, a portal with no export, a rate sheet with the tiers in merged cells and a system nobody has the password to are all inputs we have worked with. The condition of the data changes the sequence of the build, not whether it can be done.
The scope, the fee and the finish date are agreed with you in writing before anything starts. We do not publish a length, because it follows the size of the operation, how many systems the work touches and what condition the data is in.
You do. The code, the credentials and the documentation sit in your accounts and under your name from the day we start. It runs in your cloud account, and if you stop paying us it keeps running.
Nothing. It is thirty minutes with the people who would build it: the job as it runs today, where the line would sit, and what we would measure.
The nouns change and the shape does not. A CASS settlement, a carrier statement and your own job file disagree the same way a BSP settlement and a booking file do. The work is the same: match what agrees, name what does not, and put the decision in front of the person who owns it.