A customer made a false complaint against me: fight back
Factual guidanceFresh — reviewed 19 April 2026Sources: 7Next review: 18 July 2026
No sponsor
Take this with you
Dated, pre-fillable checklist + your details — ready to show a rep or solicitor.
In the next hour
- Save everything from the disputed job straight away: trip or order ID, dashcam clip, GPS log, delivery photo, customer name in the app, timestamps, any messages.
- Do not confront the customer or post about them on social media. That can destroy your credibility later.
- If the complaint is about a safety issue or involves a threat, call 101 (or 999 if there is an immediate risk) and get a police reference number. That reference is gold in a platform appeal.
- Write a short factual incident note while it is fresh: what happened in time order, what the customer said, what you did.
In the next week
- Report the false complaint through the platform safety or support route. Keep the ticket number.
- If the platform sends a deactivation or warning, respond through the proper appeal route with the evidence attached. State the specific false allegation and show how each piece of evidence contradicts it.
- If the platform refuses to explain what the customer actually said, send a Subject Access Request (UK GDPR Article 15). They must disclose personal data and the basis of any automated flag.
- Track the deactivation date if one is issued. ACAS conciliation deadline is 3 months minus one day.
In the next hour
- Save everything from the disputed job straight away: trip or order ID, dashcam clip, GPS log, delivery photo, customer name in the app, timestamps, any messages.
- Do not confront the customer or post about them on social media. That can destroy your credibility later.
- If the complaint is about a safety issue or involves a threat, call 101 (or 999 if there is an immediate risk) and get a police reference number. That reference is gold in a platform appeal.
- Write a short factual incident note while it is fresh: what happened in time order, what the customer said, what you did.
In the next week
- Report the false complaint through the platform's safety or support route. Keep the ticket number.
- If the platform sends a deactivation or warning, respond through the proper appeal route with the evidence attached. State the specific false allegation and show how each piece of evidence contradicts it.
- If the platform refuses to explain what the customer actually said, send a Subject Access Request (UK GDPR Article 15). They must disclose personal data and the basis of any automated flag.
- Track the deactivation date if one is issued. ACAS conciliation deadline is 3 months minus one day.
Tools, guides and templates to use
- weekly screenshot logging so a single false complaint does not skew your record.
- structured bundle for appeals.
- SAR template per platform.
- Article 22 challenge if the decision was automated.
- what the platforms can and cannot do with ratings.
When to escalate
Police non-emergency: 101. If the complaint was a malicious allegation, ask officers about wasting police time or malicious communications. ADCU at appdrivers.co.uk. GMB at gmb.org.uk. IWGB at iwgb.org.uk. For London PHV drivers, TfL complaints at tfl.gov.uk. For serious defamation or harassment, a specialist solicitor.
Related crisis pages
- if the false complaint led to deactivation.
- if the "complaint" was retaliation after an assault on you.
- if the flag came from automated checks, not a human.
Last reviewed
19 April 2026
Primary sources used:
Research/Gap/G1.1-uber-appeal-process.mdResearch/Gap/G6.3-assault-reporting.mdResearch/S3-rights/3.8-challenging-ratings-and-penalties.md
Before you leave
Sources
- UK GDPR Article 15 (Subject Access Request)
- UK GDPR Article 22 (automated decisions)
- Police non-emergency 101
- ACAS 0300 123 1100
- ADCU appdrivers.co.uk
- IWGB iwgb.org.uk
- TfL Taxi and Private Hire complaints tfl.gov.uk