Introduction
The SiteMinder integration keeps reservations flowing into Bookboost, but it is a lighter, inbound-only integration and there are important things to know before you rely on it. This article lists the current limitations.
One-way integration
The integration is inbound only. SiteMinder pushes reservation data into Bookboost, and Bookboost does not send anything back to SiteMinder or your PMS. Changes made in Bookboost are not reflected in the source system.
Campaign tokens are not available
Campaign tokens are not registered for SiteMinder properties today, so you cannot personalise messages with reservation or guest tokens (for example a guest's name or arrival date) for a SiteMinder-connected property. You can still send campaigns and segment audiences using the synced data.
OTA reservations without guest details
Reservations from some OTA channels, such as Expedia, can arrive without guest contact details. When that happens, Bookboost cannot attach a guest profile to the reservation or message that guest, so those reservations may not trigger guest communication.
No historical pull or backfill
Data only flows when SiteMinder pushes it. There is the optional flush of past reservations at activation, and new reservations going forward, but there is no automatic backfill if a reservation update is missed.
Data that is not synced
Cancellation, deposit, and no-show policies are not synced.
Company, billing, order, and note data is not synced.
Only limited channel detail is captured (booking channel type and company name), not the full channel manager detail available for some other integrations.
Configuration and Setup
These points apply once the SiteMinder integration is active. To connect, see Setting up the SiteMinder integration; for what it does, see What the SiteMinder integration does.
Support
Please contact us through the 'Talk to Us' option on the left menu in the platform, or through the Bookboost Support email at support@bookboost.io if you have questions or need additional support.