Mid-Office for Travel Agencies

In the Voraal stack, mid-office work for corporate programmes is anchored in GTOS. The travel team works in Control Tower on the same live trip record the client sees in the Client Portal and the traveller sees in My Mobility. Rezencia is there for reservations and sales. Folio6 is there for accounting and revenue intelligence, which is the usual destination of a mid-office handover. GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips.

What mid-office work looks like on the trip

A mid-office queue is not a single action. It includes:

- Quality checks before a ticket is issued, or before a change is released.

- Issuance itself, including automatic issuance of approved, in-policy corporate bookings, and specialist handling of complex trips.

- Changes, disruptions and after-hours work, with 24/7 operations around the record.

- Visa, document, group and meetings cases that need more than a standard ticket.

- A clean handover of cost, invoice and receipt data toward finance.

Control Tower is the operations view for that work: every trip and request, VIP, visa, group and meetings handling, and response-time tracking. Because the record is shared, the consultant is not waiting for a forwarded confirmation, and the client's finance team is not waiting for a reconstructed file.

Auto-issue is part of mid-office design, not a way around it. Routine, already-approved, in-policy trips should not occupy a person. The queue should hold the work that needs a person. See auto-issue and Control Tower.

What this page does not claim

Mid-office conversations often move quickly to named reservation systems and content sources. We do not publish a list of certified GDS, NDC or other supply badges on this page, and we do not invent connectors. If your agency depends on a particular supply path, that is a question for a demo, answered only with what is actually available.

Avunzo is a B2B travel API designed to connect travel content and booking flows to your own channels. It is not yet live on production. Early access is available on request. It should not be read as a live mid-office supply feed today.

Rezencia and Folio6 should be read as the reservations and accounting products around the mid-office, not as a claim that every agency process is already automated end to end.

Why clients feel the difference

Clients may never use the word mid-office. They feel the result: a change that already knows the trip, a spend view that includes the reissue, a duty of care map that shows the new routing, and a desk that does not ask them to repeat the file. That is why mid-office on a shared record is part of delivering a corporate-standard programme, not only an internal efficiency topic.

Each client company sees only its own data, with access by role. Two-step sign-in is available on the app. We do not claim certifications we do not hold. GTOS is built to scale to 1,000+ employees per client. USD is the main currency on this site; spend can be recorded in more than one currency. Pricing is in USD and available on request.

Frequently asked questions

Is GTOS itself a complete mid-office for every agency model?

It is the operations layer for corporate programmes run in Control Tower, on a shared trip record. Reservations and accounting are addressed by Rezencia and Folio6. Your exact mid-office path should be mapped in a demo.

Does auto-issue remove the need for mid-office staff?

No. It reduces the need for people to issue routine, in-policy, already-approved trips, so staff can concentrate on changes, exceptions and complex work.

Can mid-office staff see all clients at once?

They work in Control Tower with access by role, and each company's data is held separately. The right access model for a multi-client desk is part of implementation, not a public mixed view of every account.

Mid-office for travel agencies, on a shared trip record