How to Handle a Guest Who Won't Return the Car

A trip that's supposed to end at noon is still going strong at six in the evening, and the guest isn't answering any of your messages. It's one of the most genuinely anxiety-inducing moments in the entire hosting experience, and it's exactly the situation where a calm, staged plan matters far more than raw instinct or panic.

Having the stages worked out in advance means you're following a plan under stress, rather than inventing one on the spot while already anxious about where your car actually is.

Stage one: reach out, and assume the benign explanation first

Traffic, a flight delay, a dead phone battery. Most late returns turn out to have a completely ordinary explanation behind them. Your first message should be direct but not accusatory in tone: confirm the return plan clearly and simply ask for an honest update.

Stage two: escalate through the platform itself

If there's no response within a reasonable window of time, use the platform's own reporting tools for a late or unresponsive guest. This starts an official timeline on record and often triggers support resources on their end that you personally don't have direct access to.

Stage three: check what you're actually able to see

If the vehicle has a tracking device installed, this is the exact moment it earns back its cost, confirming the car's general status without you needing to guess blindly. Use whatever legitimate visibility you genuinely have available, and don't push further than that entirely on your own initiative.

Stage four: know the line between very late and law enforcement

There's a real, meaningful threshold where a delayed return stops being your personal problem to manage and becomes something for police to handle instead. That threshold usually involves specific platform guidance, and often a certain elapsed time with genuinely no contact at all. Know this threshold in advance, so you're not trying to figure it out under real stress in the moment.

How this actually plays out

Most late returns resolve at stage one, with a guest simply stuck in traffic and apologetic once they reconnect. A smaller number reach stage two, where platform escalation nudges an unresponsive guest into finally replying once they realize the situation is being formally tracked. Very few ever reach stage four, and hosts who've been through it once tend to describe the same thing: having already decided where that line sits made an awful evening considerably easier to get through.

Throughout all of it: preserve everything

Every message, every timestamp, every support ticket number, saved as you go rather than reconstructed later. If this situation ultimately resolves badly, that record is exactly what protects you. And if it resolves well after all, you'll simply be glad you never actually needed it.