I've long required a security deposit for Airbnb bookings, but usually I ignore it and submit a claim via AirCover instead, since that reduces the risk of a chargeback, and AirCover will often cover it anyway even if the guest declines to pay (reducing bad blood between host and guest).
But I went to submit an AirCover claim today for some damaged rugs, and I got this warning:
I tried the option for the security deposit already being returned (even though it hasn't been) and got this:
I then went back and clicked "None of the above" and got this:
This is definitely new to me since my last AirCover claim (which, admittedly, was awhile back), but I hadn't seen it mentioned here before, so I wanted to share these screenshots.
I'm wondering if maybe I'd do better to just skip the requirement for a SecDep for Airbnb bookings (it's a constant source of friction with guests not wanting to provide their details) and rely on AirCover if that's effectively what I've been doing anyway. And in this year's more challenging environment, reducing guest friction may lead to an increase in bookings and revenue, which would be a plus...with little downside, since I wasn't really ever collecting on the SecDep anyway.
I do think the mere presence of the SecDep, even if I never actually used it, did help to self-select for guests who will be more respectful of my property, so I might get more bookings without one but I might end up with more guests who are of the type to damage the property or treat it poorly. It's just a bit frustrating that Airbnb leads guests to think I'm a bad host for requiring a SecDep (with all kinds of warning and verbiage telling people not to pay or give information outside of Airbnb that I have to work hard to overcome) but then they want to outsource their risk to we hosts who do collect SecDeps. They want it both ways...
