Running a taxi business on WhatsApp: where it breaks after 3 drivers

TL;DR: Taxi dispatch on WhatsApp works until the third driver. After that, the same group chat that felt fast starts producing double bookings, missed jobs and arguments nobody can settle, because there is no record of who took what. This is what breaks, in the order it breaks, and what a small operator can put in its place without an IT department.

Why taxi dispatch on WhatsApp is where everyone starts

Nobody chooses WhatsApp as a dispatch system. It is just already there. Customers message on it, drivers are on it, the owner is on it. A thread on r/smallbusiness from a service business owner puts it plainly: inquiries, orders, confirmations, complaints and follow-ups, all in one app. For one or two cars it is fine. The owner knows every job by heart and the chat is a backup memory.

The problems with taxi dispatch on WhatsApp start when the fleet grows past the point where one person can hold every job in their head. That point is usually the third driver.

Taxi dispatch on WhatsApp: what breaks, in order

1. Two drivers answer the same message

You post “AMS to Haarlem, 08:05 tomorrow, who’s free?” Two drivers reply within a minute of each other. Both think they have it. One of them turns up at Schiphol for nothing, or worse, both do and the passenger watches two cars from your company argue at the kerb. This is the single most common complaint we hear from operators, and it has one cause: a message is not an assignment.

2. Nobody answers, and nobody notices

The opposite case. You post a job, everyone is driving, nobody replies, and the message scrolls up under forty others. The passenger finds out on the day. There is no list of “jobs without a driver” because there is no list, just a chat.

3. Quotes are typed by hand and differ every time

A passenger asks for Zurich Airport to Davos. You quote CHF 340 from the car. Your colleague quotes CHF 360 to the same passenger’s partner the next day. The passenger notices. Now your fixed fare is not fixed, and the airport-taxi-scam reputation that Swiss forums already carry attaches to you.

4. There is no audit trail

A passenger claims they cancelled on Tuesday. The driver says nothing came through. The owner scrolls back through three hundred messages looking for a screenshot that may not exist. In a dispute with a card company, a chat scroll-back is not evidence. A booking record with timestamps is.

5. The owner is on the phone forever

After hours, bookings still arrive. Someone has to reply. That someone is the owner, at 23:00, from the car. Onde’s own guidance for taxi companies says WhatsApp and radio dispatch stop scaling somewhere around ten cars. In our experience the pain starts well before that.

6. Payment happens after the ride, or not at all

Cash and bank transfers are chased after the fact. Corporate clients want an invoice. A hotel concierge wants a card receipt for the guest. None of that lives in a chat.

What operators try before they switch

Most do not jump straight to software. They try:

• A pinned message with tomorrow’s jobs. Works until someone edits it wrong.
• A shared spreadsheet. Works for the owner, never for drivers on the road.
• Separate groups per driver. Now the owner is copying the same job into three chats.
• A rule that every job must be replied to with a thumbs up. Holds for a fortnight.

All of them fail for the same reason taxi dispatch on WhatsApp fails in the first place: they add discipline to a tool that has no concept of a job, a driver or a status.

What to put in its place

The bar is not “as good as an enterprise dispatch platform”. Those are built for fifty-car call centres and priced like it. The bar is “better than a group chat”, which is low, and worth clearing with the least complexity possible.

One board, one status per job

Every booking is a row: time, route, passenger, fare, status. Requested, confirmed, driver assigned, en route, completed. Tomorrow’s jobs are visible on the owner’s phone without scrolling. Jobs with no driver stand out.

Assignment that cannot double-book

Paid by card: the job is assigned automatically. Paying later: the job goes to all drivers by e-mail and the first to accept takes it. The moment one driver accepts, it is gone from everyone else’s view. The “I thought you had it” conversation stops existing.

Drivers stay on e-mail, no app

Drivers are the reason many software rollouts die. Anything that needs an app install, a login they forget, or training, gets abandoned in a week. Jobs arriving by e-mail with a link that works on any phone is the lowest bar there is. Drivers accept or reject from the e-mail. If they want, they log in and see only their own jobs.

Fixed fares that the software quotes, not the driver

Rates per route or per kilometre, set once. The booking site quotes them to the passenger before they confirm. Nobody types a price from the car. See how the fixed-fare quote engine handles routes, night tariffs and extras.

Payment at booking, receipt by itself

Card payment through the operator’s own Stripe account at the moment of booking. The receipt sends itself. Invoices for business customers come from the same booking in one click, not from a spreadsheet at month end.

What you keep from taxi dispatch on WhatsApp

Customers who like to message you will keep messaging you. That is fine. The difference is that when the message arrives, you enter it as a booking in ten seconds and it joins the board like everything else, instead of living in the chat. The conversation stays on WhatsApp. The job does not.

How small operators actually migrate

The operators we work with did not switch overnight. A typical path:

1. The booking site goes live on their domain with their routes and fares. New online bookings land on the board from day one.
2. Phone and WhatsApp bookings get entered by the owner for two weeks, alongside the group chat. Drivers get jobs by e-mail and still see the chat.
3. Drivers stop reading the chat for jobs because the e-mail arrived first and had everything on it.
4. The group chat becomes what it should have been: a place to say the M1 is closed.

Setup on our side takes one to two business days once we have the domain, routes, rates and Stripe keys. Pricing is flat, annual or monthly, no per-driver fees, so a three-car fleet is not paying for a call-centre module.

Taxi dispatch on WhatsApp: frequently asked questions

Can I keep taking bookings on WhatsApp?

Yes. The customer conversation stays where it is. You enter the job on the board in a few seconds and it gets the same driver assignment, confirmation and reminders as an online booking.

Do my drivers need to install anything?

No. Jobs arrive by e-mail with a link that works on any phone. Drivers accept or reject from the e-mail. If they want to see their upcoming jobs in one place, they can log in as a driver and see only their own bookings.

How long does the switch take?

Setup is one to two business days on our side. Most operators run the group chat and the board side by side for about two weeks, then the chat stops being used for jobs on its own.

If your operation currently lives in a group chat and a notebook, book a free demo with your own routes and see what the board looks like with tomorrow’s jobs on it.