What Happens When a Blacklisted Guest Books

Blacklisting a guest records who you never want back. This page says exactly what Vanio does with that — and, just as importantly, what it does not do.

Blacklisting warns you. It does not block the booking.

Be clear about this before you rely on it: a blacklisted guest can book one of your properties again, and the booking goes through. Vanio does not decline it, does not cancel it, and does not hide your availability from them.

What Vanio does is make sure the booking doesn't slip past unnoticed:

• You receive an immediate alert — a bell notification in Vanio and a push notification on your device — the moment the booking arrives. The alert names the guest, the property, and the reason you recorded when you blacklisted them.
• A warning is written into the booking's own timeline, naming the guest and the reason. Anyone on your team who opens that reservation sees it.
• The reservation is marked as needing attention in Vanio's records the moment it arrives.
• The guest's profile carries a critical flag with the same reason, so the history is there whenever you look them up.

The guest is never told any of this. Nothing is sent to them, and nothing about the blacklist appears on their side.

Where the warning shows up

When a blacklisted guest books, Vanio alerts you in two ways at once:

In-app and push notification. A bell notification appears inside Vanio and a push notification is sent to your device. The alert tells you the guest's name, which property they booked, the booking reference, and the reason they were blacklisted. Tapping or clicking the alert takes you directly to the reservation — or, if the booking hasn't fully resolved yet, to the guest's profile where the blacklist reason and full stay history live.

Timeline entry on the reservation. The warning is also written into the booking's own timeline, so anyone on your team who opens that reservation sees it even if they missed the notification.

[Screenshot: Bell notification showing a blacklisted guest alert with guest name, property, booking reference, and blacklist reason]

Who receives the alert

Alerts go to team members with Owner, Admin, or User roles. They are not sent to landlord (listing owner) accounts or to field and service roles.

Controlling the alert

The blacklisted guest alert is on by default. To turn it off — or back on — go to Settings → Notifications, find the Reservations section, and toggle Blacklisted Guest Bookings.

[Screenshot: Notification settings page with the Blacklisted Guest Bookings toggle highlighted]

Routing alerts to Slack, email, or other tools

If you want the alert to go further than Vanio's own notifications, you can build a workflow on top of it. In Workflows, the trigger Blacklisted Guest Booked (listed under Guest Risk) fires whenever Vanio raises this alert. Connect it to a Slack message, an email, an SMS, or any other action your workflow supports.

[Screenshot: Workflow builder with the Guest Risk trigger group expanded, showing the Blacklisted Guest Booked trigger selected]

When the alert fires — and when it doesn't

The alert fires only on a new booking or a new booking request. It does not fire on modifications, cancellations, or bookings that were imported when you first connected a channel. Backfilled historical reservations don't trigger alerts, so connecting a new channel won't send you a burst of notifications about stays that have already happened.

Turning the booking away is your decision

Because the booking is live, refusing the guest is a deliberate action you take:

• If the booking is still a request, decline it — see Declining Reservations.
• If it is already confirmed, cancel it on the channel it came from. Cancellation penalties apply the same as they would for any other booking.

Vanio does not make that call for you. Turning a guest away carries consequences on every channel — cancellation fees, ranking effects, and in some places rules about who a host may refuse — and those are yours to weigh.

What the blacklist catches, and what it misses

Vanio matches an incoming booking to a guest using the identity the booking channel supplies.

Caught: a blacklisted guest who books again from the same channel account. That includes the case where they show up on a second profile in Vanio — the blacklist reaches every record Vanio can confirm is the same person, using the platform's own account identifier, so it still fires. When the ban is recorded on a duplicate profile, the alert links directly to the profile that carries the blacklist reason, so the context is one click away.

Missed: the same person under a new account. Someone determined to get around a blacklist can create a fresh account on the booking platform. That arrives as a new guest with no history, so there is nothing to match against and no warning is raised. The same is true across platforms — a guest you blacklisted from an Airbnb stay who comes back through Booking.com arrives as a new person, because nothing connects the two accounts.

Vanio deliberately does not guess at this. Wrongly telling you an innocent guest is blacklisted would be worse than staying quiet. If you spot a returning guest under a new account, blacklist that profile too.

Blacklisting a guest

Open the guest from Guest CRM, then use Blacklist guest on their profile. Record a reason while it's fresh — it's the text that shows up in the alert months later, and it's what tells whoever is on shift why this booking needs a second look. A blank reason is allowed, but the alert will name the guest without explaining why.

You can lift a blacklist from the same place at any time. Once lifted, future bookings from that guest stop raising the warning. The history stays on the guest's activity log.

Everyone you have blacklisted is listed under Guests → Blacklist.

Tips & best practices

• Always record a reason when you blacklist someone. The alert text is built from whatever you wrote at the time. Six months later, "aggressive during dispute over damages" tells your team manager what to do; "bad guest" does not.
• Use a workflow if you need the alert somewhere specific. The in-app and push notifications reach whoever has Vanio open. If your operations run through Slack or a group email, set up a Blacklisted Guest Booked workflow to route the alert there automatically.
• Act quickly on booking requests. A booking request is still declinable without penalty. If a blacklisted guest sends a request, you have a window to decline it cleanly — the alert fires the moment the request arrives so you don't miss it.
• Blacklist the new profile too, if you spot a returning guest under a different account. The system can only match what it can verify. Adding the new profile extends the coverage.
• Check the guest profile link in the alert. The alert links to the profile that carries the blacklist reason. If the ban was recorded on a merged or duplicate profile, that's where you'll find the full context.

Common questions

I blacklisted a guest but didn't get an alert when they booked. Why? A few things to check: confirm that Blacklisted Guest Bookings is toggled on under Settings → Notifications → Reservations. Also check that your role is Owner, Admin, or User — landlord and field/service roles don't receive this alert. Finally, the alert only fires on new bookings and booking requests — if the reservation was imported as part of a channel back-fill when you first connected the channel, no alert is sent.

The alert appeared, but I can't see a blacklist reason. Did something go wrong? No — the alert fires even when no reason was recorded. A reason is optional when you blacklist a guest. If the field was left blank, the alert still names the guest and the property; it simply won't include a reason line. To add one now, open the guest's profile and edit the blacklist entry.

Will my landlords (listing owners) see the alert? No. Alerts go to Owner, Admin, and User roles only. If a landlord needs to know about a blacklisted guest booking, you'll need to inform them directly or set up a workflow that routes the alert to a shared inbox or communication channel they have access to.

Related

• Guest CRM — guest profiles, history and contact details
• Declining Reservations — how to turn down a booking you don't want
• Reservation Operations — every action you can take on a booking
• Workflows — automating actions based on events in Vanio