Guest WiFi for Restaurants Kenya: The Chalkboard Password and What It Costs
Guest WiFi for restaurants Kenya is a topic most owners consider settled the moment they write the password on a chalkboard, and the chalkboard is where the problems begin. The password is shared with the till, the card machine and the manager’s laptop, so every customer who connects is on the same network as the restaurant’s money.
It never changes, so people in the building next door, the boda riders outside and last month’s customers are all still using it, and the connection that was fine at ten in the morning is unusable at one. One table streams a football match and the family across the room cannot load a menu.
Nobody knows how many people connected, whether any came back, or whether the WiFi did anything for the business at all beyond being expected.
And when it stops working — which it does, because a domestic router in a hot corner behind the coffee machine was never meant for forty devices — a customer asks the waiter, the waiter asks the manager, and the manager restarts it and hopes. None of this is the owner’s fault. Restaurant WiFi is treated as a utility like water, and it is actually a small piece of infrastructure with commercial, security and customer-experience consequences that are worth thinking through once.
This guide covers that: whether to charge, the tension between WiFi and table turnover, what guests expect, replacing the chalkboard with a portal and codes, keeping guests off the till, bandwidth fairness, coverage and capacity, the portal as a brand and marketing touchpoint with consent, what the restaurant should and should not learn from it, reliability, hardware and cost.
The value of guest WiFi for restaurants Kenya done properly is a service that works at one o’clock and does not expose the till, and guest WiFi for restaurants Kenya that runs through a portal with codes and time limits is both safer and more useful than the chalkboard — which is why guest WiFi for restaurants Kenya deserves an hour of thought rather than a password.
Table of Contents
- Why Restaurants Offer WiFi at All
- The Kenyan Context
- Free, Paid or Free With Purchase
- The Dwell-Time Tension
- Cafés, Restaurants and Bars Differ
- What Guests Actually Expect
- The Chalkboard Password Problem
- The Captive Portal
- Access Codes With Purchase
- Time-Limited Sessions
- Bandwidth Fairness Per Guest
- Capacity at Peak
- Coverage: Dining, Outdoor and Back of House
- Separating Guests From the Till
- Point-of-Sale Security
- Staff Use
- The Portal as a Brand Touchpoint
- Marketing Capture and Consent
- Social Login and What It Shares
- Review and Feedback Prompts
- Recognising Repeat Visitors
- What the Restaurant Learns and Should Not
- Content and Acceptable Use
- Streaming, Calls and Etiquette
- Reliability and What Failure Costs
- Power
- The Connection Behind It
- Hardware
- Running It Without an IT Person
- Multi-Outlet Chains
- Bars and Nightlife
- Hotel and Lodge Restaurants
- Data Protection
- Costs and Setup
- Frequently Asked Questions
Why Restaurants Offer WiFi at All {#why-offer}
The reasons are worth stating because they determine the design.
Guests expect it, and its absence is noticed where its presence is not.
Longer visits in formats where that is wanted.
Remote workers and meetings choosing venues by connectivity.
Guests sharing their visit online, which is marketing the restaurant does not pay for.
A touchpoint for the brand at the moment the guest is present.
A way to learn something about visitors, within limits.
Competitive parity, since the café next door has it.
Each pulls the design a different way, and guest WiFi for restaurants Kenya built for remote workers differs from guest WiFi for restaurants Kenya built for a lunch venue that wants tables turned in forty minutes.
Decide what it is for before deciding how to provide it.
The Kenyan Context {#kenyan-context}
Local conditions shape restaurant WiFi specifically.
Mobile data cost makes venue WiFi genuinely valuable to guests, since a customer on a limited bundle will choose the café with reliable WiFi.
Remote and hybrid work has grown and cafés are workspaces.
Football and streaming demand in bars and restaurants with screens.
Power interruptions drop the router along with the lights.
Heat in kitchens and behind counters kills domestic equipment.
Masonry construction limits coverage from a single router.
Dense urban locations have many neighbouring networks.
Guest WiFi is frequently shared with the point-of-sale system, which is the security problem the separation section addresses.
Boda riders and passers-by using an unprotected network is a known issue.
The chalkboard password is the default because nobody suggested an alternative, and guest WiFi for restaurants Kenya that replaces it with a portal is a modest change with a large effect, since guest WiFi for restaurants Kenya that is controlled serves the guests who are actually there.
Free, Paid or Free With Purchase {#free-paid}
The commercial model is the first decision.
Free and open, which is simplest and attracts everyone including people who are not customers.
Free with purchase, where the access code comes on the receipt or from staff.
Paid, where guests buy a package, which suits some formats and is resented in others.
Tiered, with a free basic allowance and a paid faster option.
Free with purchase is the practical default for most restaurants, since it serves customers, excludes non-customers, and costs the guest nothing.
Paid suits venues where guests stay long and consume heavily, including some cafés serving remote workers.
Open suits almost nobody, since it fills the network with people who bought nothing.
Choose for the format, since guest WiFi for restaurants Kenya that hands a code with every order has a control the chalkboard lacks, and guest WiFi for restaurants Kenya that charges a lunch customer for thirty minutes of access has annoyed them for very little.
The Dwell-Time Tension {#dwell-time}
WiFi keeps guests longer and whether that is good depends on the format.
A café selling coffee to remote workers wants dwell time, since a guest who stays three hours buys more.
A lunch restaurant with a queue wants tables turned, since a guest who lingers over WiFi costs a seating.
A bar wants guests to stay and drink.
A family restaurant wants a pleasant visit of normal length.
The tension is real and it is managed through session length, since guest WiFi for restaurants Kenya with a sixty-minute session at a lunch venue is generous to a diner and discouraging to a squatter, and guest WiFi for restaurants Kenya with unlimited sessions at a café serving laptops is what those guests came for.
A second code for guests who order again extends the visit for those who are spending.
Set it consciously, since a session length that was never chosen is the default and the default suits nobody in particular.
Cafés, Restaurants and Bars Differ {#formats}
Format determines almost every parameter.
Cafés with laptops need capacity for sustained use, sockets, and long sessions.
Fast-casual and lunch venues need short sessions and high throughput of connections.
Sit-down restaurants need reliable coverage across the dining area and modest sessions.
Bars need capacity for many phones simultaneously and tolerance for video.
Food courts and shared spaces need higher density and clear branding so guests know whose network they are on.
Outdoor and garden venues need coverage outside.
Design for the format, since guest WiFi for restaurants Kenya configured identically for a café and a lunch canteen serves one of them badly, and guest WiFi for restaurants Kenya that set session length, bandwidth and capacity for what the venue actually is works.
What Guests Actually Expect {#expectations}
Expectations are modest and specific.
That it exists.
That it connects without difficulty.
That it works for messaging, browsing, social media and the occasional call.
That it does not require handing over personal details to get online.
That it is fast enough not to notice.
That it does not drop mid-visit.
That the process of getting on is quick, since a guest who must register with three fields and confirm an email has been asked to work for a coffee.
They do not expect gigabit speed, and guest WiFi for restaurants Kenya that delivers modest consistent speed to everyone serves better than guest WiFi for restaurants Kenya that delivers fast speed to the first ten connections and nothing to the rest.
Meet the modest expectation reliably.
The Chalkboard Password Problem {#chalkboard}
The chalkboard is the default and its problems are structural.
The password never changes, so everyone who ever had it still has it.
Passers-by, neighbours and former customers consume capacity.
The guest network is the same network as the till, the card machine and the office.
No session limits, so a device stays connected indefinitely.
No idea who or how many are connected.
No fairness, so one heavy user degrades everyone.
No brand touchpoint, since the guest sees a system dialog rather than the restaurant.
Changing the password disconnects staff devices and confuses regulars.
It is the worst of every option, and guest WiFi for restaurants Kenya that replaces it with a portal and codes addresses every point above at once, since guest WiFi for restaurants Kenya on a separate network with time-limited codes is controlled where the chalkboard is not.
The Captive Portal {#portal}
The portal is the guest’s front door and it replaces the password.
The guest connects to the network and a page opens.
The page shows the restaurant’s name and branding.
The guest enters a code, or taps to accept terms, or chooses a package.
Access opens.
The session runs for its allowed time or data.
It should be fast and simple, since a portal that loads slowly or asks too much loses guests before they are online.
It should work on the phones guests actually carry, including older handsets.
Minimal fields, since guest WiFi for restaurants Kenya portals that require a name, email and phone to get online are collecting data the guest did not want to give, and guest WiFi for restaurants Kenya that opens on a code from the receipt has asked for nothing personal.
Test it across devices before opening, since a portal that does not appear on some phones is a support problem for the waiters.
Access Codes With Purchase {#codes}
Codes tie access to custom and they are simple to run.
A code printed on the receipt.
A code given by staff on request.
A voucher card at the counter.
Single-use so a code serves one device or one session.
Time-limited so it expires.
Generated by the system rather than by staff, since a code the staff invent is a password by another name.
Reissued for a second order to extend the visit.
The receipt code is the cleanest, since guest WiFi for restaurants Kenya that prints a fresh code on every receipt has tied access to purchase without any staff effort, and guest WiFi for restaurants Kenya that asks the waiter for a code each time has added a task to a busy person’s shift.
Where the till cannot print codes, a printed batch at the counter works.
Time-Limited Sessions {#time-limits}
Session length is the tool that manages dwell time and capacity.
A session that expires after a defined period.
Length chosen for the format, from thirty minutes at a lunch counter to several hours at a café.
Extension by a new code.
Expiry that returns the guest to the portal rather than silently dropping them.
Device limits per code.
It also clears the network, since a session that expires frees the capacity a departed guest’s phone was holding, and guest WiFi for restaurants Kenya with expiring sessions keeps the connected count close to the guests actually present, while guest WiFi for restaurants Kenya with no expiry accumulates every device that ever connected.
Communicate the length, since a guest who knows they have an hour is not surprised when it ends.
Bandwidth Fairness Per Guest {#fairness}
One guest should not be able to consume the connection.
A per-session bandwidth limit so every guest gets a share.
Enough for messaging, browsing, social media and a call.
Not enough for one device to stream in high definition while others cannot load a page.
Different limits for different packages where the venue tiers access.
Aggregate management so the total sold fits the connection.
The limit protects the many from the few, since guest WiFi for restaurants Kenya with a modest per-guest cap gives forty guests a usable connection, and guest WiFi for restaurants Kenya without one gives the first streamer a good connection and everyone else nothing.
Set it and forget it, since fairness applied automatically needs no staff intervention.
Capacity at Peak {#capacity}
The network must handle the busiest hour, not the average.
Count the seats and assume most guests have a phone and some have two devices.
Peak simultaneous connections is the design number.
A domestic router handles a modest number well and degrades beyond it.
Access points designed for density handle more.
Two or three access points across a larger dining room beat one in the corner.
The connection behind it must carry the aggregate, which the connection section addresses.
Test at peak before relying on it, since guest WiFi for restaurants Kenya that works at ten in the morning and collapses at one is failing when it matters, and guest WiFi for restaurants Kenya sized for the Saturday lunch rush works every other hour too.
Coverage: Dining, Outdoor and Back of House {#coverage}
Coverage determines whether every table gets service.
The dining area, which is the priority.
Outdoor and garden seating, which needs outdoor-rated equipment.
Private rooms and upper floors, which need their own access point.
Back of house for staff, on the staff network.
Kitchens are hostile to equipment, with heat and grease, and access points should not be in them.
Masonry walls between areas block signal, as the coverage article explains.
Placement away from the coffee machine, the fridge and the sun.
Survey the space, since guest WiFi for restaurants Kenya with one router behind the counter serves the counter, and guest WiFi for restaurants Kenya with access points placed to cover the dining room and the terrace serves the guests.
Separating Guests From the Till {#separation}
This is the most important section and the one most restaurants get wrong.
The point-of-sale system, card terminals, the manager’s laptop and any back-office system should never be on the same network as guests.
A guest device on the same network can see and potentially reach the till.
A compromised guest device is a threat to every other device on that network.
A separate guest network, isolated from the business network, is the fix.
Client isolation on the guest network so guests cannot see each other either.
The business network on its own password, never shared with guests.
Physical separation where equipment supports it, or virtual separation configured properly.
This is not optional, since guest WiFi for restaurants Kenya sharing a network with the till has put the restaurant’s money one step from every phone in the room, and guest WiFi for restaurants Kenya on an isolated network has removed that exposure entirely.
If nothing else in this guide is done, do this.
Point-of-Sale Security {#pos-security}
The till deserves its own attention beyond separation.
It handles payments and holds transaction records.
Card terminals communicate with payment networks.
M-Pesa till integration where used.
It should be on the business network, isolated from guests.
Wired where possible, since a till on WiFi depends on WiFi.
Default credentials on any point-of-sale device changed.
Updates applied.
Staff access to the point-of-sale system restricted by role.
A till on the guest network is the single most common serious security mistake in hospitality, and guest WiFi for restaurants Kenya done properly starts by moving the till off it, since guest WiFi for restaurants Kenya is only guest WiFi if the till is somewhere else.
Take advice on payment security requirements where card payments are processed, since obligations may apply.
Staff Use {#staff-use}
Staff need connectivity too and it should be managed.
A staff network separate from guests and from the till.
Staff devices on it rather than on the guest network consuming guest capacity.
Reasonable limits so staff streaming does not degrade guest service.
Policy on use during shifts, which is a management matter rather than a network one.
The social media blocking page addresses restricting content on staff networks where an owner wants to.
Do not let staff use the guest codes, since guest WiFi for restaurants Kenya where staff phones consume guest sessions has reduced what guests get, and guest WiFi for restaurants Kenya with a staff network keeps the two apart.
The Portal as a Brand Touchpoint {#brand}
The portal is seen by every guest who connects and it is the restaurant’s page.
The restaurant’s name, logo and colours.
A welcome message.
Today’s special or a promotion.
Opening hours and contact.
A link to the menu.
Social media handles.
It is the one screen every connecting guest looks at, and guest WiFi for restaurants Kenya with a branded portal has used that moment, while guest WiFi for restaurants Kenya with a system dialog has wasted it.
Keep it light, since a portal heavy with images loads slowly on the guest’s data before they are connected.
Update it, since a special from last month on the portal looks careless.
Marketing Capture and Consent {#marketing-consent}
The portal can collect contact details and the way it does so matters legally and commercially.
Optional rather than required, since a guest forced to give a phone number to get online has not consented freely.
Clear purpose stated, whether for offers, a loyalty programme or nothing.
Separate consent for marketing from the act of connecting.
Opt-in rather than pre-ticked.
Easy opt-out later.
Honour it absolutely.
Forced capture produces false details and resentment, and guest WiFi for restaurants Kenya that offers guests a genuine choice to hear from the restaurant collects a list of people who want to, while guest WiFi for restaurants Kenya that demands a number for access collects a list of people who gave a wrong one.
Confirm the position with qualified advice, since collecting contact details for marketing engages the Data Protection Act.
Social Login and What It Shares {#social-login}
Login through a social account is offered by some systems and it has costs.
The guest connects by logging in with a social platform.
The restaurant may receive profile information.
The guest may not realise what they shared.
The social platform receives data about the guest’s visit.
Some guests do not have or will not use social accounts.
It is friction for many guests and a data question for all of them.
A code on the receipt is simpler, faster and collects nothing, and guest WiFi for restaurants Kenya that avoids social login has avoided a question it did not need to ask, while guest WiFi for restaurants Kenya that uses it should be clear with guests about what is shared and should confirm the position with qualified advice.
Review and Feedback Prompts {#reviews}
The portal can invite a review and the invitation should be light.
A prompt at connection or at session end inviting a review.
A link to the review platform.
A brief feedback form for the restaurant’s own use.
Not a barrier to access, since a review demanded before connection is coercion.
Not repeated at every connection for regulars.
Timing at the end of a good visit rather than the beginning.
Never incentivise positive reviews, since it misleads other diners and breaches platform terms.
A light invitation produces reviews from guests who wanted to leave one, and guest WiFi for restaurants Kenya that offers a link after the session has asked once, politely, while guest WiFi for restaurants Kenya that gates access behind a review has produced reviews nobody wanted to write.
Recognising Repeat Visitors {#repeat-visitors}
The system can notice a returning device and the use should be careful.
A device that connected before can be recognised.
Returning guests can be welcomed back on the portal.
Repeat visit counts inform the restaurant about loyalty.
Recognition is of a device rather than a person unless the guest identified themselves.
It should feel welcoming rather than surveilling, since a guest greeted by name from a portal they never registered on may be unsettled.
Use it lightly, and guest WiFi for restaurants Kenya that says “welcome back” without more has been friendly, while guest WiFi for restaurants Kenya that tells a guest how many times they have visited this month has crossed into something else.
What is recognised and retained engages data protection, which the relevant section addresses.
What the Restaurant Learns and Should Not {#learning}
The network produces information and some of it should not be looked at.
Connection counts by hour, which show footfall and peak times.
Session lengths, which show dwell time.
Repeat device rates, which show loyalty in aggregate.
Portal engagement, which shows whether the brand touchpoint is seen.
These are useful and aggregate.
Individual browsing activity is not the restaurant’s business, since monitoring what a guest does online is intrusive and the lawfulness is questionable.
Individual identification without consent likewise.
Aggregate is fine; individual is not, and guest WiFi for restaurants Kenya that reports how many guests connected at lunch has learned something useful, while guest WiFi for restaurants Kenya that logs what each guest looked at has collected something it cannot justify and should not want.
Configure the system to collect the aggregate and not the individual.
Content and Acceptable Use {#acceptable-use}
Acceptable use terms on a guest network are reasonable and their scope should be sensible.
Terms accepted at connection.
Prohibition of unlawful use.
Filtering of clearly inappropriate content where the venue chooses, particularly in family restaurants.
Not blanket filtering that breaks ordinary use.
Fair use so one guest cannot consume everything.
The venue’s position on streaming, which the etiquette section addresses.
Restraint, since a restaurant is not a school and adult guests should be able to browse normally.
Keep the terms brief, since guest WiFi for restaurants Kenya with a one-line acceptance is used, and guest WiFi for restaurants Kenya with a page of terms is scrolled past without reading anyway.
Streaming, Calls and Etiquette {#etiquette}
Guest behaviour on the network affects other guests and the room.
Video streaming consumes bandwidth and, without headphones, disturbs neighbours.
Video calls in a dining room are a social question as much as a network one.
Per-guest bandwidth limits handle the network side.
House rules handle the social side, and they are the restaurant’s to set.
Bars with screens may want streaming; family restaurants may not.
The network can limit what the room cannot police, since guest WiFi for restaurants Kenya with a per-session cap makes high-definition streaming impractical without anyone having to say anything, and guest WiFi for restaurants Kenya that relies on staff to ask a guest to stop streaming has given the waiter an awkward job.
Reliability and What Failure Costs {#reliability}
WiFi that fails is worse than no WiFi.
A guest who expected it and cannot connect is more annoyed than one who never expected it.
Staff become support, which they are not.
The manager restarts the router mid-service.
Reviews mention it.
Remote workers do not return.
Causes include domestic equipment beyond its capacity, heat, power interruption, an inadequate connection, and the chalkboard network full of non-customers.
Each is addressed by the sections above, and guest WiFi for restaurants Kenya built on proper equipment with sessions that expire and a connection that carries the peak rarely fails, while guest WiFi for restaurants Kenya on a domestic router with an eternal password fails weekly.
Monitor it, since a system that shows the operator the network is down before a guest complains is worth having.
Power {#power}
Power interruption drops the WiFi with the lights and guests notice.
The router and access points reboot on every interruption.
Reconnection takes minutes and every guest drops.
A small battery backup keeps the network up through short interruptions.
It is inexpensive relative to the equipment it protects.
Generator-backed venues should include the network equipment.
Surge protection, since restaurant electrical environments are noisy.
The till’s power matters too, and a restaurant that backed up the till and not the WiFi has half a solution, while guest WiFi for restaurants Kenya with the network equipment on the same backup as the till stays up when the lights go, and guest WiFi for restaurants Kenya without it drops every guest several times a week.
The Connection Behind It {#connection}
The WiFi is only as good as the connection feeding it.
Bandwidth must carry the peak number of guests at the per-guest limit.
Upload matters for guests posting photos and making calls.
Consistency at lunch and dinner rather than headline speed.
Fibre where available; wireless where not, as the comparison article covers.
A separate business connection for the till where reliability warrants it.
Backup connectivity where the venue depends on it, including for card payments.
Size it against the guest count, since guest WiFi for restaurants Kenya on a connection that serves email and a few browsers will not serve forty phones, and guest WiFi for restaurants Kenya on a connection sized for the room works.
Do not share a marginal connection between the till and the guests, since a busy guest network slowing card payments is a real problem.
Hardware {#hardware}
The equipment should be built for the job.
A router capable of separate networks, guest isolation and captive portal, which a MikroTik provides.
Access points designed for density rather than a domestic router.
Outdoor-rated units for terraces.
Power over Ethernet to simplify placement.
Placement away from heat, grease and interference.
Enough units for the space, as the coverage section describes.
Battery backup.
The billing router is the control point, and guest WiFi for restaurants Kenya running through a MikroTik with proper access points is a system, while guest WiFi for restaurants Kenya running through the provider’s domestic router is a chalkboard with extra steps.
Buy once properly rather than replacing domestic routers annually.
Running It Without an IT Person {#without-it}
Most restaurants have nobody technical and the system must run without one.
Codes generated automatically, printed on receipts or in batches.
Sessions that expire on their own.
Bandwidth limits applied automatically.
Monitoring that alerts the owner when something is down.
A dashboard the owner can check on a phone.
Support from the provider when something needs attention.
No daily task, since a system that needs someone to do something every day will be neglected on a busy day.
The design goal is that it runs itself, and guest WiFi for restaurants Kenya that the manager never thinks about except to glance at the dashboard is the right outcome, while guest WiFi for restaurants Kenya that requires restarting, password changes and code invention is a job nobody was hired for.
Multi-Outlet Chains {#chains}
Several branches need consistency and central visibility.
The same portal and branding at every outlet.
Central configuration of session length, limits and terms.
Per-outlet monitoring and reporting.
Codes that work at any branch or only at the issuing one, as the chain prefers.
Aggregate footfall across the chain.
One system rather than a different router at each branch, since guest WiFi for restaurants Kenya managed centrally shows the owner every outlet’s network from one dashboard, and guest WiFi for restaurants Kenya configured once and applied across branches is consistent where branch-by-branch setup drifts.
Bars and Nightlife {#bars}
Bars have their own profile.
Many phones simultaneously.
Video and streaming demand, particularly for sport.
Long sessions since guests stay.
Guests sharing their night online, which is marketing.
Late hours and the need for the network to be reliable when the venue is fullest.
Screens on the business network, not the guest network.
Capacity sized for the packed Friday, and guest WiFi for restaurants Kenya in a bar should assume every guest is connected at once, since guest WiFi for restaurants Kenya that handles the match night handles every other night.
Hotel and Lodge Restaurants {#hotel-restaurants}
Restaurants within accommodation have a relationship with the property’s network.
Guests staying at the hotel may already have access.
Outside diners need their own route.
Integration with the hotel’s guest network where it exists.
Separate codes for restaurant-only guests.
The hotels article covers property-wide WiFi, and guest WiFi for restaurants Kenya within a hotel should sit inside that arrangement rather than beside it, since guest WiFi for restaurants Kenya as a separate network in a hotel that already has one confuses guests who are on both.
Data Protection {#data-protection}
Guest WiFi collects personal data and the Data Protection Act applies.
Device identifiers, connection times and anything the portal captures.
Contact details where marketing capture is offered.
Social profile data where social login is used.
Collect the minimum, since a code on the receipt collects nothing personal.
Inform guests through the portal terms what is collected and why.
Consent for marketing separate from connection.
No monitoring of individual browsing.
Retention defined and short, since connection records from months ago serve no purpose.
Access restricted.
Confirm obligations with qualified advice, and guest WiFi for restaurants Kenya should be configured to whatever position that establishes, since guest WiFi for restaurants Kenya that collected names, numbers and browsing without a basis has created an exposure to save the price of a printed code.
Costs and Setup {#costs}
The cost is modest against what it replaces.
A MikroTik router commonly from around KES 8,000 to KES 25,000.
Access points commonly from around KES 6,000 to KES 30,000 each, with one to three for most venues.
Battery backup commonly from around KES 3,000 to KES 10,000.
Installation and configuration.
The billing and portal platform subscription, commonly from around KES 1,500 monthly for a single venue.
The connection itself, which the venue likely already pays for and may need to upgrade.
Setup should begin with separation, since moving the till off the guest network is the urgent item.
Then the portal and codes, then coverage, then backup.
A single venue is typically running properly within a day, and guest WiFi for restaurants Kenya that cost a modest capital outlay and a small subscription has replaced a chalkboard that was costing the venue in capacity, security and reputation, while guest WiFi for restaurants Kenya left on the chalkboard will keep costing those things quietly.
Frequently Asked Questions {#faqs}
What is actually wrong with a password on the wall?
It never changes, so everyone who ever had it — neighbours, passers-by, last month’s customers — still consumes your capacity. There are no session limits, no fairness, no idea who is connected, and worst of all the guest network is usually the same network as the till, which puts the restaurant’s money one step from every phone in the room.
Should we charge for WiFi?
For most restaurants, no — free with purchase is the practical default. A code on the receipt serves customers, excludes non-customers and costs the guest nothing. Charging suits venues where guests stay for hours and consume heavily, such as cafés serving remote workers. Open, uncontrolled WiFi suits almost nobody.
Won’t WiFi make people sit for hours?
It can, and whether that is good depends on your format. A café wants dwell time; a lunch venue with a queue does not. Manage it with session length — sixty minutes at a lunch counter is generous to a diner and discouraging to a squatter, and a second code with a second order extends the visit for those who are spending.
What is the one thing we must do?
Separate guests from the till. The point-of-sale system, card terminals and the manager’s laptop should never share a network with guests. A separate isolated guest network with client isolation removes the exposure entirely, and if nothing else in this guide is done, this should be.
Can we collect guests’ phone numbers through the WiFi?
Only optionally, with a clear purpose, separate opt-in consent for marketing, and easy opt-out — and confirm the position with qualified advice since it engages the Data Protection Act. Forced capture produces false numbers and resentment. A code on the receipt collects nothing personal and gets guests online faster.
Can we see what guests are browsing?
You should not, and the lawfulness of doing so is questionable. Aggregate information — connections by hour, dwell time, repeat device rates — is useful and legitimate. Individual browsing is not the restaurant’s business. Configure the system to collect the aggregate and not the individual.
Our WiFi keeps dropping at lunch. Why?
Probably a domestic router beyond its capacity, possibly in a hot spot behind the coffee machine, on an eternal password shared with every device that ever connected. Sessions that expire, access points built for density, placement away from heat, battery backup and a connection sized for the peak resolve most of it.
How much does it cost to do properly?
A MikroTik router, one to three access points, battery backup and installation as a one-off, plus a modest monthly subscription for the portal and billing platform — typically a single venue is running properly within a day. Against that, guest WiFi for restaurants Kenya on a chalkboard is costing the venue in capacity, till security and reputation every week without anyone counting it.