Managing Multiple Locations: One Dashboard, Many Portals

Scaling From One Venue to Many

Each venue has its own branding, guests and calendar. VoqadoWiFi keeps one dashboard for all of them while giving each venue its own location, portal and numbers. The Starter plan covers one location, Growth covers three on one flat price, and Enterprise covers as many as you need.

Step 1: Create Separate Location Profiles

Go to Locations and click Add Location once per venue. Each location has its own portal URL slug, controller details, portal design and figures. Resist running two venues under one location: their guests mix together and the numbers stop meaning anything. If that has already happened, talk to us before adding the second site.

Step 2: Configure Location-Specific SSIDs

Each location records the SSID Name of its guest network and, optionally, the access point MAC. On the controller side, a single Omada or UniFi controller can run several sites; keep each venue in its own site with its own guest SSID pointing at that venue's portal. Keep staff on a separate SSID without the portal. Clear SSID names per venue ("CafeHighStreet Guest") make troubleshooting much easier.

Step 3: Clone Portal Config Between Locations

Each location has its own portal in Portal Builder; choose the venue at the top before you edit. There is no one-click copy between locations, so for a group with shared branding, set up one venue fully, then use the same logo, colours and wording for the next. The Quick-Start Templates on the Brand tab help you start each one in the same style. Afterwards, update anything venue-specific: the welcome text, the privacy policy link if it carries an address, and the redirect.

Step 4: Run Location-Filtered Campaigns

In Campaigns, New Campaign, use the venue picker so guests from one venue never get emails about another. For a group-wide promotion, send one campaign per venue rather than one to everyone: you get separate figures for each and can adjust the wording to each place. Email campaigns are a Growth plan feature and are not live yet; you can build and schedule them now.

Step 5: Compare Performance Across Sites in Analytics

On the Analytics page, filter by location or look at the Venue comparison and Top Locations views, which show weekly logins for each venue side by side once you have two or more. A venue with plenty of footfall but few logins probably has a portal problem: slow loading, a missing walled garden entry, or too many fields. A venue with good login numbers but few returning guests has a retention problem in the follow-up or in the visit itself.

Step 6: Set Up Per-Location Redirect URLs

Each portal has its own post-login link: in Portal Builder, Brand, Post-Login, set the Venue Website / Menu URL. Point it at something about that venue: its menu, its events page, or its own page on your website. Sending every venue to the group homepage wastes the moment when a guest is physically in that particular place.

Step 7: Franchise Model: Per-Franchisee Data Access

Per-venue team access is coming but not available yet: the Team option on Locations is marked as coming soon, and invites do not grant access today. Until then, the account owner holds the login for every venue. If franchisees need their own figures, export them per venue from CRM (the export can be filtered by location) and share only their own venue's file.

Step 8: Centralised Campaigns with Location Variables

The email editor supports two merge tags: `{first_name}` and `{venue_name}`. Use `{venue_name}` so one template reads correctly at each venue, then send a copy per venue with the right address and opening hours written in. There are no address or phone merge tags, so check those details by hand in each copy.

Step 9: Manage Seasonal Portal Variants

There are no saved seasonal variants, but History in the Portal Builder top bar keeps your earlier published versions. Before a seasonal change, note the date of your standard version, publish the seasonal look, and when the season ends restore the standard version from History rather than rebuilding it.

Step 10: Integrations Beyond the Dashboard

There is no public API today. For other systems, use the Mailchimp sync on Growth, CSV export on every plan, or the outbound webhooks on the dashboard Integrations page.

Step 11: Monthly Multi-Location Review Workflow

On the first Monday of each month, open Analytics and compare each venue's logins and returning guests with the month before. Flag any venue that has clearly dropped. For each flagged venue, work out whether the problem is finding guests (fewer new logins), keeping them (fewer returns) or the list itself (more unsubscribes). Give each venue manager ownership of their own figures; a named person per venue gets problems fixed faster than a group-wide report.