TripBidUse calendar connections for the right accommodation
Open the property's calendar and connection settings from your host dashboard. Use the supported iCal import or export tools for the property or room type where available. Match the external calendar to the correct accommodation rather than assuming all calendars represent the same inventory.
Calendar feeds primarily communicate date or occupancy information, not the full pricing, meals and cancellation policy of an offer. An imported block is not the same as a TripBid guest booking. Changes also depend on the connection's update process; do not assume an external edit appears everywhere instantly.
Illustrative single-unit calendar
A villa receives an external reservation from 10 to 14 November. That means occupied nights on 10, 11, 12 and 13 November, with checkout on 14 November. The corresponding availability should not allow another guest to occupy those same nights. Check the dates and update status in the relevant calendar rather than relying only on the presence of a feed URL.
Review room and property mappings
For a hotel or multi-unit operation, review which external room type or unit maps to each TripBid room type. A property-wide closure and a block on one room type have different effects. Keep enough detail to distinguish a sold-out category from an entire property being unavailable.
Illustrative room-type mapping
A property has double rooms and family rooms. An external calendar for one family unit should not be attached to every double room as though it describes the hotel's entire stock. Equally, a full-property closure needs to apply to the accommodation it actually affects, not just one unrelated unit.
Check the supported connection's scope and configuration shown in your account. Do not infer that one provider supports the same data flows as another.
Distinguish property-system connections from payment setup
TripBid has settings for supported PMS or channel connections where offered. Follow the setup and mapping instructions for the specific provider displayed there, and review the status and sync information after connecting. A provider's name in a settings list is not a promise that every account, room configuration or external feature is supported.
Payment setup is separate. Connecting inventory does not connect a bank account or prove accommodation payments are ready. Check the payment route independently and review your property's booking policies before accepting offers.
Keep connection credentials and calendar access links private. This public guide does not need your tokens, guest details or screenshots of sensitive settings. Share only what is appropriate through the relevant private setup process.
AI travel assistants are a different kind of connection
TripBid's current ChatGPT connector can list destinations and prepare a link to the website. It does not submit guest requests, retrieve live offers or take payments inside the chat. Guests complete requests and bookings on TripBid.
That connector is distinct from the host's AI Reservation Manager, which can send eligible offers within host rules. Public search visibility is distinct again: publishing readable guides does not install a booking integration into every assistant conversation. See integration information for the public overview and use the host settings for actual property connections.