Skip to main content

Rollout readiness

Content we need—and what to prepare

Use this page to align sales, IT, and operations before a workshop. Nothing here replaces a formal statement of work; it helps both sides shorten discovery and avoid missing inputs.

Information we need from you

The more specific you can be in your first message, the faster we can suggest phasing, modules, and integration touchpoints.

Scope & scale

  • Number of properties or sites and regions
  • Peak concurrent guest or visitor sessions (order of magnitude)
  • Indoor vs outdoor coverage expectations where Wi‑Fi is in scope

Access & identity

  • Preferred login paths: voucher, room-based, SMS or email OTP, social, MAC for TVs/IoT
  • Whether staff, contractor, or patient networks must be segmented from guest traffic
  • Any mandatory identity or audit retention policies

Hospitality & billing context

  • PMS vendor and interface type if room-based or folio workflows matter
  • Paid vs complimentary access models and who operates frontdesk recovery
  • Whether you need surveys, campaigns, or sponsored login in phase one or later

Network & operations

  • WAN design: single ISP vs multi-WAN, failover expectations
  • How DHCP and DNS are provided today and where the HSIA gateway will sit
  • Who owns change windows, monitoring, and escalation (your NOC vs partner)

What your team should prepare

These assets reduce back-and-forth during design reviews and pilot planning.

Network documentation

High-level L3 diagram: guest VLANs or SSIDs, uplinks, core switch placement, and where captive traffic will hit the gateway. IP addressing plan for guest pools helps avoid rework.

Integrations

Contacts for PMS, SMS aggregator or email relay, payment provider if you sell access, and any existing RADIUS or directory constraints.

Compliance & security

Data residency expectations, log retention, lawful intercept or regulatory notes your counsel cares about, and acceptable use or terms text for the portal.

Success criteria

Target metrics: connection success, helpdesk volume, revenue per room, or NPS—so rollout phases can be measured rather than debated.

Typical technical prerequisites

Exact checks depend on your topology; this is the checklist most enterprise HSIA rollouts converge on.

  • Stable guest VLAN or SSID path from access layer to the HSIA gateway placement you approve.
  • DNS and DHCP strategy agreed for guest clients (gateway-assisted or upstream).
  • TLS-capable captive portal endpoints where browsers will redirect unauthenticated users.
  • Time sync (NTP) and administrative access for configuration and log export during cutover.
  • A named project owner on your side plus a technical counterpart for test windows.

Final interface counts, throughput targets, and HA models are confirmed during architecture review—not assumed from this marketing summary.

Ready with your inputs?

Use the contact form with name, work email, and a message that covers site count, concurrent users, and must-have integrations.

Go to contact form