Guest Wi-Fi in cafés and restaurants: for a business with no IT staff

Guest Wi-Fi in a café or restaurant has two requirements: do not keep the guest waiting, and record who connected. There is a third that nobody writes down — the system must not ask anything of you. With no IT staff, a setup that needs weekly attention will not survive.

The guest side: the 20-second rule

A guest who sits down and meets a long form gives up and switches to mobile data. Then you have neither a record nor a welcome screen.

A practical measure: from taking the phone out of a pocket to being online should not exceed 20 seconds.

What makes that possible:

• One field. A phone number is enough. Do not ask for name, surname and date of birth; it slows things down and collects data you do not need.
• A page that opens by itself. The guest should not have to open a browser and type an address.
• Device remembering. A regular reconnects on the second visit without waiting for a code. In a café this is the single most useful setting.

Your side: set it and forget it

A setup that does not create work for you looks like this:

• A device sits at the network edge and guest traffic passes through it.
• Records are kept and archived automatically.
• Disk, services and balance are monitored; if something breaks, you get an e-mail.
• When SMS credits run low, an alert arrives and you top up.

There is no weekly or monthly chore. You only respond to alerts.

Should you set a time limit?

For cafés this is a business decision, not a technical one. Both approaches are common:

With a limit: if table turnover matters, a one- or two-hour session is reasonable. When it expires the guest can sign in again; access is not cut off for good.

Without: in places that encourage lingering, a limit backfires. Set only a speed limit instead and let it balance heavy usage.

Either way, a speed limit makes sense. One guest's large download can slow down even your card terminal.

Separate the terminal and the printer

The devices that most often end up on a café's guest network are the card terminal, the ordering tablet and the kitchen printer. On the same network as guests they cause two problems: they slow down when it is busy, and guest devices can see them.

Two options:

1. A separate network. The cleanest. Terminal and printer live on the staff network.
2. MAC exemption. If you cannot build a separate network, add those devices' MAC addresses to an exemption list; they connect without seeing the sign-in screen.

How to use the welcome screen

In a café the portal has some marketing value, but it does not take overdoing:

• Logo and brand colour.
• A short notice: a new menu, breakfast hours, a loyalty card.
• A redirect to your menu page or social account after sign-in.

Put nothing on it that delays the guest. Shown after sign-in rather than on it, a notice is both read and unobtrusive.

How many devices to expect

A rough measure: 1.2–1.5 times the number of seated guests. In a 40-seat café, 50–60 concurrent devices in the evening is realistic.

How many devices your line can carry at once matters as much as its speed. Size your capacity against that number.

Chains

With more than one site, two things change:

• There is a device per site, and they need to be watched centrally.
• The welcome screen should be shared, with the branch name changing automatically.

As the number of sites grows, "checking each one separately" stops being sustainable. A setup without central monitoring starts causing trouble after the third branch.

Setup checklist

1. Separate the guest network from the terminal and staff network.
2. Route guest traffic through the gate device.
3. Turn on SMS sign-in and enable device remembering.
4. Set a speed limit; decide on a time limit to match your style of business.
5. Define exemptions for fixed devices.
6. Brand the welcome screen.
7. Test at the busiest hour, from the furthest table, with your own phone.