A chauffeur service website that answers with a quote, not a phone number
People booking a chauffeur want to know three things fast: which car will turn up, whether the driver is licensed and insured, and what the journey will cost. A chauffeur service website should show the fleet honestly and take a detailed journey request that you can answer with a quote. Anticode does the second part through a custom form, and can even return a quote on the thank-you page if you run your own pricing endpoint.
Different clients, different first questions
- The executive assistant booking for a director: account terms, invoicing, discretion, reliability, a single contact who answers.
- The traveller heading to the airport: fixed price, what happens if the flight is late, luggage space, child seats.
- The couple booking a wedding car: the exact vehicle, ribbons and colour, how long the car stays, photos of that car.
- The event organiser moving guests: several vehicles at once, a coordinator on the day, waiting time.
One homepage can serve all four if it leads with a short line on what you do, the fleet, and a "Get a quote" button, then gives each service its own page. Generic generated chauffeur sites lean on a black saloon at night and words like "luxury" and "premium". The client wants the model, the year, the seat count and the driver's standards, and the photo of the actual car in your yard.
Fleet pages
Give each vehicle class its own page: an executive saloon, a luxury saloon, an MPV for groups, a people carrier with luggage space, any classic or wedding cars. On each, list passengers, suitcases (large and cabin), what's on board (water, chargers, Wi-Fi if you offer it), whether child seats are available, and a clear note that the exact model may vary within a class if that's true. A fleet CMS collection holds these neatly, one entry per vehicle or class, so a new car goes on the site the week it arrives.
The journey quote form
This is the page that earns the business. Anticode's standard contact form only asks for a name, email and message, which forces the client to write out the journey in prose. A custom form can carry up to 30 plain-text fields, so ask for exactly what you need to price it:
- Pick-up address, date and time.
- Drop-off address, and any stops on the way.
- One way or return, and the return time if known.
- Passengers, large cases and cabin bags.
- Vehicle class preferred.
- Flight or train number, for airport and station collections.
- Child seats, accessibility needs, a sign with a name for meet-and-greet.
- Name, phone, email, and a company name for account clients.
When the form is sent, its site function runs on the server. The simplest version saves the request and the thank-you page tells the client when to expect your quote. If you already price journeys in your own software, the site function can make a signed HTTPS call to your endpoint, and the heading and message it returns, including a quoted price, appear on the thank-you page. Anticode's built-in formula is arithmetic over form fields, so it can't work out a road distance by itself; that part has to come from your system. Nothing is calculated while the client types, because published pages run no scripts.
Route each request where it'll be seen: a Telegram or Slack message to the controller, a row in Google Sheets for the bookings log, or HubSpot for account clients with an email address. Each submission is sent once, so check your connector is working before you go live. The workflow page on routing contact form enquiries walks through the options.
Airports, events and waiting time
Write the airport transfer page around the worries: you track the flight, how much free waiting time follows landing, what you charge after that, where the driver meets the passenger, and parking fees. For weddings and events, say how long a booking lasts, what happens if the day runs late and whether decorations are included. Policies on cancellations and soiling charges belong on their own page, linked from the quote form.
Licensing, insurance and trust
Private hire and chauffeur work is licensed in most places, and clients increasingly check. State the licensing authority and your operator licence where it's appropriate to publish it, confirm that drivers are licensed and vehicles insured for hire and reward, and describe driver vetting in your own words. The exact wording and what you must display are your responsibility under local rules; Anticode won't check them. Anticode does write a starting Privacy Policy from what your site collects, which matters when you're holding home addresses and travel times.
What Anticode doesn't do here
- No dispatch or driver app. Requests arrive as messages; allocation happens in your own system.
- No live pricing as the client types, and no distance lookup without your own endpoint.
- No card payments on the site. Send a payment link from Stripe Payment Links or PayPal once the quote is accepted, or invoice account clients.
- No client logins for account holders to see past journeys.
Questions people ask
Can the website give an instant journey price?
Only after the form is sent, and only if a site function calls your own pricing endpoint. Anticode's formula can't calculate a road distance by itself.
What should an airport transfer form ask for?
Flight number, landing time, terminal, passengers, luggage, child seats and the drop-off address, so the driver can track the flight and bring the right car.
Can corporate clients book through an account?
Not with a login on the site. Take account enquiries through a form and manage the accounts in your booking or accounting software.