The Guest Who Books For Someone Else

An assistant books it. A host arranges it for clients. A partner books for a group. The name on the booking and the people in the room are different, and your record only knows one of them.

What breaks

The history attaches to the wrong person. ⚠️ Your records show a guest who has been twelve times and has never actually been in the building.

The people who came are invisible. No history, no preferences, no recognition on their next visit — even though they have been three times.

The wrong person gets the follow-up. Communications go to the booker, who did not experience the evening and cannot answer questions about it.

Nobody knows who the relationship is with. ⚠️ The most important gap. If the booker leaves their job, does the business follow them or stay with the company? Most venues cannot answer this, and it is the difference between losing one contact and losing an account.

The three arrangements

They look similar and behave completely differently:

Administrative booking. An assistant books on behalf of someone. The relationship is with the person attending, and the booker is a channel.

Host arrangement. Somebody brings clients or guests. ⚠️ The relationship is with the host — the attendees may never return without them.

Group organiser. One person from a social group books each time. The relationship is with the group, and the organiser can change.

⚠️ Treating all three the same is why follow-up frequently lands wrong — and the fix is one question at the time of booking.

The question to ask

"Will you be joining?"

One line, natural to ask, and it distinguishes all three cases immediately. Add: who should we contact about the evening itself.

⚠️ Nobody asks this, and it costs one sentence at the point where the information is freely available.

Holding both ends

Record the booker and the attendee. Both, linked, on the same booking. Not one field into which somebody types whichever name they were given.

Note who the relationship is with. ⚠️ This is a judgement, and it should be written down — the person serving them in six months cannot infer it.

Recognise the attendee on arrival. They are the one having the experience. Being recognised is worth more to them than to the person who booked.

Thank the booker separately. They are frequently doing invisible work and are never acknowledged — a small thing that keeps the booking coming back.

The corporate version

Where the booker is an account rather than a person.

Record the company as well as the individual. ⚠️ People change jobs; accounts persist — and a record attached only to a person leaves when they do.

Ask about the occasion. Recurring corporate occasions are predictable revenue, and a diary note a year ahead is the cheapest booking you will ever generate.

Three to hold

Bookings where the booker did not attend. ⚠️ Usually a larger share than expected, and the size of the blind spot.

Attendees with no record of their own. The people you are failing to recognise.

Whether the relationship holder is written down. For your largest repeat bookings, someone should be able to say whether it is the person or the company.

Where the record has to sit

Booker and attendee have to be separate, linked, on the same booking. A single name field forces a choice between recording who arranged it and recording who came, and whichever you choose, the other is lost permanently.

tasteck keeps bookings against guest records, so the person who arranged an evening and the people who attended it can both be held.

They have been in three times. Your system has never heard of them, because someone else's name was on the booking.