Hotels Cafés & bars How it works Features Guest CRM Integrations Pricing Guides Support
Integrations

Plugs into what you already have.

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.

Your Wi-Fi

It works with the equipment you already have

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. The table below shows the makes we've already set up. Not sure what you have? Send us a photo and we'll tell you.

MakeStatusFor your IT person or Wi-Fi supplier
MikroTik / RouterOSSupportedLogin page swapped for ours; access checked against our RADIUS service.
ArubaSupportedSame shape as MikroTik: redirect in, the controller checks with RADIUS.
Ubiquiti UniFiSupportedWe authorise the guest directly with the UniFi controller, with no separate RADIUS step.
Cisco MerakiSupportedClick-through or sign-on against Meraki's own cloud, which then checks with RADIUS.
Ruckus SmartZoneSupportedWe call the controller's management interface directly.
OpenWrt (openNDS)SupportedThe router checks in with us on its own, so nothing has to reach it for a guest to get online.

Running something not on this list? 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 →

Your front-desk system

Any front-desk system that can tell us who's staying, or none at all

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.

In: who's staying

Your front-desk system keeps us current

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, because none of them will call an address a hotel chooses, every five minutes by default, and as often as every minute if you want it.

  • Room number, surname and departure date are all it takes
  • Shared rooms, room moves and extended stays are all handled without a thought
  • A rate or loyalty tier can decide the guest's speed: suites get suite speeds
  • Checkout switches the Wi-Fi off behind the guest, automatically
Out: who you met

Guest details flow back where they belong

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.

  • Sent to you as it happens, or picked up whenever you're ready for it
  • If a guest withdraws consent or asks to be forgotten, that travels too, so your records stay accurate
  • Room sign-ins carry the booking reference, so nothing gets duplicated or mismatched
  • Or skip this entirely and download your guest list as a spreadsheet, free on every plan

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.

Front-desk systems we already connect to

Resort Manager comes connected out of the box. For other systems, we do the same two-way sync on your behalf, and where a ready-made connection doesn't exist yet, we hand your vendor or IT team the documentation to build one.

Front-desk systemStatusNotes
Resort Manager / Resort Manager FlexBuilt inThe only one that tells us as it happens rather than waiting to be asked. Guest details flow back matched to the booking.
Oracle OPERA CloudSupportedThrough Oracle's Hospitality Integration Platform. The older on-premise Opera, over FIAS or IFC, is not connected. Ask us before quoting a property running it.
MewsSupportedThrough the Mews Connector API, on a token the property generates itself.
CloudbedsSupportedOn an API key, reading the checked-in list, paged, so a busy changeover is read to the end.
protelSupportedThrough 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 elseSupportedFull documentation, no waiting for us to build a connector. Any system that can reach the internet can connect today.

Your system not listed? The order we build named connections in isn't fixed: it follows demand. Tell us what you run →

A page each

What connecting your front-desk system actually involves

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 →

Resort Manager

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.

Oracle OPERA Cloud

Through OHIP. The most demanding of these to set up, and the one where two easily confused credentials are both required on every call.

Mews

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.

Cloudbeds

One key, and the checked-in list read to the end rather than a first page, because otherwise the rooms above 200 quietly fail.

protel

Through protel I/O, at the address of your own endpoint. protel Air and an on-premise protel are not in the same place.

Anything else

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 →

Resort Manager properties

If you already run Resort Manager, it's connected already

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.

What's included →

Resort Manager Resort Manager Flex Any system Oracle Opera Mews Cloudbeds Protel
Mailing lists & CRM

Captured tonight, ready to use tomorrow

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.

DestinationStatusHow it connects
Resort Manager / Resort Manager FlexIncludedAutomatic, tied to the booking. Part of the base product on every plan.
Spreadsheet (CSV) exportFreeDownload your guest list from the console, filtered how you like. Free on every plan, always.
HubSpotAdd-onNamed connection: guest record kept up to date, marketing permission included.
MailchimpAdd-onNamed connection: your mailing list stays in sync, marketing-consented guests only.
OmnisendAdd-onNamed connection: same as Mailchimp.
KlaviyoAdd-onNamed connection: guest record and list kept in sync.
Scheduled file deliveryAdd-onA file sent on a schedule, for systems that can only take a file rather than a live connection, the fallback for older systems.
Anything elseAdd-onA 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.

Messaging

SMS verification, if you want it

Optional, and off by default. Turn on one-time passcodes only if collecting a verified phone number is worth paying per message for.
Sent through Twilio. One provider, deliberately. At the handful of codes a venue actually sends, a second provider just buys you a second bill to watch and us a second thing to debug when codes stop arriving.
Two ways to pay. Buy prepaid message blocks from us — 500 for $45, and the balance never expires — or connect your own Twilio account and pay your own rate, which we don't add a fee on top of. Your own account also lets you register a proper local sender name instead of a random number.
Protected against abuse. Since you're paying per message, there's a daily limit per phone and per guest. Nobody can run up your bill by hitting "send" over and over.
Before you ask us

What people ask about connecting things

Which front-desk systems connect?

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.

How current is the guest list?

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.

Which mailing tools and CRMs connect?

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.

Does it work with our Wi-Fi equipment?

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.

What does connecting a front-desk system cost?

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.

Is SMS verification extra?

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.

Tell us what's on site

What Wi-Fi you run, what front-desk system if any, how many properties. We'll tell you straight whether it works today or needs waiting for.