Every contact, every channel.
One omnichannel record.
Direct bookings, OTAs, tour operators, voice, chat, WhatsApp, captive portal and folio extras. Every contact lands in the same record, and every conversation picks up where the last one left off. One profile per guest, written by every channel and ready for the next message.
Hotel groups don't have a contact problem,
they have a guest problem.
One person reaches you on four channels, in three languages, across two properties, on the same Tuesday. A B2B CRM sees four leads. A hotel CRM sees Aoife.
Lead, opportunity, deal, account. Hotel groups don't operate that way. A guest is a person who slept in a room on a date, sometimes with their partner, sometimes with a dog, sometimes for the third time this year. They're identifiable by a booking, not a job title.
They reach you on WhatsApp at 11 pm. They DM Instagram about the rooftop bar. They call reception about a late check-in. They email about breakfast. Across nine properties, three PMS instances, and six channels, they are still one person.
GuestMaker's CRM is built around what guests actually do, anchored to bookings, enriched by every conversation, surfaced to every agent. Not a contact database. The long-term memory of your hotel group.
One ingestion API for
every system in your stack.
Push contacts, bookings, extras, and events from your PMSs, booking engines, channel managers, OTAs, and anywhere else guest data lives. Real-time webhooks for status changes, scheduled crons that recover late minibar and spa charges after checkout, bulk endpoints for historical migrations.
- POST /api/v1/reservations, upsert by reservation_id, guests + stays + extras in one call
- Webhook events for booking.created, booking.updated, guest.checked_in/out, payment.received
- Cron extras recovery, re-pulls minibar, spa, and restaurant charges that posted post-checkout
- Bulk ingestion, up to 5,000 reservations per call for historical migrations
Common questions.
Don't see yours? Bring it to the demo and we'll answer it live.
No. The CRM sits on top of your PMS (Mews, Apaleo, Cloudbeds, Opera, Protel, etc.) and complements your existing marketing tools. We integrate, we don't replace. Most groups keep their PMS and use GuestMaker as the unified guest layer above it.
Yes, natively through the WhatsApp Business API. Messages land in the same guest record as email, voice, web chat, and Instagram, with no separate inbox or contact list to keep in sync.
Our CDP layer ingests reservations and contacts from every PMS instance in your group, then resolves them using a combination of deterministic (email, phone, loyalty ID) and probabilistic (name + arrival date + property) matching. Merge decisions are transparent and reversible, with full audit logs.
Never. Memories live in your tenant only. They're used by your AI agents to personalize conversations and journeys, and surfaced to your staff in the Contact Profile. They are never used to train shared models or shared across customers.
Yes. We import historical reservations, contacts, and engagement data during onboarding. Most groups complete the historical migration in 2-3 weeks, with the deduplication and enrichment running in the background.
GDPR-compliant by design, hosted in EU, with per-channel consent capture, suppression lists, and a full right-to-be-forgotten flow that propagates across all integrated systems. SOC 2 Type II in progress, ISO 27001 underway.
Most single properties are live in 2-4 weeks. Multi-property groups typically take 6-10 weeks for full rollout, with the first property live in week 4.
See the Agentic CRM
with your own data.
Thirty-minute demo. We'll wire up one property of yours and walk through a real Contact Profile, a real segment, and a real reservation, end to end.