SiteMinder ecosystem + boutique adjacencies
What the Hotelminder shortlist actually connects to.
Every module on the Hotelminder shortlist uses the official SiteMinder API as its primary integration surface. Alongside SiteMinder itself, the shortlist reaches into eight or nine adjacent services when a boutique property benefits from that reach. This page lists them and offers advisory notes on which combinations make sense for a 10 to 80-room property.
The SiteMinder ecosystem — primary integration surface
Hotelminder integrates with the SiteMinder product family via the official SiteMinder API using an API token that your property generates from inside SiteMinder Central. We never store your SiteMinder password. Every read and write is scoped to the modules you have activated and is visible in the SiteMinder audit log.
The SiteMinder modules the shortlist reads from or writes to include the Channel Manager, GuestJoy for guest messaging, Insights for reporting, Reviews for review response, Multi-Property for portfolios, and the PMS module for room-status writes. Not every Hotelminder module uses every SiteMinder module — the requirements are declared per shortlist entry on the product page.
Adjacent services — the boutique-relevant set
Beyond SiteMinder, the shortlist touches a small set of adjacent services when a boutique property benefits. The full list is in the table below with the specific purpose and requirement notes. Advisory notes follow.
Integration table
| Integration | Category | Purpose | Requires |
|---|---|---|---|
| SiteMinder Channel Manager | SiteMinder core | Rates, availability, restrictions, bookings — the source of truth for distribution | SiteMinder subscription (any tier with Channel Manager) |
| SiteMinder GuestJoy | SiteMinder core | Guest profiles, pre-arrival and stay messaging, consent tracking | SiteMinder + GuestJoy add-on |
| SiteMinder Insights | SiteMinder core | Booking-level reporting, exports for the Distribution Intelligence Layer | SiteMinder + Insights add-on |
| SiteMinder Reviews | SiteMinder core | Review aggregation from Booking, Google and TripAdvisor; response publishing | SiteMinder + Reviews add-on |
| SiteMinder Multi-Property | SiteMinder core | Cross-property configuration for boutique groups of two to twelve | SiteMinder Multi-Property with 2+ properties |
| SiteMinder PMS module | SiteMinder core | Room status, housekeeping writes, folio references for guest links | SiteMinder + PMS module |
| Stripe | Payments | Card capture at booking, tokenised so the card number never touches Hotelminder | Stripe account, EU data region |
| Google Hotels | Distribution / metasearch | Free Booking Links + paid Hotel Ads via SiteMinder Metasearch surface | Google Hotel Center account |
| WhatsApp Business Cloud | Guest messaging | Pre-arrival, in-stay and post-stay concierge conversations, on Meta's official channel | Meta Business account, WhatsApp Business Cloud enabled |
| Postmark | Transactional email | Warmer email track for concierge messaging and pilot-pack notifications | Postmark EU region (managed by Hotelminder) |
| Datadog EU | Observability | Runtime metrics, uptime, SiteMinder API rate-limit dashboards for the advisor team | EU-region Datadog tenant (Hotelminder-owned) |
| Sentry EU | Error tracking | Non-guest-data error captures on module code, for the integrations team | EU-region Sentry tenant (Hotelminder-owned) |
| Meta Business Suite | Guest messaging control plane | Consent surface and template moderation for WhatsApp Business Cloud | Meta Business account linked to the WhatsApp Business number |
Advisory notes on which combinations fit boutique hotels
The default boutique stack we recommend
For a 20 to 40-room boutique in a European city, the default stack we recommend on the scoping call looks like this: SiteMinder Channel Manager as the source of truth, GuestJoy for guest messaging with the Concierge Expander sitting on top of it, Rate Reasoner for pricing, the Direct Deal Widget for the website. Payments through Stripe if you are not already on a payment provider that integrates directly with SiteMinder. This covers roughly 80 percent of boutique first-quarter needs.
Where WhatsApp Business Cloud makes sense
WhatsApp is the dominant messaging channel in Southern Europe (Italy, Spain, Portugal), meaningful in Central Europe (Germany, Austria, Netherlands), and less critical in Northern Europe where email retains more mindshare. The Concierge Expander integrates WhatsApp Business Cloud on Meta's official channel — not a scraped or unofficial gateway. Consent tracking through Meta Business Suite is part of the setup during onboarding.
Where SiteMinder Multi-Property changes the recommendation
Once a boutique group runs three or more properties on SiteMinder Multi-Property, the recommendation flips from "install modules per property" to "install Portfolio Sync Fabric first and cascade the module strategy through it". A group with five properties and five different concierge template libraries is a group with five different guest experiences — sometimes desirable, sometimes not. The Fabric lets you decide per module whether to keep property-level variation or align.
Where Datadog and Sentry sit
Datadog EU and Sentry EU are Hotelminder-owned tenants, used to observe the health of the module code and the SiteMinder API integration. Neither receives guest data. Both are EU-tenant only — no data leaves the European Economic Area at any point in the stack.