Which SMS providers do you support?

Twilio, MessageBird, Plivo, and any provider that exposes a REST send-SMS API. Many regional gateways are configured out of the box.

What if a guest doesn't receive the code?

Built-in retry, resend, and fallback to voucher or email login. Failure rates per carrier are visible in Daily Incident Reports.

Do you store phone numbers?

Yes — encrypted at rest, never shared with third parties, retained per the venue's data retention policy (configurable).

All features

Authentication

OTP Authentication

Replace junk emails and recycled passwords with verified phone-based access. Lower bot traffic, higher-quality leads, and a defensible audit trail for every WiFi session.

Business outcomes

Eliminate fake email guest signups
Build a phone-verified marketing list automatically
Reduce abuse and quota fraud
Meet KYC-style hospitality requirements where required

Capabilities

What's inside.

SMS OTP codes

Six-digit verification delivered via Twilio or your own SMS gateway.

Voucher fallback

Pre-printed codes for kiosks or events when SMS isn't available.

Anti-fraud rules

Rate-limiting, MSISDN deny-lists, and country-of-origin filters.

Carrier-aware retries

Smart retry logic that handles transient carrier failures.

How it works

3 steps from connect to deliver.

Guest enters phone

Captive portal collects MSISDN, optionally with consent checkboxes.

Code sent

OTP delivered via your SMS provider in 2-5 seconds.

Verify + access

Guest enters code, RADIUS grants session, profile is stamped verified.

Pairs with

Features that work together with OTP Authentication.

See all 18 features