ItReserve Guest Comms

SMS and email automation at key touchpoints in the guest journey

€17 /mo

About this module

Sends branded messages at booking confirmation, 48h pre-arrival, check-in, mid-stay and post-departure. All triggers link to reservation status changes in your Reservit account — no manual scheduling. Works on top of Reservit without replacing native communication features.

What you need

✓
Reservit account (any tier)
Any active Reservit subscription with the PMS or channel manager active and API access enabled.
✓
Reservit API key access
Found in Settings → Integrations in your Reservit dashboard. If not visible, contact Reservit to enable API access on your tier.
✓
Active ItReserve subscription
A monthly ItReserve subscription for this module. Add to cart and complete checkout to receive access within 24 hours.

Where to find your Reservit API key →

How ItReserve Guest Comms connects to Reservit

A module-specific breakdown of the API connection process, data flow and write-back behaviour.

Guest Comms subscribes to reservation status change events from your Reservit account using the Reservit webhooks API. When a reservation is created, moved to confirmed, updated to within 48 hours of arrival, set to checked-in, or set to checked-out, Reservit sends an event to Guest Comms's endpoint. Each event triggers the corresponding message template for that point in the guest journey.

On receiving a trigger event, Guest Comms reads the full reservation record from Reservit — including guest name, arrival and departure dates, room type, rate plan and any special requests recorded in the notes field. These data points are merged into your configured message template using standard merge tags. The completed message is sent via email or SMS to the contact details in the Reservit guest profile.

Guest Comms does not write data back to Reservit — it is a read-only integration beyond the initial webhook subscription. All message delivery records are stored in the ItReserve dashboard, where you can view the delivery status, open rate and timestamp for every automated message sent. The dashboard also shows which Reservit reservation triggered each message, allowing you to trace any guest query back to its source reservation in a single click.

Module features

Five core capabilities included with your ItReserve Guest Comms subscription.

⚡

Event-driven message triggers

Messages fire automatically when Reservit reservation status changes — booking confirmation, 48-hour pre-arrival, check-in, mid-stay and post-departure. No manual scheduling.

✉️

Visual template editor

Drag-and-drop email and SMS template editor with Reservit merge tags for guest name, arrival date, room type and property details. No HTML knowledge required.

📱

SMS and email delivery

Send messages via email and SMS to EU destinations. Channel is configurable per trigger type — use email for confirmations, SMS for same-day check-in reminders.

📊

Delivery and open tracking

Per-message delivery confirmation and email open tracking visible in the ItReserve dashboard. Identify which message types resonate best with your guests.

🔀

Booking source conditional content

Show different message content to OTA guests versus direct bookers based on the booking source field in Reservit — personalising communication per channel segment.

Frequently asked questions

Guest Comms and Reservit's native messaging features can coexist, but to avoid sending duplicate messages to guests, we recommend disabling any Reservit-native automated messages that overlap with the Guest Comms triggers you activate. The onboarding guide walks through this deactivation step.

Yes. Guest Comms supports conditional content blocks within message templates. You can show different text depending on the booking source field in the Reservit reservation — for example, including OTA-specific cancellation wording for OTA guests and direct booking upsell content for direct guests.

If the Reservit reservation contains no valid guest email address, the Guest Comms trigger fires but the message cannot be delivered. The failed delivery is recorded in the module's activity log with the reservation ID, allowing your team to follow up manually.