How was a guest verified?

The splash page asked for a phone number and sent a one-time code; internet access was granted after the code was entered. Social login was available as an alternative.

Where do the numbers come from?

From the platform's own export: 125,367 sessions, 41 hotspot network names, 30,798 distinct devices and 29,218 unique email-or-phone profiles between 23 June 2017 and 28 March 2018.

Can this run in a mall or at an event today?

Yes. The same architecture works with current cloud-managed access points and any SMS gateway; the festival deployment is the closest reference for event-scale bursts.

Industrial, IoT & Operational SystemsHappy Hive social WiFi · June 2017 – March 2018 (nine months of live deployments)

Social WiFi Platform: Free Guest Internet That Captured a Verified Audience Across 41 Hotspots Happy Hive social WiFi

Happy Hive was Technovier's own social WiFi product, deployed for cafés, coffee and burger chains, salons, a shopping mall and a national food festival between mid-2017 and early 2018. The venues are not named.

Duration: June 2017 – March 2018 (nine months of live deployments)

Platform: Cloud WiFi, captive portal, SMS

Channels: Social WiFi audience capture

Build Something Similar What we built

Counted from the export

What the platform captured

Hotspot networks live41

Portal sessions in the export125k

Unique verified profiles29k

June 2017 – March 20189 mo

Capture

Monitor

Alert

Act

Report

Overview

Each venue ran one or more cloud-managed access points broadcasting a branded free-WiFi network. Joining it opened a splash page: a short sign-up form or social login, a one-time code sent to the guest's phone, then free internet. Every verified sign-in landed in an audience database the venue could message by SMS and survey with branch-level feedback forms. Across the deployment period the platform export holds 125,367 portal sessions on 41 hotspot networks, 30,798 distinct devices and 29,218 unique email-or-phone profiles.

Cloud-managed access points and captive portal, custom sign-up form with OTP, social login, SMS gateway, per-venue audience database

Problem, Constraints, Baseline, Approach, Results

Problem

Venues had thousands of walk-in guests and no way to recognise, count or contact them again.

Constraints

Sign-up had to take seconds on a phone, work on unreliable venue links, verify a real number, and never block guests who simply wanted internet.

Baseline

Free WiFi with a shared password: no verification, no profile, no way to follow up.

Approach

Cloud-managed hotspots with a captive portal, a custom sign-up form with OTP phone verification and social login, an audience database per venue, and SMS and feedback campaigns run from it.

Results

Counted from the platform export: 125,367 sessions, 41 hotspot networks, 30,798 devices and 29,218 unique profiles, 59,149 of the sessions from a single festival deployment. Revenue impact for the venues was not measured, so none is claimed.

9 mo

June 2017 – March 2018

Hotspot networks live

125k

Portal sessions in the export

29k

Unique verified profiles

9 mo

June 2017 – March 2018

Hotspot networks live

125k

Portal sessions in the export

29k

Unique verified profiles

9 mo

June 2017 – March 2018

Key metrics shown: 41 Hotspot networks live; 125k Portal sessions in the export; 29k Unique verified profiles; 9 mo June 2017 – March 2018.

Challenges

1. Verification without friction: A one-time code proved the phone number was real, but the whole flow still had to finish in the time it takes to sit down.

2. Many small sites, one system: Forty-one networks across cafés, salons, a mall and a festival had to report into one audience database with venue-level views.

3. Festival-scale bursts: A single food festival produced 59,149 sessions in days; the portal and code delivery had to hold under that load.

What we built

Branded captive portal: Splash page per venue with a short form, social login and OTP verification, then automatic internet access.
Cloud-managed hotspots: Access points configured and monitored centrally, so a new venue was a configuration change, not a site visit.
Audience database and campaigns: Verified profiles with gender, age and city, SMS campaigns to segments, and branch-level feedback forms.

Why it matters for connected venues

The pattern is capture → verify → store → act → report: a physical touchpoint (the hotspot) feeding a verified record that a business can act on. It is the same discipline behind our industrial monitoring work, applied to guests instead of sensors.

• Verified at the edge: The OTP step turned anonymous connections into contactable people, which is what made the database worth keeping.

• Per-venue views, one platform: Every venue saw its own audience and campaigns while the operator ran one system.

Conclusion

A social WiFi product that ran for nine months across 41 hotspots and captured a verified audience of 29,000 profiles. The venues and festival organiser are not named; the counts come from the platform export.

Related systems