At TripWip, we use a strike policy for hosts as a preventive and educational tool. The goal is to protect the driver experience and keep a trustworthy marketplace, not to punish one-off mistakes.
What is a strike?
A strike is a warning applied when a host’s behavior negatively affects the driver’s experience or the proper functioning of the platform.
Some examples of situations that can lead to strikes:
Not responding to booking requests consistently.
Canceling confirmed bookings without a valid reason.
Repeatedly leaving drivers without a car at the last minute.
What adds points?
Not responding to a request: 2 points.
It adds the most points, and it’s the easiest to avoid.
Canceling an approved trip: between 2 and 4 points.
It depends on how soon the trip starts.
Declining a request: 1 point.
If you decline it within 2 hours of receiving it, it doesn’t add anything.
How many points get your car suspended?
Your car gets suspended at 4 points if you already have experience on TripWip, or at 5 if you’re just getting started. It also gets suspended if your acceptance rate drops below 50%.
How are they cleared?
Every trip you complete successfully clears all your accumulated points. It resets automatically, no paperwork needed.
Why do strikes exist?
Because drivers and hosts trust that the bookings they make and accept will be honored.
When a host cancels, doesn’t respond, or fails to follow through, the driver:
Loses time and trust.
May end up without a car close to their trip.
Has a worse experience with TripWip.
The strike policy helps us:
Identify patterns of problematic behavior.
Warn the host and give them a chance to improve.
Protect drivers and the ecosystem as a whole.
What happens if I accumulate strikes?
As a host accumulates strikes, TripWip may apply different measures, for example:
Lower visibility of the vehicle in search results.
Temporary account restrictions.
Partial or full suspension of the profile in serious or repeated cases.
Measures are always meant to be proportionate and to take the host’s full history into account.
How to avoid strikes
Some key best practices:
Keep notifications on so you can respond in time.
Keep your availability up to date: block dates when you can’t rent out your car.
Avoid accepting bookings you won’t be able to honor.
Notify and contact support about any genuine unforeseen issue (mechanical problems, force majeure, etc.).
Communicate clearly and respond well to drivers.
What if I think there was a mistake?
If you received a strike and believe it was assigned by mistake, or that some information wasn’t taken into account:
Contact the support team through the official channels.
Tell us what happened and share as many details as possible.
We’ll review your case and, if appropriate, adjust or reverse the measure.
Learn more about the policy
You might also find this useful: