Yes. The wp_hb_booking_rooms table is part of context so the bot knows which rooms are blocked for which dates. For multi-night stays, every night in the requested range is validated before a room is suggested. If a single night in the middle is blocked, the bot won't offer that room — it'll suggest a different room or different dates.

Yes. The bot calculates total cost across nights including any seasonal adjustments per night, applies the room's base rate where seasons don't override, and adds optional extras with the right per-night versus per-stay rules. A two-night booking with a one-night seasonal adjustment in the middle gets the right total, not a flat base rate times two.

Yes. hb_extra_services posts are read with their prices, descriptions, and rules — per-night versus per-stay, mandatory versus optional, applies-to-all-guests versus per-room. The bot surfaces the right ones in context, so a guest asking about breakfast on a three-night stay sees the per-person-per-night total, not a single charge.

Yes. Promotional rates and codes stored in WP Hotel Booking are read and validated by the bot before quoting a discount. If the code has a date restriction, room-type restriction, or minimum stay requirement, the bot checks against those rules and only applies the discount when it would apply at checkout. No phantom discounts.

Yes. The hb_room_type taxonomy is part of context, so the bot can compare suite vs standard vs accessible rooms accurately, including capacity, amenities, and base rates per type. "What's the difference between the King Garden View and the Suite" gets a structured comparison from the actual room records, not a generic description.

Each room's max occupancy is read so the bot won't suggest a single room for a family of four. If a room has a base capacity plus an extra-bed option, that nuance is surfaced too — "the King Garden sleeps two but we can add a rollaway for $25/night for a third guest" — drawn straight from the room's capacity meta.

Yes. WP Hotel Booking stores cancellation policy text on the property and per-room-type level, and the bot quotes it verbatim. If a guest asks "can I cancel for a refund", the answer reflects whatever policy you've actually written, not a generic "please check our terms."

WP Hotel Booking syncs availability with channel managers like SiteMinder through dedicated extensions, and the rooms availability table reflects that synced state. Since SleekAI reads the live availability table, channel-blocked dates are excluded automatically. The bot won't sell a room that's already booked through Booking.com if the sync is working.