Booking.com

Overview

The Booking.com card in /integrations does not provide a standalone Booking.com connection or collect Booking.com credentials. Booking.com is one of the largest online travel agencies (OTAs). Booking.com does not expose a self-serve public API for individual accommodation partners; its Content, Reservations, Messaging and Reviews APIs are reached by certified Connectivity Partners, which is what every modern short-term-rental and hotel PMS already is. Access in MessageMind is proxied through whichever PMS you have connected (Hostaway, Hospitable, Lodgify, Guesty, Zeevou, Booking Experts or WebHotelier). The PMS stitches Booking.com reservations, guest messages and reviews into its unified inbox and property catalog, and the AI reads and writes against that unified surface using the PMS credential.

What MessageMind can do with it

• Read Booking.com reservations attached to a thread, including stay dates, check-in and check-out times, guest identity, number of guests and the Booking.com reservation reference, as surfaced by the connected PMS.
• Answer a guest message that arrived on Booking.com inside the PMS's unified inbox, where Booking.com, Airbnb, Vrbo, Expedia, email, SMS and WhatsApp are one thread per guest per reservation.
• Send a reply back on the Booking.com thread, routed by the PMS to Booking.com's Messaging API with the correct transport chosen for that thread.
• React to Booking.com reviews on the PMS's periodic review walk, so a review-triggered follow-up fires once the review lands in the PMS (Booking.com's review timing can lag the stay by days).
• Quote Booking.com listing content (room/unit descriptions, amenities, house rules, check-in and check-out windows) that the PMS has synced into its property catalog.

Requirements

• A Booking.com Extranet account that is connected to one of the supported PMS platforms (Hostaway, Hospitable, Lodgify, Guesty, Zeevou, Booking Experts or WebHotelier) as its channel manager.
• That PMS connected to MessageMind through its own shipped integration, with Booking.com listed as an enabled channel on the PMS side.

How to connect

1. In Booking.com Extranet, confirm the integration with your PMS is live under Account and then Connectivity provider. If Booking.com is not already pointed at your PMS, enable the connection on the Extranet first; this is the step Booking.com requires on their side.
2. In your PMS, confirm Booking.com listings are mapped to the PMS properties and that two-way messaging is on.
3. In MessageMind, open Integrations and connect the PMS itself (Hostaway, Hospitable, Lodgify, Guesty, Zeevou, Booking Experts or WebHotelier). Follow that PMS's documented connect flow; there is no separate Booking.com connect form.
4. Once the PMS is connected, Booking.com reservations and messages appear on the usual inbox as a thread with channel set to booking_com.
5. Optional: open the PMS integration's settings and confirm Booking.com is in the list of channels the AI is allowed to send on, if the PMS supports a per-channel allow-list.

Authentication and permissions

Available data and actions

AI agent use cases

• Reply to a Booking.com guest asking for an early check-in without opening the Extranet, because the thread is already a normal unified-inbox thread via the PMS.
• Confirm a returning Booking.com guest's reservation dates and check-in time from the PMS's reservation record, matched to the Booking.com reservation reference.
• Trigger a post-stay follow-up on a Booking.com review once the PMS imports it on its review walk.
• Answer property-specific questions (parking, Wi-Fi, nearest station) using the PMS's listing content for the Booking.com-mapped unit.

Configuration

• The channel label on a Booking.com-sourced thread is set to booking_com by every supported PMS; the AI picks reply transport from the PMS, not from a MessageMind setting.
• Message-send budgets are the connected PMS's own (for example Hostaway's 30 sends per minute per account, Hospitable's 2 sends per minute per thread).
• Booking.com's own review-release window can delay a review by several days after check-out; the PMS review walk uses a multi-day overlap so late reviews are still picked up.
• If the PMS supports a per-channel allow-list for AI replies, Booking.com can be turned on or off there without disconnecting the whole PMS.

Example workflows

Limitations

• No direct Booking.com connector in MessageMind. Booking.com's Connectivity APIs are gated to certified partners, and the supported path for every PMS-managed property is through that PMS.
• The depth of what the AI can do on a Booking.com thread (which fields are readable, which transports are allowed, whether host sends emit a webhook) is bounded by what the connected PMS exposes.
• Booking.com's review-release lag is set by Booking.com and cannot be shortened by the PMS or by MessageMind.
• If the PMS loses its Booking.com mapping (for example a listing is unlinked in the Extranet), the thread will still arrive but will not resolve to a property in the AI's catalog until the PMS re-maps it.
• The AI will not change rates, create or cancel Booking.com reservations; the PMS's channel-manager flow handles that, not MessageMind.
• The current Booking.com modal has no credential fields and includes placeholder Calendly copy. Opening that card does not add a direct Booking.com connection; use the supported connected PMS channel for eligible guest conversations.

Troubleshooting

Disconnect and reconnect

• Disconnecting Booking.com from MessageMind means disconnecting the PMS integration that proxies it. Open the PMS integration page in MessageMind and choose Disconnect; the AI stops reading or replying on Booking.com threads at the same moment it stops using the PMS.
• To stop Booking.com alone while keeping Airbnb, Vrbo and the other channels, remove Booking.com from the PMS's enabled channels on the PMS side.

Related integrations

Hostaway Hospitable Guesty Lodgify