A reservation, a reply, a returning guest, a Tuesday at 9am. GuestMaker listens to your PMS, your inbox, your chatbot and your calendar, then sets the right journey in motion.
Hotel-native triggers from your PMS, the moment they happen.
Every reply, every chat, across every channel becomes a trigger.
What happens at the front desk and around the building.
Time itself becomes a trigger.
When a contact's profile changes, the journey reacts.
For everything else, staff actions and your own external systems.
90 hospitality-grade templates out of the box, an AI studio that generates editable HTML in under two minutes, one-click multilingual translation, and a campaign wizard that audits every send before you press the button.
The Guestmaker Gallery ships with hospitality-grade templates across pre-stay, in-stay, post-stay, loyalty, and promotions. Translate any template into 26 languages in one click, every variant stays in sync with the original.
30+ curated prompts cover every hospitality scenario, Black Friday, post-stay thank-you, room upgrade, anniversary. Pick one or describe your own. The AI Studio writes copy, picks imagery, builds responsive HTML, and hands it off to the visual editor in under 120 seconds.
Switching CRMs is the moment most teams lose years of templates. We give every account a unique import inbox, forward your templates from your old provider and they land here, parsed, indexed, and ready to edit in the visual editor. No copy-paste, no rebuild.
Seven guided steps walk teams from naming a campaign to a final 12-point audit, with realistic hotel segments, booking-protection rules, and deliverability checks built in.
We audit every template against Meta’s policy before submission, auto-throttle broadcasts to stay inside the rate limits, and pause sends during each guest’s quiet hours, so your messages reach inboxes, not complaint queues.
One sentence in: an audited, variable-mapped, Meta-ready template out. No more rewriting bodies to dodge category rejections.
Every header, body, and button is scored against Meta’s policy in real time. Fix what flags red, then auto-submit when the score hits 100.
Pick a template, map the variables, target the segment. We’ll throttle to Meta’s rate limits, defer per-guest DND windows, and tag every send with UTM, before you hit confirm.
Volume, deliverability, attribution and reply intent across every email and WhatsApp campaign, with AI agents flagging anomalies, attributing revenue and synthesising A/B tests in the background.
A journey is a multi-step automation tied to a guest event, booking confirmed, 7 days before arrival, post-stay day 2. A broadcast is a one-shot send to a static or dynamic segment, typical for win-backs, promotions, or last-minute offers. Same templates, same throttling, same consent gates, different intent.
Email, WhatsApp and SMS in one tree, with channel fallbacks (try WhatsApp first, fall back to email if the guest has not opted in to WhatsApp). Voice can fire from a journey node too, useful for high-value win-backs. Every channel respects its own consent record at send time, not at audience build time.
Any node can hand off to the AI agent for the next reply. The agent inherits the guest's full memory, the journey's brand voice, and the property's policies. When the guest replies, the agent answers in their language, books the upgrade, modifies the reservation, or escalates to staff with a translated summary, then returns control to the journey on the next scheduled step.
Twelve audit checks before the send button enables: subject line length, spam triggers, sender domain DKIM, audience size and consent, booking-protection (do not message guests with an active reservation), language-template match, image hosting, link tracking. The wizard refuses to send if any critical check fails. You see the audit live, not after the fact.
Both. Each property can have its own templates, sender domains, and journeys with property-specific branding and tone. Group-level campaigns roll up across all properties with role-based access for HQ. The same audience, the same consent record, no duplicate sends across property boundaries.
Quiet hours apply per guest in their local timezone, deferring sends until the window lifts. Marketing opt-outs gate at dispatch, not at audience build, so a guest who opts out an hour before send is excluded automatically. WhatsApp throttles to Meta's documented per-tier rate limits, with adaptive backoff if the API returns a 429.
Yes. The import flow accepts MJML, raw HTML, and direct platform pulls from Mailchimp, Klaviyo, Brevo, HubSpot, Customer.io, and ActiveCampaign. Variables are mapped on the fly to GuestMaker contact fields, with a one-click translation pass to extend the template into 26 languages while keeping every variant in sync.
Twenty-six languages out of the box. Translation is one click per template; the system runs a hospitality-tuned model, preserves all merge tags and links, and stores each language as a sibling variant. Edit the source language, the rest re-translate automatically. Guests receive the variant matching their stored language preference.
UTM tags are added per send, deeplinks are signed and tracked back to the original message, and bookings completed within an attribution window (default 7 days for marketing, 30 days for win-backs) get tied to the originating campaign or journey step. Revenue and conversion rates appear per-template, per-property, per-language in the Analytics dashboard.
The journey pauses on that contact while the AI agent or your team handles the reply. If the agent answers and resolves, the journey resumes from where it paused. If the conversation requires human follow-up, the journey waits until the contact is marked resolved in the inbox, then continues. No double-messaging, no journey stepping on a live conversation.
We'll wire up your PMS, drop in your tone of voice, and walk through a real win-back journey on your data, in your language. Thirty minutes is enough to see it ship.