The Question You Ask Every New Guest
Most venues capture a name and a phone number on a first visit and lose the one thing that would bring the guest back. What to ask, when to ask it, and why longer forms produce worse data.
A new guest arrives. Somebody takes a name and a number.
That is enough to make a booking and almost useless for making them come back.
What the second visit actually needs
Think about what would make a returning guest feel recognised. It is never their phone number.
It is that somebody remembered what they liked, who they got on with, and why they came.
None of those get captured, because the intake was designed for booking rather than for the relationship — and it has been that way so long that nobody notices.
The three fields that matter
Who they asked for, or who they ended up with. The single most predictive field. A returning guest almost always wants the same person, and if that is not recorded, the second visit is a coin flip.
What they came for. A birthday, a client, an ordinary Tuesday. Frequently visible from the booking itself and almost never written down.
One thing about them. Anything. What they drank, that they hated the music, that they are in from out of town. One line is enough to make the second visit feel like a return rather than a first visit repeated.
Why longer forms make this worse
The instinct is a proper intake form. It fails, reliably.
A form at the door competes with the queue. It loses.
A guest answering questions is a guest being processed. The tone of the visit is set in the first ninety seconds, and an interview is the wrong opening.
Fields nobody fills get filled with anything. ⚠️ A form with twelve fields produces worse data than one with three, because staff learn to complete it rather than to record it.
Three fields, written after the guest sits down — by the person who served them, in their own words — beats any form.
When to capture it
Not on arrival. On departure, or after.
By the end of the night the person who served them knows all three answers without asking a single question. Arrival is the worst moment: nobody knows anything yet and the guest is being processed.
⚠️ The window closes fast. By the next shift it is a guess, and a guess in a guest record is worse than a blank — because it will be read as fact by whoever serves them next.
The check that shows whether it is working
Not how many records have the fields filled.
Take ten guests who came twice. Could the second visit have been improved by what was recorded on the first?
If the answer is mostly no, the fields are being completed rather than used, and adding more will not help.
The one that pays for itself
Who they asked for.
Get this one right and the second visit gets substantially better with no other effort. Get it wrong and everything else is decoration.
⚠️ And it is the field most often missing, because at booking time it is frequently not decided yet — which means it has to be written after the visit, and after-the-visit is exactly what does not happen.
What not to record
The same line as anywhere else: behaviour, not judgement.
"Prefers the corner table" is useful. "Difficult" is not — it is a verdict passed to the next person, who will now treat them accordingly and produce the thing the note predicted.
⚠️ What you may store about a person, for how long, and what you must disclose varies by jurisdiction. Confirm the rules before you build the habit — that is a question for your counsel, not an operations decision.
Three to hold
Share of first visits with a person recorded. The field that decides the second visit.
Share with any note at all. Blank means the moment was missed, not that there was nothing to say.
Second-visit rate for guests with a note versus without. ⚠️ Correlation, not proof — but if there is no gap at all, the notes are not being used, and that is worth knowing before you ask anyone to write more of them.
Where the record has to sit
If the booking holds a name and the visit holds a tab and the person who served them holds the memory, the second visit starts from nothing. That is the whole mechanism.
tasteck keeps the person, the visit, and the note on one guest record, so the three fields written on a Friday are in front of whoever takes the call three weeks later.
They will come back once out of curiosity. What decides the third visit was written down — or not — on the first.
Read next
Related articles
"Same Girl As Last Time" — Answering In Three Seconds
When a regular rings and asks for whoever he saw last, a desk that has to flip through booking sheets loses him. Here is what to look up — last entertainer, last date, usual request — how to check she's working today, and what to offer when she isn't.
Entertainers' Notes On Clients — Fewer Fields, And A Set Time To Read Them
Notes entertainers keep on clients stop being written when there are too many fields, and are useless if nobody reads them before the next booking. Here is how to cut them to five fields, put reading time just before the session, and separate what the venue sees from what stays personal.
The First 90 Days After Moving Your Client Records
Moving client records off paper and spreadsheets is not finished on migration day. Over the next three months duplicates creep back, categories drift and unused fields pile up. Here is what to check in month one, two and three, and the 30-minute monthly habit that keeps records usable.
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