How corporate travel managers search for ground transport — and what to publish for them

Most of the enquiry volume on a chauffeur site comes from someone booking their own car. Most of the account value sits with someone booking on behalf of other people — a travel manager, an EA, a procurement officer, an event planner. Across the accounts I look at, this second group is maybe 3-4% of impressions and can be 40% or more of annual revenue once a company is on the account books. It is a different search, asked in a different language, and it almost never shows up if you only wrote your site for the person booking a wedding car.

This article is about that second group: who they are, the exact phrases they type, and the documents your site needs to publish so that when procurement runs a search — or, increasingly, asks an AI assistant to shortlist suppliers — you are one of the names that comes back.

Who is actually doing the searching

"Corporate booker" is not one person. On the accounts I have supported in London, Sydney, New York and Dubai, the search behaviour splits into four fairly distinct roles, and each wants a different answer before they will pick up the phone.

• Travel manager or head of travel. Runs an RFP, compares two or three suppliers on paper, cares about SLA, insurance limits, sustainability reporting and consolidated billing. Searches with company-policy language: "preferred supplier ground transport", "duty of care taxi policy UK".
• Executive assistant or PA. Books reactively, often outside office hours, cares about reliability and how fast a human answers. Searches urgently and locally: "chauffeur service open now Mayfair", "can I book a car for 6am tomorrow".
• Procurement. Joins late in the process, cares about contract terms, VAT invoices, payment terms, insurance certificates and whether you'll sign their supplier agreement rather than yours. Rarely searches Google at all — they search your website once they have your name, looking for the document that proves you're real.
• Event or roadshow planner. Books multi-vehicle, multi-day jobs — product launches, conference shuttles, film unit moves. Searches for capacity and coordination: "multi-vehicle transport roadshow UK", "crew transfer chauffeur company".

Notice that none of these four ever type "limo hire" or "chauffeur near me". They also rarely use your brand adjectives — "luxury", "premium", "bespoke" — because those words don't answer a procurement question. They use terms lifted from their own company's travel policy and from the RFP template they've filled in a dozen times before.

The actual phrases, and why each one matters

I pull these from Search Console query reports on corporate-facing pages, and from the RFP documents operators forward to me for review. The phrasing is remarkably consistent across the UK, US, Australia and UAE, adjusted for local licensing terms.

• Preferred supplier / approved supplier — they want to know if you already work with companies like theirs, and whether you'll appear on a shortlist rather than be sourced ad hoc.
• Duty of care — a legal and HR term, not a marketing one. They need a written policy on driver vetting, vehicle safety and what happens if a passenger doesn't arrive.
• DBS check / driver vetting (UK), background check (US/AU) — specific, checkable, expected in writing, not "our drivers are fully vetted professionals".
• PHV licence / TfL licensing (UK), livery / TLC / limousine permit (US), state PHV licence (AU), RTA permit (UAE) — jurisdiction-specific licensing terms procurement checks against a register.
• Employers' liability / public liability limits — they want the £ or $ figure, not the word "insured".
• SLA / KPI — on-time percentage, cancellation notice period, how a delay or no-show is handled and credited.
• On-account invoicing / consolidated monthly billing — no card payment per trip; one invoice a month, ideally split by cost centre.
• VAT invoice / tax invoice — a document requirement, often the first thing procurement checks your site for before a call.
• Cost centre reporting — the ability to code trips to departments so finance can allocate spend.
• Roadshow / crew transfer — multi-vehicle, multi-day, often cross-city, coordinated by one point of contact rather than booked trip by trip.
• RFP / tender — the formal process; searched almost always alongside a deadline, e.g. "ground transport RFP template response".

The pages and documents to actually publish

A consumer-facing homepage answers none of this, and burying it in a PDF nobody can find defeats the point — procurement and travel managers search your site before they email you, and if the document isn't indexable they assume it doesn't exist. Publish these as real pages, not attachments buried three folders deep.

• Account terms page — on-account eligibility, invoicing cycle, payment terms, minimum monthly spend if any.
• Duty-of-care statement — driver vetting process, vehicle maintenance schedule, incident and escalation procedure, named contact for account queries.
• Insurance and licensing page — actual figures and licence numbers, not "fully licensed and insured", with jurisdiction called out (PHV/TfL in London, TLC in New York, state licensing in Australia, RTA in Dubai).
• SLA and KPI page — on-time percentage over the last 12 months if you'll stand behind it, cancellation window, how delays are credited.
• Roadshow and multi-vehicle capability page — fleet size available same-day, coordination process, examples of past multi-city or multi-day jobs.
• Sample invoice — a redacted real one showing VAT/tax treatment, cost-centre coding and line-item detail. This single page converts procurement better than almost anything else on a corporate site, because it answers the question they were about to email you to ask.
• Passenger data and GDPR page — how booking data, addresses and flight details are stored and who can access them; increasingly asked for directly in RFPs, especially from EU and UK-headquartered clients.
• Sustainability / EV fleet page — EV and hybrid share of the fleet, emissions-per-trip if you track it, because many corporates now need this figure for their own ESG reporting and won't award an account without it.

Structuring an RFP-ready page

Most RFP responses are still built by copying answers out of a Word template into a portal, one field at a time. You cannot skip that process, but you can cut the time it takes by having every answer already published and stable on your own site, so whoever fills in the tender is copying from your account terms page rather than reconstructing the figures from memory.

The page itself should read like a specification, not a pitch: company registration details, fleet size and vehicle classes with capacity, insurance figures with policy type, licensing by jurisdiction, driver vetting process, SLA figures, invoicing and payment terms, escalation contact, references available on request. Skip the adjectives entirely here. A travel manager scoring a tender is working through a checklist, and a page that reads like one scores faster and more favourably than a page that reads like marketing copy.

A downloadable capability statement

Alongside the page, keep a single PDF capability statement — two to four pages, same content condensed, dated on the cover so it's obviously current. Procurement and travel managers forward this internally far more often than they forward a link, and a stale one from 2022 with old insurance figures does more damage than not having one at all. Update it whenever your licensing, insurance or SLA figures change, not on a fixed schedule.

What an EA needs at 11pm

The travel manager and the EA are not the same reader, and a page written for procurement will lose the EA completely. An EA booking a car at 11pm for a 6am pickup wants three things fast: a phone number that's answered at that hour, confirmation that you can actually do a same-day booking, and a way to add the trip to an existing account without re-entering card details. If that information is buried under duty-of-care policy language, she'll book with whoever's site says "24-hour dispatch, call now" in the first line. Keep an urgent-booking page separate from the account documentation, and link between them rather than merging them.

It's also worth being realistic about how these pages get found. Corporate searches don't behave like consumer ones — a lot of the discovery now happens through an assistant summarising a shortlist rather than someone scrolling ten blue links, which is one more reason this content needs to be plain, factual and quotable rather than persuasive. I cover how that shift changes what to publish in how AI assistants pick which operator to recommend, and if you're weighing whether to build this cluster yourself or hand the drafting to a tool, agency retainer versus AI content tool walks through the trade-offs. The wider structural fix for a site that isn't showing up at all is in the six pages that fix Google visibility, and route-level detail matters for corporate travel too — see route pages for airport transfers if the account involves regular airport runs.

What to expect once these pages are live

Impressions on account-facing pages will stay low, often single or low double digits a month per page even a year in, because the total number of people typing these exact phrases is small. What changes is the quality of the enquiries that do arrive: fewer price-shoppers, more emails that open with "we're reviewing suppliers for our EMEA travel policy" and already assume you can do on-account billing because the page told them so. That is the entire point of writing for this audience — not more traffic, a better shortlist.