Introduction
The Cloudbeds integration is in limited release and certified for pre-check-in use cases. There are things it does not do yet, and knowing them upfront is more useful than discovering them mid rollout. This article lists the current limitations and the operational points worth planning around.
Availability
The integration is in limited release and may not be visible in all Cloudbeds accounts yet. Access is enabled per account, so contact your Customer Success Manager or support@bookboost.io to have it enabled.
Writing data back
Two-way sync is limited to pre-check-in. Guest details submitted through a pre-check-in form are written back to Cloudbeds. Manual edits made in the CRM do not sync back to Cloudbeds.
Guest consent is imported only. Consent is read from Cloudbeds but cannot be updated in Cloudbeds from Bookboost yet.
Identity document fields must meet Cloudbeds' format. If a document field is incomplete or does not meet Cloudbeds' requirements, the update may be rejected.
Custom fields are not available as tokens. Custom Cloudbeds fields, such as a personal access code, cannot currently be pulled into Bookboost as tokens.
Operational best practices
Disconnect from the Cloudbeds side. To remove the integration, disconnect it from Cloudbeds (myfrontdesk). Once disconnected, new data stops syncing; existing data in Bookboost remains unless you request its deletion.
Configuration and Setup
These points apply once the Cloudbeds integration is active. There is nothing to configure to encounter them. To connect a property, see Setting up the Cloudbeds integration; for what the integration does, see What the Cloudbeds 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.