Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. How Do We Prove a Passenger Didn't Turn Up, or That Our Taxi Driver Really Waited, When the Customer Disputes It?
Problems We Solve

How Do We Prove a Passenger Didn't Turn Up, or That Our Taxi Driver Really Waited, When the Customer Disputes It?

Taxi no-show and waiting charges get disputed and written off. We build journey evidence from GPS, calls and texts so each charge is shown or credited fairly.

Updated 3 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

No-show and waiting charges are hard to defend because the evidence, the car's GPS position, the time the driver arrived, the call or text to the passenger, sits in different places and is rarely pulled together. We build a no-show and waiting record that assembles that evidence automatically for every such job, applies your charging rules consistently, and gives the office a clear summary to send when a customer or account disputes a charge.

The driver waited, the customer says they did not

A driver arrives for a pre-booked pickup at a hotel. The passenger does not come out. The driver rings the office, the office rings the passenger, there is no answer. After the time your policy allows, the driver is released and the job is marked as a no-show. Or the passenger appears much later, and waiting time is added.

A week later, the account customer's travel booker emails: their guest says the car was not there, or was late, and they will not pay the no-show charge. The office goes looking. The driver remembers the job but not the times. The dispatch system has some of it. The call to the passenger was made from someone's mobile. Faced with an argument it cannot win quickly, the office credits the charge.

Why the evidence is never in one place

Everything needed to settle the question exists. It just exists in several systems, and nobody puts it together until there is a dispute.

  • Arrival time and position are in the dispatch system's GPS data, which may only be kept for a limited period.
  • Calls to the passenger were made from the office phone, a driver's own phone or not at all.
  • Texts sent by the dispatch system, such as 'your driver has arrived', may not be stored with the job.
  • Your policy on how long a driver waits, and what you charge, is applied differently by different controllers.
  • The booking might have the wrong pickup point, such as the hotel's side entrance, which is not recorded anywhere.

Written-off charges and awkward conversations

When evidence is missingWhen evidence is ready
Charge credited to avoid an argumentCharge supported or credited on the facts
Office spends time searching several systemsSummary produced from the job record
Driver feels unsupportedDriver's wait is recorded and paid fairly
Account customer loses confidenceAccount customer sees a clear timeline

There is a fairness point too. Sometimes the customer is right: the driver went to the wrong entrance or arrived late. A clear record helps you credit those quickly and fix the cause.

A no-show and waiting record built for every job

What we build collects the evidence as the job happens, not after the complaint.

  1. When a driver marks arrival, the time and GPS position are captured from your dispatch system and saved with the job, beyond the dispatch system's normal retention if needed.
  2. Arrival texts and calls to the passenger are sent and made through a service such as Twilio, so each one is logged with its time and outcome.
  3. Your waiting and no-show rules are set once, such as the free waiting period and the charge after it, with different rules for airports and accounts if you have them.
  4. When a job ends as a no-show or with chargeable waiting, the charge is calculated from the rules and the recorded times.
  5. A one-page summary is produced for each such job: booking details, pickup point, arrival time and position on a map, messages and calls, and the charge.
  6. When a dispute comes in, the office sends the summary or decides to credit the charge, and the outcome is recorded against the job.
  7. A monthly report shows no-shows and disputes by account and by pickup location, which often points to a hotel entrance or a station exit where drivers and passengers keep missing each other.

Disputes settled in minutes

When a travel booker questions a charge, the office opens the job and sends a clear timeline. Most disputes end there. Where the record shows the driver was at the wrong entrance or arrived late, the office credits it quickly and adds a pickup note to that location.

Drivers see their waiting time recorded and paid consistently, which matters to self-employed drivers who lose earnings every minute they wait.

Your waiting policy is applied the same way every time, so customers are treated alike and the charges are easier to explain.

Sound familiar?

  • Disputed no-show charges are usually credited.
  • Finding a job's GPS record takes a long time.
  • Calls to passengers are made from personal phones.
  • Different controllers apply waiting charges differently.
  • The same pickup points cause missed passengers again and again.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Do you set our no-show and waiting charges?

No. The rules are yours, and whether they apply to a customer depends on your terms and any account agreement. We apply the rules you give us.

Can we get GPS data from our dispatch system?

Most dispatch systems record vehicle positions and many make them available through an API or reports. We check what yours keeps and for how long.

What about passenger privacy?

Only the data needed for the job is kept, with access limited to the office and a retention period you agree.

What drives the cost?

How much data your dispatch system exposes, whether calls and texts move to a logged service, and how many rules you have.

Keep reading

More on Problems We Solve

Start here

Tell us where your taxi office loses time

Describe the bookings, the drivers and the paperwork that are causing trouble, the dispatch system you run and the accounts you invoice. We will tell you what we would build around your existing setup and what we would leave alone, and if your dispatch system already does the job with a setting you have not switched on, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →