You have served thousands of people. Tomorrow you want to tell four hundred of them something. There is no way to do it — the names are in a phone, a follower count and a system you do not own.

Something changes at short notice. A closure, a new night, a date moved. You want to tell the people who come regularly.

⚠️ There is no way to do it. The names are in somebody's phone, in a follower count you do not control, and in a booking system that holds them but was never set up to send anything.

⚠️ What this page cannot tell you

⛔ What consent you need to contact anybody, what you must record, how long you may keep it and what people can ask you to delete are data protection questions with specific answers where you are.

⛔ This page tells you none of that and is not a substitute for advice. ⭕ Ask before you collect anything, and again before you send anything.

⭕ What follows is the operational half: whether a reachable list exists at all, which is the question almost nobody has asked.

The four places the names actually are

None of these is a list you can send to.

A follower count

⚠️ ⭕ You do not decide who sees a post. The platform does, and the share of followers reached has fallen every year for a decade. A follower is not a contact.

⇒ The Staff Account That Is Also Your Marketing

Individual phones

⇒ ⭕ Your best staff have hundreds of guests in their own messages. ⛔ Whose data that is and what may be done with it is a question for your adviser — but operationally, it leaves when they do.

⇒ The Guest Who Messages Instead Of Calling

A booking system that holds names but does not send

⭕ The data is there and the function is not, or the function exists and nobody has ever used it. Both end in the same place.

⇒ The Data You Cannot Take With You

And a stack of paper nobody typed up

⚠️ ⭕ Sign-up cards, a book by the door, a form from an event. Collected with intent and never entered anywhere, which is worse than not collecting it.

Why it stays this way

Four reasons, and none of them is that nobody thought of it.

There is nothing to send most weeks

⇒ ⭕ A list only justifies itself when something changes. Between those moments it is an unused thing, so it never gets built.

Followers feel like a list

⚠️ ⭕ A number that goes up looks like progress. It is the single most common substitution here, and it holds until the week you actually need to reach people.

Collecting feels like an imposition

⭕ Asking for contact details at the door or the table feels like sales. ⚠️ It is only an imposition if there is nothing in it for them — which is a design problem, not a reason not to.

And nobody owns it

⇒ ⭕ Not the manager, not the door, not whoever runs the social account. A thing with no owner does not get built.

⇒ The Loyalty Scheme Nobody Uses

The test

⭕ One question, and it takes no preparation.

"If we had to tell four hundred regulars something tomorrow, how?"

⇒ ⭕ Most operators reach for the social account, then pause. That pause is the finding.

Then ask how many would actually see it

⚠️ ⭕ A post reaching a small fraction of followers is not four hundred people. ⭕ Anybody who runs the account can tell you the real number, and it is usually lower than the room expects.

And ask who would have to be asked

⭕ If the answer involves asking a member of staff to message people from their own phone, you do not have a list — they do.

What a usable list needs

Four properties. Nothing about size.

It is yours

⛔ ⚠️ If it lives only inside a platform's account, it is not yours in any sense that survives that account being closed. ⭕ You need it somewhere you can export it from.

It has a way to reach people that you control

⇒ ⭕ Whatever channel your guests actually use. ⛔ What you may send, and what consent it requires, is the question for your adviser — settle it before you build anything.

It records when and how somebody joined

⚠️ ⭕ This matters more than the contact detail itself. ⛔ It is also what any question about consent will turn on, which is another reason to ask before collecting.

And it is connected to what they actually did

⭕ A contact detail with no visit history is a name. ⚠️ Joined with visits and spend, it becomes the only way to tell a regular from somebody who came once.

⇒ What a Regular Is Actually Worth

Where the details already exist

⭕ Most venues are collecting far more than they realise and keeping none of it.

Bookings taken by phone and message
Deposits and pre-payments
Event and private hire enquiries
Anything with an emailed receipt or confirmation
Wi-Fi sign-ins, where you run it

⚠️ ⭕ Each of these already involves somebody giving you a way to reach them. ⛔ Whether you may then use it for anything else is exactly the question to ask your adviser — the operational point is that the detail is already passing through your hands and being discarded.

⇒ The Booking Channel You Do Not Control

What to do with it once it exists

Three uses, in order of how much they return.

Telling people something changed

⭕ This is the reason to build it and it justifies the whole effort in one use. A closure announced three weeks ahead to the people it affects is worth more than any campaign.

Noticing who stopped coming

⇒ The Guest Who Stopped Coming and Nobody Noticed

And knowing how many regulars you really have

⇒ How Many Regulars Do You Actually Have

How to lose it

Four ways, all common.

Sending too often

⚠️ ⭕ The fastest way to make a list unusable is to use it weekly with nothing to say. ⭕ A list used four times a year for real news keeps working.

Sending the same thing to everybody

⇒ ⭕ Somebody who comes every week and somebody who came once do not want the same message. Sending both the same thing loses the first one.

Letting it go stale

⇒ The Guest List You Have Never Cleaned

And leaving it with one person

⭕ ⚠️ If one person holds the login and the routine, the list is as fragile as the phone it replaced.

What good looks like

The tomorrow test

Ask how you would reach four hundred regulars tomorrow. ⇒ A concrete answer means a list exists. A pause means it does not.

The ownership test

⚠️ Ask what happens to it if a platform account is closed. If the answer is "we lose it", it was never yours.

The joined-up test

Working     — contact details sit with visit history in one place
Not working — names in one system, visits in another, and nothing joins them

Three to hold

1  A follower count is not a list — you do not decide who sees a post
2  The details already pass through your hands at booking, deposit and enquiry
3  It justifies itself the first time something changes at short notice

Where the record has to sit

Contact details, when and how somebody gave them, and what that person has actually done — in one place you can export from, not split between a platform, a member of staff's phone and a book by the door. ⛔ Settle what you may collect and send with your adviser first. Kept there, the week something changes you can tell the people it affects, and you can see who stopped coming before they are gone. Kept nowhere, you have served thousands of people and cannot reach a single one of them without asking somebody to hand over their own phone.