The contract is signed. There is cake in the office and a congratulatory email from the founder. A new corporate client with two thousand travellers is coming on board.
Three weeks later, the mood has changed. A senior director's booking failed because his passport details were never loaded. A sales team booked business class because the travel policy was set up wrong. Twenty invoices went to the wrong cost centre, and the client's finance team has noticed.
None of these problems are dramatic on their own. Together, they make the travel manager quietly wonder whether she chose the right partner.
Why the first weeks matter so much
Corporate clients do switch. In a GBTA survey of 786 travel buyers and industry professionals, 30% said they planned to re-evaluate or change their travel management company, with service quality among the top reasons.
Every switch means a new implementation. And the first impression a client forms of your service is not your sales pitch. It is how well their first fifty trips go.
A smooth onboarding buys you goodwill for years. A messy one becomes the story the travel manager tells at every review meeting. The difference is rarely talent or technology. It is preparation, careful checking and enough hands at the right moment.
What usually goes wrong
Most onboarding problems are not technology failures. They are data and process problems:
- Incomplete traveller profiles: missing passport details, loyalty numbers or seat preferences.
- Policies loaded incorrectly: wrong cabin rules, hotel caps or approval thresholds.
- Approvers and cost centres out of date, taken from an old spreadsheet.
- Billing set up the wrong way: invoices to the wrong entity, address or reference.
- Travellers not told what changes, so they keep calling the old provider.
Each of these is easy to prevent and expensive to fix after the first booking.
Start with a clean data handover
The single most useful thing you can do is agree exactly what data the client will provide, in what format and by when. A short template saves weeks of back-and-forth.
At a minimum, ask for:
Traveller data: full names as on passports, employee IDs, departments, contact details and loyalty numbers.
Policy rules: cabin classes by trip length, hotel rate caps by city, advance booking rules and exceptions.
Approval structure: who approves whom, and what happens when an approver is away.
Billing set-up: legal entities, cost centres, project codes and invoice delivery preferences.
Our process handover checklist covers the same thinking for any process, and is a useful companion here.
Load it, then check it
Loading data is quick. Checking it is what protects the relationship.
Before the first live booking, check a sample of every data type against the source. Open twenty traveller profiles and compare them field by field. Run test bookings against the policy: one that should be approved, one that should be blocked and one that should trigger an exception. Generate a test invoice and send it to the client's finance team for confirmation.
These checks take a day or two. They prevent the kind of mistakes that take months to forget.
As an illustration, imagine a client with 2,000 travellers where just 5% of profiles have a passport detail wrong. That is 100 people who could face a failed booking, a check-in problem or a missed flight. Finding them in a sample check before go-live takes hours. Finding them one complaint at a time takes months, and every one of them remembers whose service let them down. Our guide to data entry quality checks explains how to set simple field rules that catch errors before they reach a traveller.
Plan the first 60 days, week by week
A clear plan keeps both teams calm. A simple structure works for most clients:
Weeks 1–2: collect data, load profiles and policies, run test bookings and confirm billing.
Weeks 3–4: go live with a pilot group, such as one department or office, and review every booking.
Weeks 5–6: roll out to all travellers, with daily checks on profiles and policy exceptions.
Weeks 7–8: hold a joint review, fix recurring issues and send the first monthly report.
Starting with a pilot group is the key step. Problems show up in twenty careful bookings instead of two thousand rushed ones. It also gives you a group of early travellers who can tell their colleagues that the new service works. Our 30-day pilot plan offers a similar structure for any new process.
Talk to the travellers, not just the travel manager
The travel manager signed the contract. The travellers decide how it feels.
Send a short, friendly welcome note before go-live: how to book, who to call, what changes and what stays the same. Keep it short enough to read on one phone screen. Follow up after their first trip with a short two-question survey, and act quickly on anything it reveals.
Make the first interaction easy, and make sure the team answering it already knows the client's policy and key travellers. A traveller who gets a fast, correct answer on their first call becomes a supporter. Our customer support playbook covers how to set response standards that hold up, even during a busy launch.
Measure the onboarding itself
Track a few numbers during the first 60 days and share them with the client:
- Profile completeness: the share of travellers with every required field filled.
- Booking errors: bookings that needed correction because of data or policy issues.
- Invoice accuracy: invoices accepted by the client's finance team without changes.
- Traveller contact rate: how often travellers needed help to complete a booking.
Sharing these numbers openly builds trust, especially when they improve week by week. If a number gets worse, say so first and explain the fix. Clients forgive problems far more easily than surprises. When the first monthly report arrives, make it one the client actually reads. Our guide to the monthly travel report clients actually read shows how.
Who should do the onboarding work?
Your account manager should own the relationship, the kick-off meeting and the joint reviews. The work behind it is different: cleaning and loading hundreds or thousands of profiles, setting up policies, checking samples, running test bookings and preparing reports. That work is detailed, time-bound and often arrives exactly when your existing team is busiest.
Dhiti supports corporate travel and hotel businesses with back-office operations, data and profile management, accounts and finance, reporting and sales support, with more than 200 trained specialists. If your next client launch needs extra hands, we would be glad to help you get the first 60 days right.
Examples and suggested targets are illustrative, not Dhiti client results or contractual commitments. Adapt the approach to your process, risk and team.



