10-Year Superhost (4.99★) Facing Statutory Tenancy Risk—Airbnb Safety Refusing to Act on Vendor Harassment & Overstay Warning
Has anyone else experienced fragmented, AI-scripted support loops from Airbnb Safety when reporting an active long-term guest overstay risk?
We are 10-year hosts with a 4.99★ rating, currently facing critical legal and financial exposure due to a bad-faith long-stay guest. Despite repeated warnings to Trust & Safety regarding intentional tenancy/occupancy leverage, Airbnb refuses to take preventative action or lock the backend reservation date prior to checkout.
The Core Safety & Legal Issues Ignored by Airbnb:
Vendor Harassment & Interference: The guest severely harassed and obstructed our professional cleaning team while performing their duties (a clear violation of house rules and local workplace protections).
Rejection of Impartial Evidence: We submitted an official, third-party complaint filed directly by the cleaning company detailing the guest's abuse and dishonesty. Airbnb Safety has refused to accept or act on this official report.
Support Bouncing & Inaction: Case management has bounced between over a dozen unpreprate agents in General Support and now with ineffective Safety Team member with scripted, automated replies. Rather than executing an administrative date adjustment or cancellation to protect the host, support is directing us to "wait until after she leaves" and negotiate payouts retroactively across secondary teams leaving no host protection.
By stalling and siloing this file, Airbnb is exposing us to severe statutory tenancy risk, financial loss, and ongoing property exposure.
Questions for Experienced Hosts:
How have you successfully forced Airbnb Safety to take ownership of an active overstay/tenancy risk before checkout occurs?
Has anyone successfully compelled Safety to accept and review an official third-party/vendor harassment report?
What is the fastest escalation path to a human Safety supervisor when frontline support stalls in scripted loops?
This case requires immediate, senior-level Safety intervention and a backend calendar lock—not post-checkout general support delays.
