Back to blog
Guide

The Regular Who Never Books

Walk-in regulars are the guests your booking system cannot see. They spend, they return, and they are absent from every report built on reservations. How to count them without making them book.

He comes most Thursdays. Sits at the same end of the bar, spends steadily, knows three of the staff by name.

He has never made a booking, so as far as every report is concerned he does not exist.

What this distorts

More than it looks like.

Your regular count is wrong. Built from booking history, so it counts the people who plan and misses the people who habituate — and habit is a stronger signal than planning.

Your busiest night may be misidentified. If one night skews toward walk-ins, its bookings understate it, and the staffing follows the bookings.

Your retention numbers are measuring the wrong population. A guest who stopped coming after two years is invisible if he never booked. You cannot notice the absence of someone you were never recording.

⚠️ And the correction is not "make them book." The lack of friction is frequently why they come.

Why "just get them to book" fails

Three reasons, and all three are the guest's:

It removes the point. Part of the appeal is deciding at 21:30 that tonight is a night. A booking is a commitment made hours earlier by a different mood.

It makes them a transaction. A regular who walks in is a person the room knows. A regular who books is a party of one in a slot.

They will not do it. They have been coming for two years without booking. A new policy will lose the guest before it changes the habit.

Counting them without changing anything

The record has to be created at the point where they are already known: the tab, or the person serving them.

Attach the tab to a person, not a table. ⚠️ This is the whole mechanism. If a tab can carry a guest identity — even a nickname the staff use — then every visit is recorded without the guest doing anything.

Let staff attach a returning face. They already recognise them. The only thing missing is somewhere to put it, and one action to do it.

Accept partial data. A regular known only as "Thursday bar guy, drinks the house red" is enormously more useful than nothing. Perfect identification is not the goal; continuity is.

What becomes possible once they exist

Absence becomes visible. The single largest gain. A walk-in regular who stops coming currently generates no signal at all.

Their real value shows up. Frequently higher than the booking regulars, because frequency beats party size over a year.

Staffing gets honest. A night with heavy walk-in traffic stops looking quiet in the forecast.

The trap

Do not make it a loyalty scheme.

A card, an app, points — these ask the guest to participate, which is the same mistake as making them book, wearing different clothes.

⚠️ The counting must happen entirely on your side of the bar. If it requires anything from the guest, it will capture the guests you already capture and miss exactly the population you are trying to see.

The check

Take a Thursday. Count the covers. Count the bookings.

The gap is the population your reports cannot see. In many rooms it is larger than half, and nobody has ever put the two numbers next to each other.

Someone absent from the numbers is absent from the decisions

Distorted  the forecast for the night
Distorted  their visit interval
Distorted  how you hold seats

⚠️ The third does the damage. Nothing is held for them, so on a busy night you turn away the person who has been coming longest.


"Just get them to book" fails for a reason

Not booking  is part of what they like

⚠️ They come when they feel like it, and not having to decide in advance is the point.   ⇒ Asking them to book is asking them to give up the thing that makes     them a regular, for your convenience.


Change the counting, not the guest

Recording bookings  records intentions
Recording arrivals  records facts

⚠️ A booking is a forecast. A visit is what happened.   ⇒ Only one of those is worth building a picture of a guest from.

And do not add a step for them

Asking for a name at the door  is a booking by another route
Noting what you already know at payment  is not

⇒ ⚠️ The moment it costs the guest anything, the guest stops.


What becomes possible once they exist in the record

You can call them on a busy night, while there is still a table
You can notice when they stop coming
You can staff the night they usually appear

⚠️ The second is the largest. A guest with no bookings can disappear entirely without anybody registering that they have.


The trap immediately afterwards

Now that they are recorded  the urge to send them something

⚠️ Anything sent tells them they are being watched, and the ease they valued disappears.   ⇒ The record exists so you can receive them well, not so you can     pursue them.



Three to hold

Covers minus bookings, by night. The size of the invisible population.

Share of walk-in visits attached to a known guest. Whether the mechanism is working.

Walk-in regulars not seen in sixty days. The signal that did not previously exist.

Where the record has to sit

If tabs attach to tables, walk-ins are anonymous by construction, and no amount of reporting will recover them. The fix is upstream of every report.

tasteck lets a visit attach to a guest record without a booking, so a regular who never reserves still accumulates a history — and still shows up on the list when he stops coming.

He has been coming for two years. Your system has met him for the first time, every time.


Read next

Free, no signup, ~5 minutes

Map out your operations in 5 minutes

Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.

Your answers are not stored. The assessment runs entirely in your browser.

Try tasteck free for 30 days

No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.

  • No card required
  • Free data migration support
  • All features unlocked for 30 days