The Guest Who Only Comes for One Person

A guest has come in every fortnight for two years. Excellent spender, no trouble, knows the staff.

They have never once come in when a particular person was not working.

Nobody noticed, because from the venue's side they look like a regular. They are not. They are somebody else's regular, using your room.

Why this is worth measuring rather than worrying about

The instinct is to treat this as a risk to be reduced. That is only half right.

Personal loyalty is why they come at all. A room with no personal relationships is a room people visit rather than return to. Trying to reduce the dependency by discouraging it destroys the thing producing the revenue.

The useful question is not "how do we stop this" but "how much of our revenue is in this shape, and do we know which people carry it."

The measurement

For each of your top guests by spend, one number:

What share of their visits coincided with a specific member of staff working?

You are looking for the extremes. A guest whose visits are spread across everyone is loyal to the venue. A guest at ninety-plus percent with one person is loyal to that person.

⚠️ The middle of the distribution is not interesting. The tail is.

Then flip it: for each member of staff, how much revenue is attached to guests in their tail. That number is what walks out if they leave, and it is frequently concentrated in two or three people.

What to do with the answer

Three things, in the order they actually work.

Know it. Most of the value is here. A departure that is a surprise costs far more than one you saw coming, and the number tells you which departures to see coming.

Build a second relationship, deliberately and early. Not a handover — a second familiar face while the first is still there. This is the only intervention that reliably works, and it has to happen years before it is needed.

Capture what the person knows. Preferences, history, the things that make the guest feel recognised. ⚠️ The relationship does not transfer, but the knowledge can — and the knowledge is what makes the second relationship possible instead of starting from nothing.

What does not work

Rotating staff to break the dependency. The guest stops coming. This is tried surprisingly often and it fails almost every time.

A handover at the point of departure. Two weeks' notice is not enough time to transfer two years of relationship. By then the useful move is a graceful introduction, not a transfer.

Pretending the guest is the venue's. They will follow the person if the person goes somewhere else, and treating that as disloyalty gets you neither the guest nor a good reference.

The part people avoid saying

Some of these guests will leave when the person leaves. That is not a failure of retention; it is the nature of the business, and a plan that assumes otherwise will be wrong.

What is a failure is finding out afterwards — losing the guest and only then discovering they were a fifth of one person's book.

The related number worth having

Requests as a share of visits, per member of staff.

A person with a high request rate is carrying relationships, which is valuable and also concentrated. A person with a low one is serving whoever is in front of them. Both are needed; a room made entirely of the first is fragile and a room made entirely of the second does not retain anyone.

Knowing the mix tells you what your room is, which is more useful than either number alone.

A companion piece on the same subject

　This site has a second page on a guest attached to one person: 　The Guest Who Only Deals With One Person.

⚠️ The two were written independently and cover much the same ground. 　 They are linked here so a reader who wants a second angle can find it, 　 rather than meeting whichever one a search happened to surface.

---

Three to hold

Guests above eighty percent overlap with one person. Your concentration list.

Revenue attached to each person's tail. What a departure actually costs.

Requests as a share of visits, per person. Whether your room runs on relationships or on service, and in what proportion.

Where the record has to sit

If visits are not linked to who was working, none of this is computable — and in most venues that link exists in the rota and in the booking, but never in the same place.

tasteck keeps requests, visits, and shifts on one record, so which guests only come when this person works is a query rather than something a manager half-suspects.

They were never your regular. That is worth knowing before the notice period, not after.

---

Read next

• When Someone Stops Being Requested
• Guest CRM for Rooms Where Everyone Pays Cash
• Night Venue Scheduling: Why the Roster Never Matches the Room
• The Regular You Lost Without Noticing
• Why Your Best Staff Leave in Month Four
• Douhan: The Shift That Starts Before the Shift
• The Two Tuesdays
• Who Types The Request In
• The Request Fee Nobody Explained