Your Wi-Fi. Your front-desk system, your PMS. Your mailing list or CRM. We connect to all three without replacing any of them: PMS Wi-Fi integration without a PMS project, no new equipment to buy, no shopping list of "approved" gear designed to sell you something new. If your Wi-Fi is reasonably recent and your front-desk system can send a guest list, you're already compatible.
Branded sign-in pages are something Wi-Fi equipment has supported for years. We use that, not a box of our own. If your gear was sold for use in a hotel, café or shop, the odds are strongly in your favour. Forty makes are set up, each with a page of its own; the table below shows six of the most common. See all forty → Not sure what you have? Send us a photo and we'll tell you.
| Make | Status | For your IT person or Wi-Fi supplier |
|---|---|---|
| MikroTik / RouterOS | Supported | Login page swapped for ours; access checked against our RADIUS service. |
| Aruba | Supported | The controller shows our login page and checks each guest against our RADIUS service. |
| Ubiquiti UniFi | Supported | We authorise the guest directly with the UniFi controller, with no separate RADIUS step. |
| Cisco Meraki | Supported | Click-through or sign-on against Meraki's own cloud, which then checks with RADIUS. |
| Ruckus SmartZone | Supported | We call the controller's management interface directly. |
| OpenWrt (openNDS) | Supported | The router checks in with us on its own, so nothing has to reach it for a guest to get online. |
Running something that is not among the forty? Almost all Wi-Fi equipment speaks the same sign-in pattern, so adding a new make is usually straightforward rather than a rebuild. Tell us what you have →
Room-and-surname sign-in only needs to know one thing: who's in which room, and until when. Any front-desk system that can send that gets the full experience. Resort Manager just happened to be first. Running a café or a bar? Skip this section entirely; the other ways in don't need a front-desk system at all.
Check a guest in and they can be online within minutes. Resort Manager tells us as each guest arrives, and can re-send the whole in-house list at any time, which is how it recovers cleanly if the link between the two systems drops for a while. Every other front-desk system is asked instead: every five minutes by default, and as often as every minute if you want it.
Every guest we meet becomes a proper record in your own systems, matched to their booking, not guessed at by name. Your guest records get richer every busy night.
For your IT team or PMS vendor: the connection is by API key, issued per property, limited to what that connection actually needs, and logged on every use.
Resort Manager comes connected out of the box. For other systems, we do the same two-way sync on your behalf, and for a system without a ready-made connection, your vendor or IT team gets the documentation to build one.
| Front-desk system | Status | Notes |
|---|---|---|
| Resort Manager / Resort Manager Flex | Built in | The only one that tells us as it happens rather than waiting to be asked. Guest details flow back matched to the booking. |
| Oracle OPERA Cloud | Supported | Through Oracle's Hospitality Integration Platform. The older on-premise Opera, over FIAS or IFC, is not connected. If that is what you run, talk to us first. |
| Mews | Supported | Through the Mews Connector API, on a token the property generates itself. |
| Cloudbeds | Supported | On an API key, reading the checked-in list, paged, so a busy changeover is read to the end. |
| protel | Supported | Through protel I/O. We ask for the address of your endpoint rather than assuming it: protel Air and an on-premise protel are not at the same one. |
| Anything else | Supported | Full documentation, no waiting for us to build a connector. Any system that can reach the internet can connect today. |
Your system not listed? It connects through the documented route, the same as any other. Tell us what you run →
One page per system: what the connection reads, how quickly it hears about a check-in, what a guest sees, and what has to be true before an installer starts. Worth reading before the site visit rather than during it. All five in one place →
Connected out of the box, and the only system here that tells us about a guest as it happens instead of waiting to be asked.
Through OHIP. The connection that asks the most of you to set up: Oracle issues two separate sets of credentials, and both are needed.
Through the Connector API, on a token the property generates itself. A reservation with no surname on it is a guest who cannot sign in.
One key, and the whole checked-in list is read, however many rooms the property has.
Through protel I/O, at the address of your own endpoint. protel Air and an on-premise protel are not in the same place.
A URL, how to authenticate, and which field means what. No release of ours to wait for, and most independent properties run something regional that will never justify a connector of its own. Tell us what you run →
Who's staying flows out and the guest details flow back into your guest records, tied to the booking. There's no extra charge for the Resort Manager connection: it's part of the base product on every plan.
The same applies to Resort Manager Flex, which works the same way.
A guest list is only worth what you do with it. Every destination below gets the same complete guest record — name, contact details, whether they said yes to marketing — so connecting your own system is a switch to flip, not a project to plan. And because their permission travels with the record, the list stays one you're legally allowed to use.
| Destination | Status | How it connects |
|---|---|---|
| Resort Manager / Resort Manager Flex | Included | Automatic, tied to the booking. Part of the base product on every plan. |
| Spreadsheet (CSV) export | Free | Download your guest list from the console, filtered how you like. Free on every plan, always. |
| HubSpot | Add-on | Named connection: guest record kept up to date, marketing permission included. |
| Mailchimp | Add-on | Named connection: your mailing list stays in sync, marketing-consented guests only. |
| Omnisend | Add-on | Named connection: same as Mailchimp. |
| Klaviyo | Add-on | Named connection: guest record and list kept in sync. |
| Scheduled file delivery | Add-on | A file sent on a schedule, for systems that can only take a file rather than a live connection, the fallback for older systems. |
| Anything else | Add-on | A documented connection with your own key, so anything that can receive data over the internet can be hooked up. |
Permission travels with the record. Whatever the destination, a guest's withdrawal of consent, or request to be forgotten, here is passed on there too, as an instruction to stop using their details. That's what keeps your marketing list safe to use after it leaves us. Third-party connections are a paid add-on; the Resort Manager connection and the spreadsheet export are not.
Resort Manager and Resort Manager Flex out of the box, and Oracle OPERA Cloud, Mews, Cloudbeds and Protel. Any other system that can say who is in which room and until when can be connected through a documented API rather than a private arrangement.
Resort Manager tells us about an arrival, a room move or a departure as it happens. Every other system is asked on a schedule the property sets, five minutes by default, so a change reaches the sign-in page within a few minutes rather than instantly.
HubSpot, Mailchimp, Omnisend and Klaviyo as named connectors, a CSV or SFTP drop, generic webhooks and Zapier. Each connector is $15 per site per month, or $150 a year. The spreadsheet export is free, always.
Almost certainly. Forty makes are set up, from Aruba, Ruckus and Cisco Meraki to Ubiquiti UniFi, TP-Link Omada and MikroTik, each with its own page saying what it can do and what has to be true first. One setting changes on the equipment running the guest network.
Properties running Resort Manager pay the loyalty rate of $75 a month, with the connection included. Properties on any other system pay $250 a month, with one front-desk connection included. The difference is a thank-you to the Resort Manager family, not a technical charge.
Yes, as a block of 500 messages for $45 that never expires, or free through your own SMS gateway account. There is a daily limit per phone and per guest, so nobody can run up the bill.
What Wi-Fi you run, what front-desk system if any, how many properties. We'll tell you straight whether it works with what you have.
