No. As long as your reservations live as WordPress posts, postmeta rows, or a custom table, SleekAI can read availability and create new bookings. Many teams build a thin room_booking custom post type for this use case. If you already use a plugin with a database table, you map its fields into the prompt and the bot works against that source of truth.

Yes. Tell the bot 'every Tuesday at 9 for the rest of the term' and it creates one booking per week up to the end date, checking each instance for clashes. It surfaces any conflicts and offers alternates for those specific weeks, which is much faster than a calendar grid where you have to click through every recurrence.

The bot handles both in the same conversation. 'Move RR-9182 to 4pm' triggers an availability check on the new slot, updates the post in WordPress, and resends invites to attendees. Cancellations free the slot immediately and notify the original participants. Every change is logged on the booking record for audit.

Yes. Display conditions and prompt scoping let you enforce per-role policies. Members might book up to two hours per day. Staff might book unlimited. Guests might be capped at one slot per week and require approval. The bot states the rule when it applies, so users always know why a request was declined.

By the closest match on capacity, equipment, and proximity to the user. If you ask for four seats with a screen, the bot will rank a four-seat room with a screen above a twelve-seat room with the same kit, because oversized bookings waste capacity. Proximity uses the user's department or home floor from user_meta when available.

Yes. The same pattern works for courts, lanes, music rooms, lab equipment, even shared cars. Anything that has a schedule and a set of attributes can be modeled as a bookable post type. You just adjust the prompt and the metadata fields to match the resource the bot is booking.

Yes. Maximum duration, advance-notice windows, blackout periods, and cancellation deadlines can all be coded as rules. The bot checks each before confirming a booking and explains the rule in plain language if it has to decline. This avoids the friction of a system that just shows an error code without context.

Everything stays in your WordPress database. Bookings are posts in the reservations custom post type. Conversations are logged with model, token usage, and origin page in the SleekAI tables. You can export, audit, or delete them according to your retention policy without contacting a vendor support team.