OBT vs TMC
OBT vs TMC is the division of work in a managed travel programme: the OBT (online booking tool) is the software where travellers book within policy, and the TMC (travel management company) is the service company that configures it, tickets and services the bookings, and manages the client relationship.
How the work is split
Think of it as a split of responsibilities. The OBT handles search, the display of policy, the approval workflow, traveller profiles and the booking itself. The TMC loads the client's negotiated fares and hotel rates, sets up the policy rules, issues tickets under its accreditation and runs quality control on each booking.
When something goes wrong, such as a cancellation, a complex multi-city trip or a visa problem, the TMC's agents take over. Reporting usually draws on both: the OBT records what was booked and why, and the TMC adds invoiced spend, refunds and unused tickets.
Why the split matters
Getting the split wrong is a common reason corporate travel programmes underperform. A good OBT without a capable TMC leaves travellers stuck during disruption; a strong TMC behind a clumsy OBT drives calls to the agent desk, which costs more per trip. Buyers should ask who owns traveller data, who is accountable for duty of care, and how quickly the TMC can change the OBT's configuration when policy changes.
Example
A traveller books a two-city trip in the OBT, which applies policy and collects approval. The TMC's mid-office checks the fare and issues the ticket. When the second flight is cancelled overnight, the TMC desk rebooks it and updates the trip in the OBT so the traveller sees the change on their phone.
Related terms
Where this fits in altovo
altovo's TravelDesk is the OBT side: TMCs license it white-label to put their own brand on the booking tool, and companies can also license it directly. Build vs buy for corporate travel software covers the TMC's choice, and the travel policy engine guide covers the rules.