Travellinx normalizes voice-captured trip intent into one schema, then routes each component — air, hotel, ground transport, private aviation — to the supplier system best equipped to fulfill it. We're building the connector layer now, and looking for partners to build it with.
Rather than building a one-off integration for every category, Travellinx converts voice-captured trip intent into a standardized internal schema once — then routes each component to whichever connected system, or human task queue, is right for it.
Advisor-led or AI-first voice capture converts a live trip request into structured intent — destination, dates, party size, preferences — regardless of channel.
Each trip component is matched to the system built to fulfill it: GDS for air and hotel, dedicated APIs for ground transport, an advisor task queue for anything outside standard connectivity.
Supplier-specific responses come back into one unified advisor workflow — a consistent review surface no matter how many systems were queried underneath it.
Layer 4 is where a new supplier integration lives. It sits between trip-matching logic above it and the advisor's review screen below — added without touching either.
Travellinx doesn't ask you to change how your system authenticates, settles, or reconciles. We route into it.
Wherever a supplier system requires agency-owned credentials — a Sabre PCC, an Amadeus Office ID — Travellinx routes through the agency's own account. Permissions stay scoped to the minimum actions the workflow needs.
Travellinx is designed to coordinate transactions, not intermediate them. Where your system permits it, settlement, refund processing, and accreditation stay exactly where they are today.
Bookings land directly in your native queue — PNRs, reservations, confirmations. Back-office accounting, invoicing, and commission workflows continue unchanged.
Every new supplier — GDS, ground transport, accommodation, private aviation — is treated as a connector to the same normalized trip schema, so your integration doesn't get rebuilt every time we add a category.
Traveler profiles can contain passport data, loyalty IDs, and sensitive service history. Partner systems should know exactly where our scope starts and stops.
Payment details are never taken by voice. Real-time-billed suppliers — ground transport, private aviation — receive payment through a tokenized entry method, not spoken numbers, keeping live calls out of PCI-DSS scope.
Card data is tokenized at the point of capture through a PCI-compliant gateway. Travellinx's own systems never store or transmit raw PAN or CVV.
Raw voice audio is not persistently stored unencrypted. Only the data required for workflow, audit, and customer-approved retention is kept.
Traveler data is encrypted and segregated per agency, with explicit ownership boundaries — one agency's data is never visible to another's.
GDS, accommodation, and ground-transport credentials live in an auditable, rotated secret-management layer, kept apart from traveler-profile data.
Travellinx is in active development. If your platform touches air, hotel, ground transport, private aviation, or advisor tooling for the luxury travel channel, we'd like to understand your API and figure out where it fits in the schema.
No integration is live today — we're sequencing GDS first, ground transport close behind. Early conversations shape what gets built next.