Skip to content
See the demoStart free
Use Case

Build a Restaurant Email List From Scratch

The job to be done

Go from having no way to contact your guests to owning a list you can fill a quiet Tuesday with.

A restaurant meets hundreds of people a month and usually cannot contact a single one of them. The booking platform owns the diner. The delivery app owns the diner. The review site owns the diner. An email list is the one channel where the relationship is yours, no algorithm sits in the middle, and a quiet Tuesday can be addressed directly rather than discounted publicly.

Why the WiFi login works where cards and table QR codes stall

Paper comment cards get filled in by whoever likes stationery. QR codes on tables need a reason to scan and a staff member to explain them. Loyalty apps ask a guest to install software before they have decided they like you. The WiFi login is different because the guest initiates it, they want something specific in return, and the exchange happens at the exact moment they have sat down and committed to staying. It is the only capture point in a restaurant where the guest is asking you for something first.

What to actually send, and how often

A list only stays valuable if the mail is worth opening. Restaurants that succeed here send fewer, better messages tied to something real: a menu change, a one-night event, a seasonal opening, a table release. Restaurants that fail send a discount every Thursday until the discount becomes the only reason anyone comes, and the list trains itself to wait. The honest test before pressing send is whether a regular would be mildly annoyed to have missed this. If not, do not send it.

  • A welcome message within a day of capture, while the venue is still fresh in memory.
  • Menu and seasonal changes, which are the messages guests actually forward.
  • Event and limited-run announcements, where scarcity is genuine rather than manufactured.
  • A small number of genuinely quiet-night offers, used sparingly enough that they still move people.
  • A yearly re-permission message to anyone who has not opened anything in a long time.

Segment on the two things WiFi actually knows

You do not need a data science function. WiFi gives you two segmentation axes for free. The first is recency, meaning when the guest last connected, which separates active regulars from people who came once in spring. The second is frequency, meaning how many distinct visits their identifier has produced, which separates a loyal weekly diner from a tourist. Those two axes alone let you send a different message to a first-timer, a regular and a lapsed guest, and that difference in relevance is worth more than polishing the copy of a single blast.

A worked example, with the assumptions stated

This is illustrative arithmetic, not a measured result. Suppose your dining room turns over 200 guest devices a month and 60 percent complete the portal form. That is 120 captures a month, or about 1,440 in a year before any deduplication for repeat visitors. Deduplicate at, say, 30 percent repeat rate and you finish the year near 1,000 unique consented contacts. Whether that list is worth anything depends entirely on the send discipline described above. A thousand people who open your mail is a business asset. A thousand people who mute it is a storage cost.

List hygiene, which is boring and decides everything

Deliverability is the difference between a list and a rumour. Bounced addresses need removing rather than retrying. Guests who have not opened anything in a year need either a re-permission message or removal. Unsubscribes must process instantly and visibly, because a guest who cannot get out will mark you as spam instead, and spam complaints follow your sending domain around for a long time. None of this is glamorous, and all of it is why some restaurant lists still work in year three.

How to set it up

In order. Skipping a step here is usually why a portal ends up showing a spinner instead of a login screen.

  1. 1

    Put the portal in front of the guest network

    Set up VoqadoWiFi as the external captive portal on your Omada or UniFi controller, with the guest SSID open and staff traffic on a separate protected network.

  2. 2

    Make the trade explicit on the splash page

    Say what the guest gets for the address in one sentence, above the field. First look at menu changes and event nights is a real offer. "Join our mailing list" is not.

  3. 3

    Connect an email platform before you collect anything

    Wire a webhook or export path into whatever sends your mail, so captures flow out continuously rather than sitting in the portal while their memory of you fades.

  4. 4

    Build the welcome message first

    Before any campaign, set up the one message that goes to every new capture within a day. It confirms the address, sets the expectation for frequency, and gives the guest a reason to keep you out of the junk folder.

  5. 5

    Brief the front of house

    Staff need one sentence they can say when a guest asks for the password: the network is open, the login screen appears by itself, and there is no app to install. Confused guests abandon the form.

Who this suits

The venue types where this job comes up most often, and where the data the portal produces is dense enough to act on.

Independent restaurants without a chain marketing function
Bistros and neighbourhood dining rooms with regular custom
Bars and gastropubs with event programming to announce
Coffee shops building a weekday morning habit
Small groups running two or three sites from one list
Hotels with a restaurant that needs its own local audience

Run this on your own network first

The Starter plan is free forever: one location, 500 logins a month, a branded splash page and consent logging. Growth is $49 a month and covers up to three locations. Works with TP-Link Omada and Ubiquiti UniFi.

Common questions

How long before the list is big enough to be useful?

It depends entirely on your footfall and your capture rate, so no honest answer is a number of weeks. The useful milestone is not size, it is the first message that fills tables. That can happen long before the list looks impressive, because a small list of recent, consented, local guests is worth more than a large stale one.

Can I import the addresses I already have on paper?

Only where you can show those people agreed to marketing email. An address written on a comment card with no consent wording next to it is not a marketing opt-in, and importing it puts your sending reputation and your compliance position at risk. If in doubt, send a single re-permission message and keep only the people who confirm.

Does this replace my booking platform?

No, and it is not trying to. The booking platform fills tables from people already searching. The list lets you reach people who already chose you once, on a night when nobody is searching. They solve different problems and the second one is the one you own.

What does it cost to run for one restaurant?

The Starter plan is free forever with one location and 500 guest logins a month, which suits a quieter dining room; a busy one may pass it, and guests are never cut off if you do. Growth is $49 a month and covers up to three locations and 5,000 logins, so a single busy restaurant or a small group runs on one subscription. Enterprise is custom priced, with unlimited logins and locations and setup help for every venue.

Read next

These jobs share the same plumbing, so operators normally set them up in sequence rather than one at a time.

Stop reading.
Set it up in an afternoon.

Free forever on Starter: one location, 500 logins a month, branded splash page and consent logging. Enough to see the login, the consent record and the guest list working on your own network; campaigns and visit history are on Growth.

TP-Link Omada and Ubiquiti UniFi  ·  No card required