It hands off to the plugin you already run. Amelia, BookingPress, FluentBooking, WP Simple Booking Calendar, and Easy Appointments all expose webhook or REST endpoints, and most teams confirm via webhook so the official record stays in the plugin's tables. The bot's job is to qualify, offer the right slot, and confirm; the underlying plugin handles availability, reminders, and the calendar write itself.

The grounding context refreshes per conversation, and the actual reservation happens through the booking plugin's normal API, which holds the source of truth for availability. The bot offers slots based on the snapshot it received, then the plugin's confirm step rejects a stale slot and the bot asks for an alternative. In practice this almost never fires because conversations are short, but the safety net is there.

Yes. Staff bios, the services each one performs, and their working hours flow in from postmeta or ACF. The system prompt can be told to recommend the right person by skill and to honour blocks for days off, with display conditions per service page so a colour bar visitor and a cut-only visitor see different scope without configuration overhead.

Most WordPress booking plugins already bridge to Google Calendar, Outlook, and Apple via the standard ICS or OAuth flows. SleekAI hands off to the plugin, which keeps the cross-calendar sync intact. There's no need for a bespoke Google connector inside SleekAI because the plugin you already chose to handle bookings keeps doing that job.

Yes, with the right webhook. The bot can capture the confirmation code or email used at booking, then the underlying plugin's cancellation endpoint takes the action. For reschedules the bot offers two or three alternative slots and confirms with a fresh webhook call. Most teams cap cancellation windows in the system prompt so the bot doesn't promise a refund the plugin's policy wouldn't honour.

That depends on the plugin. If the booking plugin requires a deposit for that service, the confirm webhook returns a payment link the bot can pass into the chat. If the plugin allows free booking with payment in person, the bot just confirms and the receipt follows by email. The behaviour matches whatever the booking plugin is already configured to do, so payment policy stays in one place.

Calendly's flows are pinned to its own data model and pricing. SleekAI lives in your WordPress install, grounds against the booking plugin you already paid for, and uses your own model provider key. If your booking plugin already covers reminders, cancellations, and calendar sync, layering a hosted scheduling SaaS on top is a duplicate cost. SleekAI's role is the conversational layer, not a competing scheduling backend.

Booking conversations are typically short, 3 to 6 turns at 400 to 800 tokens per turn, which lands well under a cent per booking on a mid-tier OpenAI or Anthropic model. Compared to the no-show rate a static widget produces and the time saved on email-back-and-forth bookings, the model cost is the small line item. Logs record token usage per conversation so you can budget against actual numbers.