TravelDesk Feature Map

NDC and traditional (EDIFACT) airline content, including one-way combinable fares and single or split PNR construction.

Clients book flights, hotels, and packages on a branded site; the booking is held, not ticketed, until policy and approval clear.

950+ airlines through GDS connections (Amadeus, Travelport, Sabre) — no separate GDS work for you to set up.

1M+ hotels through the Core Engine supplier network.

Load each client's negotiated flight fares and hotel rates, configured per client.

Each client gets its own flight, hotel, and package configuration, so you can segment inventory by client.

An optional consumer-leisure storefront (flight, hotel, and bundle search) — fully separate from the corporate side.

A single partner account can own multiple corporate clients, with one login to manage them all.

Every client gets its own web address out of the box (e.g. client.traveldesk.altovo.io) — no DNS work per client.

Each client sees its own logo, colours, and sign-in page text — the portal looks like theirs, not yours.

Set each client's default currency and language.

Provision new clients, switch a client off instantly if ever needed, and track go-live readiness with a built-in checklist.

Each client's admins manage their own employee list — add individuals, upload a spreadsheet, or send invites.

A client runs TravelDesk on its own domain (e.g. travel.client.com) alongside its default address — adding a custom domain doesn't remove the original.

The client points their domain at a single address you provide (e.g. ingress.traveldesk.altovo.io). Standard "bring your own domain" process.

Every custom domain gets its security certificate issued and renewed automatically — no manual certificate work.

Generate separate branded addresses (company1.brand.com) under a custom-domain partner.

Users stay signed in whether they're on the default address or the client's own domain.

Your agency is a core part of the product. Both internal teams (your staff inside a client) and external TMCs (running your own book of business) are supported.

A client must grant you permission before you can see their trips — you can request access, but never give it to yourself. Permission can cover the whole client, a department, or a single traveller.

Combine the client's permission with optional limits per agent, so each of your consultants sees only the clients and trips they handle.

Work trips across every client you serve from a single screen — no switching between logins.

Your consultants book using the traveller's details and trip, not their own — so every booking is made on the traveller's behalf.

A permission you can hold agency-wide or per agent, letting you approve trips that fall outside policy — on the client's terms.

Each client picks the servicing style that suits them: full self-service, auto-approve in-policy trips, review your proposals, or route approvals to their managers or travellers.

You always know which trips are yours to handle, with a straightforward handoff between traveller, approver, and your desk — nothing gets lost between people.

Your consultants can work the desk from a phone — a thumb-reach layout with a bottom tab bar, not a shrunk-down desktop screen.

Employees book on the branded site and the Core Engine holds the PNR. Nothing is ticketed until policy and approval clear — low risk for clients.

Managers approve, reject, or reverse requests from a dedicated queue, with a short window to reverse a rejection.

Managers can approve or reject from any device via a one-time email link — no need to sign in.

A manager can hand approvals to a colleague for a set period (e.g. while away).

An employee can name a travel arranger (such as someone in your agency) to book on their behalf.

Bookings that can't be matched to an employee land in a queue for an admin to assign.

Each employee keeps a personal profile — contact details, preferences, and identity fields — that pre-fills their bookings so trips are quicker and cleaner.

Store a passport plus up to three frequent-flyer and five hotel-loyalty memberships per traveller, ready to attach to bookings.

Bookings can require the details they need up front, so trips don't stall later for a missing passport or contact.

Each client sets its billing and invoicing details once; they flow through to the Core Engine invoice automatically.

Every booking is checked against the client's rules the moment it's made — no manual review needed for in-policy trips.

Flight class, hotel rate cap, flight rate cap, advance booking notice, and carrier rules — all configurable per client.

Caps and limits flex automatically by the employee's grade, plus route and destination — so one rule set covers the whole client. Department drives who approves rather than the caps themselves.

Policies are versioned — clients can see exactly what changed and when.

In-policy bookings can be approved and sent for ticketing automatically — no manager in the loop.

A per-client threshold (default 5%) checks the re-quoted price against the approved price before settlement.

Once switched on, each approved booking is re-priced, validated against the approved trip, and moved through to ticketing automatically — with a human safety net available (below).

Before any money is taken, the pipeline confirms the price hasn't moved and the booking still matches what was approved.

If the price, availability, or itinerary shifts, the booking is routed to the right person (approver, traveller, or your operations team) instead of failing silently.

If an automated booking stalls, it's handed to a real person to confirm — so nothing falls through the cracks.

Switch on end-to-end automatic payment when you're ready — no manual settlement step.

Payments settle against the agent credit balance held in the Core Engine.

Bookings about to lapse are flagged, and in-policy ones can be auto-approved before they expire — no lost bookings to TTL timeouts.

Every user signs in with a verified account; each client is its own closed user group.

Admins invite each employee by email; no one can self-register. Best for tight control.

Employees join automatically using their work email, limited to approved email domains.

Employee, manager, and admin roles — each sees only what they need. Manager authority follows the client's reporting lines.

Manage all your clients and their trips from one login.

Automatic rate limiting protects clients from misuse.

Spend charts by airline, cost centre, department, destination, product, and employee, plus a spend trend and a compliance summary.

A filter bar with date presets and reset, over both summary and detailed data.

Export buttons on the reports page for offline analysis.

Portal usage analytics to see how travellers use the site. No end-user tracking consent is required (B2B legitimate-interest basis); internal admin traffic is excluded from measurement.

Each client's data is walled off — a user in one client can never see another client's data.

Booking data arrives over signed channels that can be rotated with zero downtime.

Passport numbers, phone numbers, and dates of birth are encrypted when stored.

Every action — approvals, changes, cancellations — is recorded in a database-enforced, insert-only audit log with who, what, and when.

The system prevents conflicting actions, so two people can't approve and cancel the same booking at once.

If a credential ever leaks, the exposure is limited to a single client.

All flights, hotels, and packages come through the altovo Core Engine.

Trip, approval, and reminder emails sent automatically to travellers and approvers.

Runs on managed cloud infrastructure with automatic scaling.

Fast loading worldwide through a global content network.