The Clock PMS integration covers guest communication and segmentation from live Clock data, but there are things it does not do. Knowing them upfront is more useful than discovering them mid rollout. This article lists the current limitations and the operational points worth planning around.

The Clock integration is one-way: data flows from Clock into Bookboost. Bookboost does not write data back to Clock. Guest details captured or edited in Bookboost, and form submissions, are not sent to Clock, so Clock stays the master record and any changes to a booking are made in Clock.

Companies are not synced as separate profiles from Clock. Bookboost syncs the primary guest and the contact person on a reservation, and the contact person is sometimes a company. Company or booker details held only at company level in Clock may not appear as a separate profile in Bookboost.

Clock does not store space availability data, so adjusted occupancy is not available in Bookboost Insights for Clock properties.

Clock applies request limits, so large historical imports are brought in smaller blocks, around three months at a time. When you import a specific date range, the reservation's arrival date decides whether it is included.

These points apply once the Clock integration is active. There is nothing to configure to encounter them. To connect a property, see Setting up the Clock PMS integration; for what the integration does, see What the Clock PMS integration does.

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.