Configuring your splash screen

The splash screen is what guests see when they join your WiFi: your branding, a short sign-in form, and optionally a consent step, a verification code, and a "you're online" page. This guide walks through every tab of the editor.

How the editor works

In your dashboard, open your venue and go to Splash Screen. The editor has seven tabs on the left and a live preview on the right — phone or desktop:

Two things to know before you start:

• The splash screen is configured per venue, not per access point. Every access point at a venue shows the same splash screen.
• Changes are live the moment you save — guests joining right after see the new version.

Design

Template, colors, and logo — the look every page inherits.

• Template — a purely visual choice. Every template renders the same fields, so you can switch any time without losing content.
• Primary color — buttons and accents. Must be a 6-digit hex value like #8B5E3C — shorthand (#abc) and alpha values are rejected, and an invalid color is silently ignored.
• Background color — the page background, same 6-digit hex rule. Check the contrast against your primary color.
• Show logo — toggles your logo on every page. With it off, only your title and sub-heading show.

Login page

The first page guests see, and the only place their contact details are captured — whatever you turn off here is data you'll never have for marketing.

• Title — the headline, up to 100 characters, e.g. Welcome to Café Heidi.
• Sub heading — up to 250 characters; leave it empty to hide the line.
• Guest details — four built-in fields: first name, last name, email, phone. Each can be shown or hidden, and independently marked required. Email is what marketing campaigns need most.
• Continue button text — up to 40 characters, defaults to Continue.
• Custom fields — up to 8 extra questions (text or checkbox), e.g. a room number or booking reference.

Consent page

Where guests opt in to marketing. Guests who decline still get online — this is consent, not access.

• Ask for marketing consent — turning this off skips the page entirely. No consent is captured, so your campaigns will have no opted-in audience.
• Heading (up to 100 characters) and subheading (up to 250).
• Body paragraphs — 1 to 4 paragraphs, up to 1,000 characters each.
• Accept / decline button labels — up to 40 and 60 characters.

Verification

An optional wall: guests confirm their email or phone with a one-time code before getting online. It raises data quality and blocks junk sign-ups, at the cost of friction — most venues leave it off.

• Channels — email, SMS, and/or WhatsApp. At least one must be on, or verification switches itself off. SMS and WhatsApp both verify the phone number, so enabling both still asks for one number.
• Default channel — must be one of the enabled channels.
• Requirement — any (one confirmed contact is enough) or all (every enabled channel must be verified). Any is almost always right.
• Remember guests for — 0 to 90 days before a verified guest is asked again. 0 means re-verify on every visit.

Connected page

What guests see once they're online — a second chance to point them somewhere useful: your menu, booking page, or a review link.

• Title (up to 100 characters) and subtitle (up to 250; empty hides it).
• Button — label up to 40 characters, and an https URL.
• Auto-redirect — send guests to a URL automatically after 0–30 seconds instead of showing a button. Https only; if the URL is invalid the redirect silently never fires.
• Custom fields — up to 8 optional questions, same rules as the login page. A good spot for a quick rating, since the guest already has internet and nothing is blocking them.

Terms & Privacy

The legal documents linked from the splash footer.

• Every venue starts with the platform default privacy policy and terms — you don't have to write anything.
• Customize lets you publish your own text instead, per language. Publishing appends a version, so a mistake is recoverable.
• The footer link toggles control whether each link appears on the splash pages at all.

Languages

Whether guests can read the splash screen in their own language.

• Supported languages: English, German, Italian, and French — the portal ships translated buttons, error messages, and verification copy for exactly this set.
• The language switcher only renders with at least two languages available.
• Translations are a words-only overlay: which fields exist, colors, and templates are venue settings shared by every language.
• Any field you haven't translated falls back to your default language instead of rendering blank — half-finished translations are safe.
• The language a guest picks is stored with them and reused for verification codes and marketing sends.

Faster with the MCP

Every option above can be configured conversationally: connect the HeidiFi MCP server, ask your assistant to "set up my splash screen", and review the preview link it sends before anything goes live.