Integrations
Connected to 230+ hospitality technology partners. And the connection writes back.
Property management systems, channel managers, payment providers and metasearch. Bookings, profiles, stays and upsells move in both directions, so the front desk never re-keys what the guest already did online.
230+
Integrations
PMS, channel managers, payment providers, metasearch and analytics combined.
150+
PMS connected
One per property, and they do not have to match across a group.
40+
Channel managers
Rates, availability and OTA bookings through the manager the hotel already runs.
Payment providers
Card, wallet and local methods taken on the engine and settled by the provider.
Metasearch
The direct rate carried to Google Hotel Ads and the other channels WhizzAds runs.
Works with your existing hotel technology
Works with every major PMS, Channel Manager, OTA, and Payment Provider
What flows each way
Read from the PMS. Written back to it.
Six things move between the hotel's systems and BookingWhizz. Here is the direction of each.
Data
From the PMS to BookingWhizz
From BookingWhizz to the PMS
Rates and availability
From the PMS to BookingWhizz
Room types, rate plans and inventory arrive from the PMS or channel manager, so the engine sells what the hotel has.
From BookingWhizz to the PMS
A booking taken on the engine reduces availability at the source, so nothing is sold twice.
Reservations
From the PMS to BookingWhizz
Every reservation, direct or OTA, phone or walk-in, is read into the guest record with its source kept.
From BookingWhizz to the PMS
A direct booking is created on the PMS reservation as it is confirmed, with the member rate and any offer attached.
Guest profiles
From the PMS to BookingWhizz
Names, contact details, stay history and spend are matched to one record per guest across every property.
From BookingWhizz to the PMS
Loyalty membership, tier and preferences are written to the PMS profile so the front desk sees them at check-in.
Stay crediting
From the PMS to BookingWhizz
Checked-out stays and folio totals are read so points are earned on what the guest actually spent.
From BookingWhizz to the PMS
The tier and points balance after each stay are written back where the PMS holds a loyalty field.
Folio and upsell posting
From the PMS to BookingWhizz
Outlet, spa and in-stay charges join the guest record and count towards points and tier.
From BookingWhizz to the PMS
An upgrade or add-on the guest buys is posted to the reservation and its charge to the folio, without re-keying.
Consent and contact details
From the PMS to BookingWhizz
Verified email and phone, and any marketing preference the PMS holds, are read into the record.
From BookingWhizz to the PMS
Opt-ins, opt-outs and corrected contact details captured on our channels are written back to the PMS profile.
Whether a row runs one way or both depends on the connection. Reading from the PMS is standard; writing back is confirmed per system. Each connection is scoped and quoted per PMS.
Write-back, loyalty crediting and supported workflows vary by system. Some connections carry third-party charges.
The central source
Every property, every PMS, every system and every website feed one guest record.
WhizzCRM is not one more system beside the PMS. It is where the group's guest data lands, is cleaned, and is read back by everything that talks to the guest.
What feeds it
Property management systems
One per property, and they do not have to match. Different systems at different hotels, all into the same record.
The Booking Engine and the hotel websites
Every direct booking, every enrolment, every Booking Booster sign-up, from one site or a group of sites.
Channel manager and OTA extracts
Bookings that arrived through an OTA still belong to the guest profile.
Restaurant, spa and outlet systems
POS and spa spend joins the profile, so the guest who dines but has not stayed is still known.
Replies and consent
Email and WhatsApp answers, opt-ins, opt-outs and verified contact details.
One record per guest
Identity
AI-powered matching across name, email, phone, booking references and stay patterns, with configured merge rules and source history kept.
Group-wide history
Stays, room revenue, F&B, spa and preferences across every property in the group.
Loyalty state
Membership, tier, points balance and reward activity.
Consent and channel
What the guest agreed to, on which channel, and when.
What runs on it
WhizzLoyalty
Recognition, tier and member value at every property.
Booking Engine and AI-powered PriceMatch
The member rate shown to the right person at the moment of choice.
Guest communication
Pre-stay, in-stay and post-stay messages personalised from the profile.
Upselling in WhizzCRM
Offers chosen from tier, property and past preferences.
Booking Booster and WhizzMailer
Segments and audiences built from the same profile.
Reporting
One view of the guest for the owner, not one per system.
Switching it on
How a connection is switched on
Step 1
Tell us the system
The PMS, the channel manager and the payment provider at each property. A group can run different systems at different hotels.
Step 2
We map what flows each way
Row by row from the matrix above: what is read from the PMS, what is written back, and what that connection supports. Scoped and quoted per PMS.
Step 3
It goes live
Live in 48 hours when the required access, data and integrations are ready. Programme design and configuration are agreed with the hotel.
Whizz AI · Write-back
What the guest buys on the website lands on the reservation, not in an inbox.
The connection runs both ways. The engine reads what the PMS holds, and what happens on our side is posted back to it where the PMS connection is configured.
Detected: A guest bought a suite upgrade on the website at BW Riverside Hotel.
Activated: The upgrade and the charge posted to the reservation in Riverside’s PMS. The front desk saw the upgraded room without re-keying.
Questions
What hotels ask about the connection
Do we need to change our PMS?
No. BookingWhizz connects to the PMS the hotel already runs, and a group can keep different systems at different hotels, all into the same guest record.
Is the connection real-time?
Rates, availability and reservations move as they change, so the engine sells what the hotel has and a direct booking reduces availability at the source. How each row runs depends on the connection, which we confirm when we scope it.
What if our system is not on the wall?
The wall shows the marks we hold, not the full list. Tell us what the hotel runs on and we will say what flows each way for that connection and what it takes to switch it on.
Is the connection two-way?
Where the PMS supports it. Reading from the PMS is standard. Writing back a booking, a profile, a stay credit or an upsell charge depends on the connection, and two-way to the PMS is scoped and quoted per PMS.
Who handles the mapping and testing?
BookingWhizz does. We map each row with the hotel, test the connection against live reservations before go-live, and confirm what the front desk will see.
Is support included?
Yes. The hotel has a named customer success contact, the support knowledge base, and support by email and WhatsApp. Live in 48 hours when the required access, data and integrations are ready. Programme design and configuration are agreed with the hotel.
Don't see your system?
Tell us what the hotel runs on. We will say what flows each way for that connection, and what it takes to switch it on