Chapter 04 / 10
04 / Use what already works
Use what already works.Connect only what we need.
We would build around the travel relationships and business systems PIVOT already uses. Our team would confirm their roles, secure the right access and connect the systems needed for a complete booking. Keep what works. Add what's missing.
Build around the systems you already use.
EXAMPLE 04We connect the services behind the booking
PIVOT / T2C
Keep the booking and the customer relationship with PIVOT
Flights through to ticketing
Validate search, booking, ticketing and servicing access
First-launch connection
Payments and refunds
Agree who charges the card and receives the money
First-launch connection
Build around Nexion and Concur
Confirm their roles with PIVOT and the travel partner
Map at kickoff
Keep customer records together
Connect to PIVOT’s chosen main customer system
Map at kickoff
Keep useful hotel and ground options
Keep useful room blocks and booking links
Later, unless needed at first launch
Experiences later
PIVOT chooses the partners. Agree availability and refunds
I wouldn’t build this first
Our connection checks: approved access, test bookings and a clear support handoff before launch.
This is our connection plan for the systems named in your RFP and strategy. We would confirm access, responsibilities and test bookings before activating each connection.
Connect the full booking, not just fares
Our provider checks cover search, ticketing, cancellations and traveler support. Every step matters.
Don't replace it just because we can
Let's understand Playbook 365, your hotel links, Concur and Nexion before changing them.
Use fares we can actually book
Copying fares from a website isn't enough. We need an approved provider that can confirm the price and issue the ticket.
Let’s talk through the details
Here’s how we would deliver it.
Our response to your requirements.
For flights, we would start with PIVOT's existing ticketing and agency relationships. Our team would confirm a provider can support search, current prices, bookings, tickets and servicing. An approved booking connection gives us more than copied fares from a website.
For hotels, we would check room blocks, commissions and cancellation support. For ground travel, we would check coverage, reservations and help.
Provider selection remains open. We would review terms, costs, connection limits and support with PIVOT, then validate the choice through test bookings.
We would work with PIVOT to confirm Nexion's role in booking and ticketing, permitted fees or markups, traveler support and commission payments.
That review gives us a practical connection plan: what T2C can handle directly, what stays with your travel partner and which access we need. The specific connection and terms remain to be agreed.
Some of your travel may already belong in Concur. We wouldn't move it without a reason. First decide what stays there and which T2C booking details it needs.
Then check what Concur allows us to send or receive, and where the official records should live. That tells us whether we need a simple handoff, shared reports or a deeper booking connection.
We would connect to the system PIVOT chooses for its main customer records. Both are options; we would only connect both if there is a clear business need.
Our team would map the organizations, contacts and booking updates that need to move, protect access, prevent duplicate records and retry failed updates safely. We would agree that mapping and secure access before building the connection.
Issuing a flight ticket is part of the first working booking. Event tickets and local activities are different. We would add those later.
PIVOT should choose where those experiences come from. We need to check availability, commissions and refund terms with your approved partners before selling them.
Keep useful Playbook 365 programs, hotel links and room-block relationships. There's no reason to rebuild something that already works.
Before connecting anything, we would walk through how a booking moves between your travel team, payment provider, ticketing partner, finance team and customer records. Then decide what needs to change and whether any existing information needs to move.
Based on: Strategy §§5, 19–21, 24 · RFP APIs & solutions
