Hospitable stops re-verifying returning guests, and starts checking their email is real

Hospitable has reworked Guest Vetting over the past few weeks, and the changes pull in two directions at once: less friction for guests who have already proved who they are, more scrutiny on the details of a new booking.

Repeat guests skip the ID check

On Direct Premium, a guest who has already completed identity verification with you does not have to do it again. Their previous verification is reused and they move through the booking flow faster.

It applies across instant bookings, booking requests and custom quotes, so the behaviour is consistent however the reservation arrives.

For anyone with real repeat business on direct, this removes the most common complaint about verification: the guest who stayed in March, books again in October, and is asked to photograph their passport for a host they have already met.

Name matching stopped crying wolf

The second change is less visible and probably saves more time. Guest Vetting now recognises that a name on a booking and a name on an ID often differ for completely innocent reasons.

It handles nicknames standing in for legal first names, Abby for Abigail. It handles a missing middle name, Tom Herrmann against Tom Kay Herrmann. It handles shortened forms, Matt for Matthew. And it handles small typos, Jonh for John.

Anyone who has run document verification at volume knows what this fixes. The mismatch flag fires, a staff member opens the booking, reads two names that are obviously the same person, and clears it. Multiply by a few hundred bookings and it is a part-time job that produces nothing.

Email addresses now get checked

A new check looks at whether the guest's email address is valid and reliable, flagging addresses that are undeliverable, temporary or disposable, or simply malformed.

This is the genuinely new signal. On a direct booking, the email address is your only reliable channel to the guest, and a disposable address is both an operational problem and a soft fraud indicator. A guest booking a legitimate holiday rarely reaches for a throwaway inbox.

What to weigh before you relax

Reusing a previous verification is a trade. It is convenience bought against the assurance of a fresh check, and it inherits whatever the first check was worth. If the original verification was thin, or the account is shared within a household or a group of friends who book in turn, the reuse carries that forward. For most operators that is an acceptable risk on a returning guest. For anyone letting high-value property, or property where a licence obliges you to record who actually stays, it is worth deciding deliberately rather than taking the default.

The name matching has the same shape. Fewer false alarms is the right goal, and the examples Hospitable gives are plainly benign. But tolerance for a name mismatch is exactly the gap that a stolen card or a borrowed identity sits in, and a system that now explains away small differences will explain away some that were real. The honest read is that Hospitable has moved the dial toward throughput, which is almost certainly correct on volume, and that the small number of cases it now waves through will not announce themselves.

Hospitable does not say whether the name matching and email checks are limited to Direct Premium or run on all vetted bookings. The reuse of verification is explicitly a Direct Premium behaviour. Check which of these you actually have before you change how your team handles a flagged booking.