Take WhatsApp Bookings — Without Risking the Badge

For licensed London Hackney drivers. UK-only.

Every London cabbie reading this has had the same WhatsApp message at some point:

"Hi mate, can you grab me from Liverpool Street at 6:15?"

It's from a regular. Someone you've driven a dozen times. Their fare's good, their journey's predictable, and you'd happily take the work. You know exactly where they are. You know the route. The cab's clean and you're heading that way anyway.

And then you hesitate. Because picking up a pre-booked job off WhatsApp without a proper record is one of the easier ways to put the badge at risk — and most cabbies have heard at least one story of a local licensing prosecution that started with "informal" direct bookings.

So you either take the job and quietly worry, or you don't take it and your regular books another cab. Either way, you lose.

This post is about what to do instead. Specifically: how the BAT.TAXI invite system turns those WhatsApp messages into proper, TfL-compliant pre-booking records — without changing how the customer asks you, and without changing how you do the rest of your work.

One thing to flag before going further: BAT.TAXI is a pre-book only service with a minimum one-hour lead time between booking and pickup. That lead time is structural — it's what gives you time to either get to the customer or arrange a Co Driver who can. Last-minute requests aren't what this is for; customers know to hail or use an app for anything inside the hour. The Liverpool Street to Heathrow example above (5 AM message, 6:15 AM pickup) fits the model — 1 hour and 15 minutes of lead time is exactly the kind of pre-book job BAT.TAXI is built for.

Important: this post is general guidance, not legal advice. Compliance specifics vary by licensing authority. Verify your own position with TfL or your local council before relying on any of this.

The friction is the booking record, not the technology

Cabbies aren't avoiding direct WhatsApp bookings because WhatsApp is hard. WhatsApp is easy. Your phone is already on the dashboard.

The friction is the booking record. For pre-booked work — meaning any job arranged in advance, not flagged off the street or picked up off the rank — the licensing regime expects a proper written record. Date, time, pickup, destination, customer details, fare, driver. Audit-able. Exportable. The kind of record that holds up if your renewal interview goes anywhere near the question "how do you keep track of pre-booked jobs?"

A WhatsApp thread isn't that record. It's a conversation. It might contain most of the right information scattered across several messages, but it isn't structured, it isn't audit-ready, and it doesn't survive your phone being stolen or wiped.

So in practice, most cabbies have done one of three things:

Refused all direct WhatsApp bookings and stuck to rank, hail, and the apps.
Taken the WhatsApp bookings informally, kept the fingers crossed, and hoped no inspector ever asked.
Tried to keep parallel records in a notebook, a spreadsheet, or the back of a fare card — and given up after a fortnight because the admin doesn't scale.

None of those is a real solution. The first sacrifices a growing slice of repeat-customer work. The second is the risk we just described. The third works for a week and stops working as soon as the calendar fills.

How BAT.TAXI's invite system fixes this

The fix is structural. Instead of WhatsApp being the booking system (it isn't, and shouldn't be), WhatsApp becomes the invitation channel to a booking system that handles the record automatically.

Here's the loop:

Your regular messages you on WhatsApp asking for a ride. Same as today.
You send them your BAT.TAXI invite link — one tap from your driver dashboard. The link can also go via SMS, email, or be scanned from a QR code in the back of your cab.
They open the link and request the quote — pickup, drop-off, time. They enter their own details once. Future bookings remember them.
You see the request in your BAT.TAXI dashboard and send a fixed-price quote.
They tap to confirm.
A proper, structured pre-booking record is generated at the moment of confirmation. Date, time, pickup, destination, customer name, contact, fare, driver licence number, vehicle. All of it. Stored. Exportable. Audit-ready.
You take the job. Same job you would have taken anyway — except now there's a record that holds up.

The customer experience is barely different from what they're used to in WhatsApp — they're tapping a link and confirming a price. The cabbie experience is barely different from quoting a regular by text — except the booking record is real, structured, and yours forever.

The other channels work the same way: SMS invites, email invites, QR codes. Many cabbies print a small QR card and slide it into the back of the cab so passengers can scan it at the end of the ride. (This is the loop the London Driver Pack is designed around — and it's how the founder and fifteen other London cabbies operated the model manually for eighteen months before this platform existed.)

What happens when you can't take the job — the Co Driver mechanic

A real one for any cabbie who's worried about over-committing: what happens if a regular pre-books you for 6 AM on a Thursday and you're on holiday, asleep, at a hospital appointment, or already on another job?

The trusted Co Driver redirect handles it. When you redirect a booking from your dashboard, the job details — including the price and conditions you already agreed with your customer — get advertised to your trusted Co Driver network. An accepting driver takes the work on your terms: same fixed price, same drop-off fee, same agreed conditions. The customer experience is identical regardless of which driver actually fulfils the job. The fare your customer was quoted is the fare they pay.

This is the structural reason a Co Driver network actually works — and why it's not the same as sub-contracting. No negotiation in the moment. No surprise quotes. No customer wondering why their cabbie's mate is charging differently. The relationship stays clean.

(This is one of the features that came directly out of the eighteen-month manual phase — the founder and the fifteen other cabbies he was operating with were already doing this informally over WhatsApp. The platform just makes it structural.)

What's in the booking record

The structured record generated by every accepted BAT.TAXI quote includes:

Booking timestamp — the moment the booking was made, not the moment the ride happens.
Pickup details — full address, time, any notes the passenger added.
Destination details — full address.
Customer identity — name and contact details, taken once and re-used on subsequent bookings with the same customer.
Fare quoted — the agreed price, written at confirmation.
Driver and vehicle reference — your BAT.TAXI account identifies you and your licensed vehicle automatically.
Status trail — quote sent, quote accepted, ride completed, payment recorded.

The record is exportable any time. CSV or spreadsheet. If you ever need to demonstrate compliance to a licensing officer or at a renewal interview, you can produce the full history of your pre-booked work in seconds.

This is different from what's in a WhatsApp thread. WhatsApp gives you a conversation. BAT.TAXI gives you the structured record of the conversation that turned into a job.

Airport runs are the strongest use-case

If you've ever done a Heathrow drop-off and watched the passenger climb out without ever giving you anything more than the fare, you already know the highest-ROI moment (Return On Investment) of any cabbie's day. The airport run is your single best opportunity to convert a one-off passenger into a repeat customer.

The BAT.TAXI airport quote system generates a fixed-price quote for Heathrow, Gatwick, City, Stansted and Luton. You send your customer an invite link from the kerb. They book the return ride via your app, where your price for going to/from any airport is applied, so your new customer has booked their return ride before they're on the plane (they call this upstream fishing). The booking record is generated for the return; the customer is now on your list; you've turned one airport job into two — and a likely third, fourth, fifth as they keep travelling.

This is the loop the Driver Pack was designed around, and it's where the WhatsApp/SMS/QR invite system pays for itself fastest.

What about the rank and the hail?

Nothing changes.

This whole compliance question only applies to pre-booked work — jobs arranged in advance. The rank and the hail are different in law. When you pull up to the rank, the next passenger is the next passenger; no booking record is needed for a hail or a rank job because the booking happens at the kerb.

BAT.TAXI is for the pre-booked work — the repeats, the regulars, the airport returns, the early-morning hospital runs. It sits alongside your rank work, not on top of it.

Pricing

Same two tiers as the rest of the BAT.TAXI platform. The invite system, the booking record generator, the airport quoting, the message centre, the customer profile — all included in either tier. There's no per-record charge.

Platform Only: £4.99/month or £39.99/year. UK rollout cities + international. Digital only.
Driver Pack (London only): £99 first year (marketing pack + platform included free); £39.99/year from Year 2. Same platform plus the physical in-cab QR materials and the Airport Pricing dashboard feature.

If you're doing more than one direct booking a month, the £4.99/month tier has paid for itself before it bills.

FAQ

Is BAT.TAXI's booking record actually TfL-compliant? The record is structured to include the fields a TfL audit of pre-booked work would expect — booking timestamp, pickup, destination, customer details, fare, driver/vehicle identification, status trail. The record is exportable. As with any compliance question, you should verify your specific position with TfL or your local licensing authority — this is general guidance, not legal advice.

How far in advance does the booking need to be? The 1-hour minimum is the regulatory floor — anything shorter than an hour isn't what BAT.TAXI is built for; customers needing a cab in the next 20 minutes are still using rank, hail or the immediate-hire apps, exactly as before. But in practice, most bookings come in with 24 hours' notice or more — airport runs are typically the day before or several days ahead; hospital and business regulars often book days or weeks in advance. The 1-hour figure is the floor, not the typical. The 1-hour minimum is configurable from the backend and we may shorten it (e.g. to 30 minutes) as the system matures and as Co Driver networks deepen in each city.

What if my regular wants a cab now, not in an hour? Then they're not pre-booking — they're hailing. The honest answer: BAT.TAXI is the wrong tool for in-the-next-20-minutes work, and they should hail one off the rank or use an immediate-hire app for that ride. The point of BAT.TAXI is the rest of their journeys with you — the planned ones, the airport runs, the standing weekly bookings, the trips where they want certainty that you'll be there. Most regulars rapidly figure out which of their rides are which.

Does the customer need to download an app? No. BAT.TAXI is a web-based platform. The customer taps the invite link, opens a web page on their phone (or laptop), so it opens in their browser. Nothing to install, nothing to update. They can save the page (BAT.TAXI icon) to their phone home screen, then they'll have one-tap access next time they use it.

Can I keep using my personal WhatsApp for general chat with regulars? Yes. WhatsApp is still your inbox for "are you free Friday?", "running ten minutes late", and the usual back-and-forth. The invite system is the layer that turns "yes I'm free Friday" into a proper pre-booking record when the customer commits to the actual job. Conversation stays in WhatsApp; the booking lives in BAT.TAXI.

What if a regular just keeps texting me their pickup without using the link? You can still take the job — but you'd need to send them the invite link to convert the text into a structured booking before you do the work. The system is designed to make this a one-tap action from your dashboard. Most cabbies who try this for a month find regulars start using the link directly because it's faster for them.

Will my regulars find the invite system fiddly? Probably not. The link opens a simple web page — pickup, drop-off, time. They enter their details once and the system remembers them for future bookings. Most regulars take a single ride via the link, then default to it for everything afterward because it's quicker than typing out the same WhatsApp message every time.

Does the QR code work in the back of a black cab? Yes. The Driver Pack (London only) includes printed QR-coded materials designed specifically for in-cab placement. Outside the Driver Pack tier, you can generate a QR code from your dashboard and print your own — many cabbies stick one to the partition glass or include it on a small card handed to passengers at the end of the ride.

What happens if a customer asks to be removed from my records? One-tap delete from the customer profile. The customer is removed from your records and the underlying booking history is anonymised in line with UK GDPR retention requirements for transactional records.

Is this the same as joining one of the apps? No. The apps own the customer relationship — when you stop using the app, the customer can't reach you. BAT.TAXI invites bring the customer into your list. Your contact details, your booking history, your relationship. If you cancel BAT.TAXI, the cascade-delete fires across your customers and they leave with you — irreversibly, so export your records first (your responsibility, not ours). Read A CRM Built for the Cabbie, Not the Fleet for the structural difference.

Ready to take WhatsApp bookings — properly? Sign up as a cabbie →

Already a BAT.TAXI cabbie? Sign in →