Google Calendar via OAuth, Microsoft 365 calendars, and the Amelia or Bookly WordPress plugins are the most common. If your team uses a custom post type for showings, SleekAI can read and write that directly, which is the cleanest setup because everything stays in WordPress. For Calendly the integration is read-only via their API, write happens through a deep-link the bot generates with the slot pre-selected.

Each listing post stores the assigned agent as a postmeta field or taxonomy. The bot reads that agent's calendar for availability and writes the booking against the agent's calendar, not a generic pool. For team-shared listings you can set a fallback order, primary agent first, then teammate two and three, so a slot is always offered even on the primary agent's busy day.

Both are configurable in the prompt or as global settings. Default tour duration is 30 minutes, default buffer is 15 minutes between showings to account for driving between properties. The bot enforces these silently when computing available slots. For high-value listings you can set a 60-minute slot, for back-to-back open-house weekends you can drop the buffer to zero in the prompt for that specific window.

Yes. Add a 'virtual' option to the conversation. The bot captures the preferred video platform (Zoom, Google Meet, FaceTime), the visitor's email and timezone, and generates the meeting link from your provider's API. Confirmation email includes the join link and a screen-share-ready checklist for the agent. Useful for out-of-town buyers, accessibility cases, and quick first looks before committing to a drive.

Yes within reason. A no-show flag can be applied to the booking record by the agent after the slot, which the bot reads on future bookings from the same email and can decline to confirm a third no-show without manual review. Cancellations through the confirmation email's link are logged with a timestamp, and a freed slot is immediately bookable by other inquiries. The bot does not chase no-shows for payment, that is outside scope for residential tours.

Yes. The bot's confirmation only requires one named contact, with a note that additional visitors are welcome. For ID-required showings (high-value or vacant single-family), each adult visitor is asked to bring ID on arrival, captured in the pre-tour checklist. Partners, family members, and inspectors can all attend on the same booking without separate registration.

It is stored in your WordPress database as part of the booking record and used to send the confirmation. It is not sent to any third-party chatbot vendor. The model API call goes to whichever provider your key belongs to, with that provider's retention. For maximum privacy, set the chat log to redact email and phone in the persisted transcript and store them only on the booking record. The bot still works fine for the live conversation.

Yes. Add a pre-tour intake step that asks for the budget range, financing status (pre-approved, in process, cash), and timeline. For high-value listings you can require a pre-approval letter upload before confirming a tour, which dramatically reduces tire-kicker showings. Lower the bar for entry-level listings where any qualified viewing is welcome. The intake fields are stored against the lead record alongside the booking.