The booking gate for real covers

Four empty tables on a Saturday is not a no-show problem. It is a bot problem.

Bot Bouncer scores every booking before it takes a table. Real guests walk straight in. Suspicious bookings get a deposit or a hold, and anything unconfirmed goes back into inventory by 4pm.

Uses a sample restaurant

Sits behind your existing booking system. Nothing changes for the guest.

Incoming booking / AsterSAMPLE · 01/03
Booking received
Priya N.
Party of 2 · Friday 7:30pm
#001
Time to completeAwaiting signal
Attempts across slotsAwaiting signal
Account ageAwaiting signal
Card behaviourAwaiting signal
Agent identityAwaiting signal
Risk score0/ 100
Checking booking signals
The score updates as each signal arrives.
Scoring sample bookings
01 / The signals

Five things, none of them clever.

You should know exactly what gets a booking challenged. Here is what the score looks at, and what each signal can get wrong.

01

Time to complete

A human filling in a form takes seconds to minutes. A script takes three.

Misses: Fast, confident regulars who book on a saved card.

02

Attempts across slots

Eleven tries across nine slots in four minutes is not someone deciding.

Misses: A genuinely indecisive party of six.

03

Account history

Previous visits, previous cancellations, previous no-shows.

Misses: Everyone on their first visit.

04

Card behaviour

A card seen before, declined then retried, or used across many venues in minutes.

Misses: New cards, which are ordinary.

05

Verified agent identity

Whether the request is signed by an assistant the venue has chosen to accept.

Misses: Nothing, but only agents that sign can be checked.

No single signal decides anything. Aster's rules weigh them together, then decide whether the table needs a challenge.

02 / The false positive

Sam booked for two on a Thursday and got challenged.

Sam T.

Party of 2 · Thursday 6:30pm

45
Medium risk
AccountBrand new
Time to complete11 seconds
CardNew to the system
Card holdChallenged, not rejected.
90 seconds laterConfirmed the booking.
At serviceSat, ate, paid.

A challenge is not a rejection. It is a card hold or a confirmation click. Sam cleared hers in 90 seconds.

You set the threshold. Challenge more and you catch more bots and annoy more guests. Challenge less and the reverse.

Every challenged booking is in the dashboard, including the ones that turned out fine.

Any tool that claims no false positives is either lying or letting bots through.

03 / Agent policy

Let the good ones in. Set the rules yourself.

An assistant booking for a real diner is a customer. A script holding nine slots is not. The difference is whether it will sign its name.

Aster / Agent policySample settings. Try changing them.
Venue rules
Accept verified agents: on.
Marcus D. · party of 4 · Saturday 7:00pmWithin policy. Confirmed 2:12pm.
04 / Pricing

One monthly fee. No per-booking charge.

The fee is based on the size of your room, not the number of bookings or challenges. Bot Bouncer sits behind your existing booking system.

J. Whitcombe · party of 6 · Saturday 8:00pmReleased 4:00pmTable resold 4:20pm
Six covers that would have been empty.

Run it on a Saturday service.

Tap through a real evening at a sample restaurant, including the booking it challenged that turned out to be a regular.