WiFi Marketing for Franchise Operators: Central Brand, Local Intelligence

The Franchise Marketing Tension

A single venue owner decides everything about their guest WiFi. A franchise network has two parties with different needs. The franchisor wants every portal to look the same, every email template on brand and one consent wording everywhere. The franchisee wants their own guest list, their own campaigns and their own numbers.

Get it wrong one way and franchisees ignore a central system that does not help them locally. Get it wrong the other way and every site does its own thing, the brand looks inconsistent and nobody can say what consent was collected where.

Decide the list model before you deploy the first portal. Changing it later means moving guests between lists, and that is where consent records get lost.

Architecture Option 1: Separate Lists per Location

Each location runs its own account, its own email audience and its own campaigns. Head office supplies a master portal design (logo, colours, fonts, consent wording) and each site copies it.

Advantages:

• Franchisees see and own their local guest data
• Campaigns can be properly local: a quiet Monday in one town is not a busy Saturday in another
• One weak site does not muddy brand level numbers

Disadvantages:

• A national campaign has to be set up and sent once per location
• A guest who visits two sites appears as two separate contacts
• Design drift: sites edit their copy of the portal and stop matching

Best for: networks where franchisees are independent and good at their own marketing.

Architecture Option 2: Merged Brand List with Location Tags

All guests from every site go into one brand level audience, tagged with the locations they have visited. Head office runs brand campaigns; each franchisee filters to their own tag for local sends.

This is how VoqadoWiFi's Mailchimp sync works out of the box. An account syncs to one Mailchimp audience and tags each guest "wifi-guest" plus "location:" followed by the venue name, so a guest who logs in at two sites carries both tags. Mailchimp sync is on Growth and above. Only guests who tick the separate, unticked marketing box on a venue's login page are synced, and they arrive as subscribed contacts.

Advantages:

• You can see guests who use more than one site
• Brand level reporting is in one place
• One consent standard, one privacy notice, one place to handle requests

Disadvantages:

• Franchisees have less control over their local list
• Someone has to decide, in the franchise agreement, what happens to a site's guests if that franchisee leaves

Best for: networks with a strong central marketing team and site managers who focus on operations.

Architecture Option 3: Federated Model

Each site keeps a local list for local campaigns, and every site also feeds a brand master list. A guest who visits several sites sits in each relevant local list and once in the brand list. Head office can send to everyone; sites can send locally.

It is the most flexible model and the most work. Every opt out has to reach every list the guest is on, quickly, or you will email people who said stop. Only choose it if someone owns that job.

Compliance at Franchise Scale

This is general information, not legal advice.

Standardise these across every site, whichever model you choose:

• Portal consent wording (one approved version, used everywhere)
• Privacy notice (one document, linked from every portal; see our privacy notice template)
• Data retention (one policy, applied the same way)
• Access and erasure requests (one inbox, with a named person at each site to carry them out)

Who is legally responsible depends on who decides why and how guest data is used. Under UK GDPR, organisations that decide the purposes and means together can be joint controllers. Joint controllers do not need a contract with each other, but they do need a transparent arrangement setting out who does what, and individuals can still exercise their rights against each of them (ICO, joint controllers). Where a supplier processes guest data on your behalf, there must be a written contract between you (ICO, controller and processor contracts).

In practice, the franchise agreement should say who decides the consent wording, who holds the list, and who answers a guest who asks what you hold on them. Get your own legal advice for your network and countries.

Illustrative example: 12 location fast casual chain

This is a made up scenario to show the set up decisions, not a customer result.

A 12 site fast casual chain wants brand campaigns from head office and some local freedom. It picks the merged model: one audience, location tags, one consent wording.

What it has to sort out:

• Plan. Growth covers up to 3 locations, so 12 sites means Enterprise, which is priced on request (pricing). Paid plans are activated by a person and invoiced monthly; there is no card checkout.
• Roll out order. Pilot two sites for a few weeks, fix the portal wording, then copy it to the rest. Check each controller's walled garden settings during the pilot (Omada setup, UniFi setup).
• Local sends. Site managers send only from approved templates to their own location tag, and head office keeps a shared calendar so a guest does not get a brand email and a local email on the same day.
• Measurement. Track returning guests per site in the dashboard, and opt in rate per site. A site with a much lower opt in rate usually has a portal problem or staff telling guests to skip it.

Next step: write down which of the three models you are using and who owns opt outs, before the first portal goes live.