Third-Party Bookings and Fake IDs: When Someone Books for Someone Else

The account is four years old with sixteen reviews, a professional photograph and a verified badge. The person who arrives is nineteen, has never heard of the account holder, and has six friends in the car. The booking was never for the person who made it, and every protection you thought you had was built on the assumption that it was.

Why it matters more than it sounds

A verified account with good reviews is not a character reference for whoever holds the keys. When the booker is not present, three things break at once. The reviews you screened on describe a different person’s behaviour. The messages you exchanged were with someone who will not be in the building. And any claim you file names a guest who can truthfully say they were never there.

That last point is where the money is lost. Damage claims are built on attributing an incident to a responsible guest, and a booker who was two hundred miles away has an obvious answer to the request. The claim does not automatically fail, but the argument becomes about the booking rather than the damage, which is a worse argument to be having. How Airbnb decides damage claims covers what the review actually weighs.

The patterns that show up before check-in

• The booker asks questions that suggest they are not travelling: “will they be able to park” rather than “can I park”.
• A short local booking on an account registered elsewhere, with a vague reason for the stay.
• A request to add a large number of guests after booking, or evasiveness about the number.
• An older, well-reviewed account booking a property style that does not match its history at all.
• A parent, employer or agent explaining that the booking is for someone else, which at least is honest.
• Pressure to communicate off-platform, or a phone number that belongs to a different person.

None of these prove anything on their own, and none of them relate to who a person is. They are behavioural facts, and the appropriate response to each is a direct question rather than a decision. The discrimination-free routine for that conversation is in screening a booking before you approve it, and local booking explains why the proximity signal changes the risk profile.

Ask the question in writing

One message does most of the work: confirm that the account holder will be staying and checking in, and ask for the number of guests. Keep it neutral and administrative, because most bookings are exactly what they appear to be and a suspicious tone loses you good stays.

The answer resolves the situation either way. A guest who confirms they are staying has put that in writing, which strengthens any later claim. A guest who admits the booking is for someone else has given you grounds to raise it with the platform. A guest who avoids answering has told you something too, and repeated evasion is itself a reason to escalate before arrival rather than after.

What to do when it is confirmed

The third row deserves emphasis. If a large unexpected group arrives, the priority is not the reservation, it is not being alone in a confrontation. Escalate to the platform, and where there is a genuine safety concern, to local authorities. The property is replaceable and insured; an argument on a doorstep at midnight is not worth having.

The connection to parties

Third-party bookings and party bookings overlap heavily, for an obvious reason: a group that expects to break the rules has an incentive to book on an account that will not be held to them. That is why the same screening questions catch both, and why the two policies reinforce each other.

The Airbnb party and event policy covers what the platform prohibits and what it acts on, Airbnb party damage covers the aftermath and the claim, and a guest caused a noise fine covers the penalties that follow. If your listing is in a market where this pattern is common, the paid screening services compared in guest-screening tools compared add verification steps the platform does not.

If damage happens anyway

File on the reservation holder, because that is who the contract is with, and describe the situation factually rather than indignantly: who booked, who arrived, what the messages said, what was damaged, what it cost. Attach the message thread showing the question you asked before check-in, if you asked it, because that is what converts “I was not there” from a defence into an admission of a rule breach.

The ordinary requirements still apply: file within 14 days of checkout or before the next guest checks in, request payment from the guest first, and build the file on dated before-and-after evidence with third-party costings. The free Claim Strength Checker will tell you where this particular file is weakest, and it is usually the identity question rather than the damage one.

The honest summary

Screening an account is not screening a guest unless the account holder is the one staying. Ask that question in writing on every booking that gives you a reason to, keep the answer, and escalate to the platform rather than cancelling yourself when the answer is wrong.

The free Guest Risk Pre-Screener runs the behavioural checks in order without touching anything protected, and it takes about five minutes. That is a good trade against the one booking a year where the person who booked never walks through the door.