How to choose a guest WiFi marketing platform

VoqadoWiFi publishes this guide and sells a platform you might score with it, so we are not a neutral party. The framework is built to survive that: the criteria are the ones we lose on as well as the ones we win on, and there is a section further down naming exactly when we are the wrong choice. Use the scorecard on us with the same weights you use on everyone else.

Name the controller, not the brand

The answer is not TP-Link. It is the controller software, the model, and the firmware version currently running on it. Vendors integrate with controller APIs, and those APIs change between versions.

Ask what happens on a firmware update

Captive portal integrations break when the network vendor ships a change. Ask which versions the platform is tested against and how quickly a break gets fixed. Vendors who do not test will hear about it from you.

Test on your own access points

A demo tenant on hardware the vendor controls proves nothing about yours. Insist on a trial where a real guest connects through your real network before any money moves.

Treat bundled hardware as a separate decision

Buying access points from the software vendor removes the compatibility question entirely, which is a genuine benefit for a venue with no controller. It also means switching later means replacing the network. Both facts are true at once.

Whether the price is published, and whether it is charged per location or per account. The model matters more than the headline number, because the model decides what you pay at venue four and venue twenty.

Whether the guest list is yours in practice, not only in the contract. A guest database you cannot take with you is a rented asset that quietly becomes a switching cost.

Whether the platform records how and when each guest consented, keeps that record auditable, and gives you a working path for access and deletion requests.

How the platform asks for reviews, and whether that method holds up against the published rules of the review platforms themselves. This is the criterion most likely to create a problem you did not know you bought.

Whether the platform sends campaigns itself, pushes contacts into the email service provider you already pay for, or does both and bills you twice for the same capability.

Whether one guest database spans your sites or fragments into one list per venue, and whether staff permissions match how your group is actually run.

What the platform connects to out of the box, what needs an API, and whether API access is on the plan you can afford.

Who answers when the portal stops loading on a Friday evening, how quickly, and whether that answer is included or sold separately.

How long the product has been sold, whether it is actively developed, and what happens to your data if the company is acquired or shuts the product down.

Why it matters. The answer separates a platform you are using from a platform that is holding your list. Ask for the format and the fields, not a yes.

Why it matters. Per location pricing is honest but linear. Per account pricing is cheaper at small multiples and usually has a ceiling. You need both curves before you can compare quotes.

Why it matters. The cost of changing your mind is set here. A twelve month term with sixty day notice and an undisclosed escalator is a different product from the same software billed monthly.

Why it matters. Captive portal integrations break on firmware changes. A vendor who cannot name the versions they test against will find out about the breakage from you.

Why it matters. Some vendors advertise sentiment filtering as a feature. Review platforms publish their own rules about discouraging or intercepting negative reviews, so read those rules and decide deliberately rather than inheriting a choice the vendor made for you.

Why it matters. If this takes more than one email, compliance is not a solved problem inside that company, and it will not be solved faster once you are a customer.

Why it matters. You will be asked eventually. A vendor with a real workflow can describe it in two sentences. A vendor without one will describe a policy instead.

Why it matters. This single answer tells you whether you are buying a group guest database or a set of parallel lists that happen to share a login.

Why it matters. Paying twice for sending is the most common avoidable line item in this category. Decide whether you are buying capture, sending, or both.

Why it matters. API access is frequently a top tier feature. If the integration you are counting on needs the API, the real price of the platform is the tier that has it.

Why it matters. Guest WiFi fails in public, in front of customers. The recovery path matters more than the feature list on the day it happens.

Why it matters. You are choosing a custodian for a database you intend to grow for years. Continuity is a feature even though no vendor lists it as one.

Quote only pricing is normal at the enterprise end, where scope genuinely varies. It is harder to justify for a product sold to independent venues. When nothing is published, the price is set by what the vendor thinks you will pay, and you cannot compare two quotes that were both built that way. Ask for the list price and the discount separately.

Some vendors advertise routing predicted unhappy guests to a private feedback form while predicted happy guests get the public review link. Review platforms publish policies about discouraging or intercepting negative reviews, and those policies are the thing you should read before adopting the practice. Beyond the policy question, a rating built by filtering tells you nothing you can manage the business with.

If the only way to get your own contacts out is a support ticket, a fee, or a notice period, the list is functionally an asset the vendor controls. Test the export before you commit, not when you are leaving and have the least leverage.

Bundled access points can be a genuine shortcut for a venue with no controller and no IT support. The flag is when the hardware only works with the cloud of that one vendor, because the day you want to switch you are replacing the network as well as the software.

Any promised percentage increase in reviews, repeat visits, or revenue that arrives before the vendor knows your traffic, capture rate, and average visit is a sales artefact rather than a forecast. Ask what it is based on. The answer is usually a single unnamed customer.

If you cannot get a trial account against your own hardware, you are evaluating a video. Compatibility, capture rate, and portal behaviour on your actual access points are the only tests that predict what you will live with.

This is the binary constraint and we fail it more often than any other. VoqadoWiFi integrates with TP-Link Omada and Ubiquiti UniFi controllers. If your estate is Meraki, Aruba, Ruckus, Cambium, MikroTik, or a mixed inheritance of all of them, no amount of feature fit rescues the evaluation. Stop here and shortlist platforms with broad vendor support instead.

If your process requires a page of named logos, a dozen published case studies, and hundreds of reviews on the software directories, we do not clear that bar and we are not going to pretend otherwise. Larger and older vendors in this category do. If social proof volume is genuinely part of your risk assessment, weight it and let it decide.

Hotels running a serious direct booking programme usually want guest records flowing between the portal and the property management system, with folio and stay data attached. That is a specialised integration surface and it is not ours. Platforms built specifically for hospitality stays will serve that requirement better than we will.

If the outcome you are being measured on is proving that a message caused a physical return visit, or mapping dwell time and zone movement across a large venue, that is a different product category. We report on campaigns and reviews, not on presence analytics.

Removing our branding from the portal is an Enterprise feature. If a fully unbranded portal is a requirement and an entry level budget is a constraint, those two facts do not meet on our pricing page, and an agency oriented platform will fit better.

Hardware compatibility, before anything else. It is a binary constraint rather than a scored criterion: either the platform supports your access points and controller or it does not, and if it does not, every other strength is irrelevant. Confirm the exact controller model and firmware version in writing, then score the remaining criteria only among the vendors that passed.

The weights in this guide are a starting point, not a standard. Pricing transparency and data ownership carry the most weight here because they set your long term cost and your ability to change your mind. If you run twenty venues, raise multi location management. If you already pay for a mature email platform, lower messaging depth and treat the WiFi platform as capture and sync. The scorecard lets you change every weight, which is the point.

Neither is better in the abstract, and the honest answer depends on your venue count. Per location pricing is transparent and scales linearly, which is predictable but expensive at scale. Per account tiers are usually cheaper at small multiples and then hit a ceiling that pushes you to a quote. Model both against the number of sites you expect in three years, not the number you have today.

Review filtering, sometimes called sentiment gating, means routing guests toward a public review or a private form depending on how they are predicted or reported to feel. Review platforms publish their own policies about discouraging or intercepting negative reviews, and those policies are what you should read before adopting the practice. There is also a practical argument: a rating produced by filtering does not tell you anything you can act on, because the feedback that would have changed the business was diverted away from the public record.

Sometimes not, and sometimes yes. If your sends are simple, a WiFi platform with native campaigns can replace a separate tool. If you run complex flows, deliverability monitoring, or ecommerce triggers, a dedicated email service provider will keep winning and the WiFi platform should be judged on how cleanly it syncs contacts into it. What you want to avoid is paying two vendors for the same sending capability and using neither well.

Export your guest list and open the file. It takes ten minutes and it tests four things at once: whether export is self serve, whether consent metadata survives, whether visit history is included, and how the vendor behaves when you show you intend to keep your options open. A vendor that makes this awkward during a trial will not become more generous after you sign.

VoqadoWiFi wrote it, and we sell one of the platforms a reader might score with it. The framework is written to be usable against us, which is why it includes a section naming the buyers we are wrong for: anyone not running TP-Link Omada or Ubiquiti UniFi, anyone who needs a long public reference list, anyone who needs deep property management system integration, anyone buying footfall attribution, and anyone who needs white labelling on an entry level budget. Score us on the same criteria as everyone else and let the total decide.