At TripWip, we continue to improve the experience for everyone. That's why we launched (and it's already active) a strike policy for hosts based on a point warning system, aimed at encouraging commitment and proper management of listings within the community.
What is a strike?
A strike is a warning assigned when behavior is detected that negatively affects the driver's experience or the operation of the platform. It is a preventive and educational measure: we seek for hosts to adopt good practices, not to penalize for the sake of penalizing.
What behaviors generate a strike?
A strike will be assigned when any of the following situations are detected:
Not responding to a rental request.
Rejecting requests without a justified reason.
Canceling a confirmed reservation.
How many strikes does each action accumulate?
Not responding to requests - 2 strikes
Early rejection - 1 strike
Late rejection - 2 strikes
Early cancellation - 2 strikes
Late cancellation - 3 strikes
Consequences
Upon accumulating 8 strikes, the host's account will be temporarily suspended.
The policy is designed to protect the user experience and improve the reliability of the platform.
How to avoid strikes (best practices)
Being a good host does not mean being available 24/7. It means using the tools we offer you to manage availability and expectations effectively:
Keep notifications enabled to avoid missing requests.
Block the calendar when you do not want or cannot rent.
Set a minimum number of days per reservation if you need longer bookings.
Respond clearly and promptly to requests and questions from drivers.
These actions help reduce rejections and cancellations, provide a better experience for drivers, and increase your chances of booking more days and improving your income.
What if you think there was a mistake?
If you believe a strike was assigned to you by mistake or want more information about a measure taken against your account, contact us through the support channel and we will review it.