Corporate travel booking software: self-booking and the agent desk on one platform

1. Two booking channels, one corporate account

A corporate account books in two ways. Employees self-book the simple trips: a return flight, a hotel near the office, an airport transfer. The TMC's agents handle the rest: multi-city trips, groups, VIPs, visas and anything that goes wrong.

When those two channels run on separate systems, the same traveller has two profiles, the same policy is configured twice and the same trip can exist in two places. Every change on one side needs a person to copy it to the other. The self-booking tool works on its own terms, but the account as a whole doesn't.

2. What corporate travel booking software has to cover

Strip away the demo and the list is short:

• Policy enforcement: rules by designation, department, route or budget, applied while the employee is searching, not in an email after the booking.
• Approvals: chains by cost centre, amount or trip type, with delegation when an approver is away.
• Content: flights across GDS, NDC and LCC, plus hotels and transfers, with the company's negotiated fares and hotel deals surfaced first.
• People data: profiles, departments, cost centres and approvers kept in sync with HR, so routing doesn't break after every reorganisation.
• Duty of care: knowing who is travelling where, and reaching them when plans change.
• Reporting: spend, negotiated-rate usage and out-of-policy bookings by cost centre, supplier and traveller.

None of this is unusual. What separates tools is whether it all holds together when the agent desk gets involved.

3. Corporate travel policy enforcement belongs in the search results

Policy that only shows up at checkout teaches employees to work around it. Good corporate travel policy enforcement shows the rule in the results: an out-of-policy fare is hidden, flagged with a reason, or allowed with a justification the approver can read.

There is a subtle second requirement. The same policy must apply when an agent books for that employee. If the agent desk can't see the corporate policy, the TMC either books out of policy without knowing or keeps a separate rulebook in a spreadsheet. Both defeat the point of writing the policy in the first place.

4. Why the agent desk and self-booking should share records

When the corporate self-booking tool and the agent desk run on the same records:

• A trip an employee started can be picked up by an agent without re-keying.
• Policy, approvers and negotiated rates are configured once for the account and apply on both sides.
• The travel manager sees one list of trips, not two exports to merge.
• Reports cover everything the company booked, whichever channel it came through.

This is also an integration question. If both channels draw content through one unified travel API, a fare or hotel looks the same to the employee and the agent, and adding a supplier doesn't mean integrating it twice.

5. Changes and disruptions: where separate tools break

Booking is the easy part. The hard part is what happens after: an airline moves a flight, a meeting shifts by a day, a traveller misses a connection.

Involuntary schedule change handling is a good test. When the airline changes the schedule, someone has to notice, check whether the new timing still works and offer alternatives. If the trip was self-booked in one tool and the agents work in another, that change can sit unseen until the traveller is at the airport.

On one platform the change lands on the same trip record the agent desk already uses. The traveller gets an alert, the agent sees the same trip and the travel manager knows who is affected. That's duty of care in practice, not as a slide.

6. Questions to ask a corporate travel booking software vendor

• Does the agent desk see the same corporate policy, approvers and negotiated rates as the self-booking tool, or are they configured separately?
• Can an agent take over a self-booked trip without rebuilding it?
• Is policy shown in the search results, and can a rule be hard, soft or justification-based?
• How are profiles, departments and approvers kept in sync with HR?
• Which flight channels (GDS, NDC, LCC) and which other verticals are in the self-booking tool itself?
• When an airline changes a schedule, who is alerted, the traveller, the agent or both, and where does the change show up?
• Do the reports cover agent-booked and self-booked trips together?

If the answers depend on a nightly sync between two products, you're buying two products.

7. Where Orbit fits in the Elkanio suite

Orbit is Elkanio's corporate travel booking software: a self-booking tool employees can use on mobile, a hard and soft policy engine, multi-level approval chains, profiles and cost centres synced from HR, negotiated airline and hotel deals preferred by policy, and duty-of-care visibility of who is travelling where.

For a TMC, each corporate account on Nucleus can get its own Orbit policy, approvers, cost centres and negotiated rates. Self-booked trips land on the same desk and reports as the ones your agents make. Content comes through Synapse, the unified travel API behind the suite, and schedule-change alerts and staff replies run through Pulse so the travel manager stays informed.

Orbit doesn't have to be day one. Many TMCs start with the agent desk and add Orbit as corporate clients ask for self-booking. Corporate travel offices can start with Orbit directly.

Bring your corporate travel policy and a sample of last quarter's trips. We'll show how Orbit and the agent desk would have handled them. Request an Orbit walkthrough.