Yes. Pro and add-ons share the same database tables, and the bot reads any extra fields they introduce automatically. Multi-location, deposit, custom fields, group bookings and staff categories are all picked up through the same retrieval layer. There is no separate adapter to install per add-on, since SleekAI reads any post type and any meta. New add-ons work the same way as existing ones.

By default it pre-fills checkout so payment and confirmation use Bookly's existing flow. This keeps payment processor, fraud rules, deposit collection and confirmation emails on the production path that's already been tuned. A direct-create flow is optional for businesses that want chat-only bookings, but most teams prefer the checkout handoff because it preserves their existing logic.

Existing appointments are read from wp_bookly_appointments at retrieval time, and the bot will not suggest a slot that's already booked. Staff breaks, days off and any blocked time are honored too, since they're part of Bookly's own availability calculation. A slot that gets booked by another customer between the bot's suggestion and the visitor's click is caught by Bookly's checkout, which re-checks availability before confirming.

Yes. Deposit amounts and rules per service are read into context and quoted accurately. The bot can say 'a $20 deposit is required to hold this slot, balance due at the appointment' from the actual Bookly setting. Conditional deposits, where a deposit only applies for certain services or first-time customers, are honored as long as those rules are stored in Bookly's config rather than computed at runtime.

Yes. Staff, services and locations are linked, so the bot answers correctly per branch. A barbershop with Greenwich and Williamsburg locations can run two scoped bots through display conditions, each surfacing only its own staff and chairs. The visitor asking 'who's available at the Williamsburg shop tomorrow?' gets the right staff list rather than a mix from both locations.

Yes. SleekAI matches the visitor's language even when the data is stored in your default site language. Service names get returned in the visitor's locale where translations exist via WPML, Polylang or TranslatePress; prices, durations and time slots are universal. International chains end up with one bot rather than one per locale, which simplifies maintenance and ensures consistent behaviour.

Yes. A logged-in customer asking 'can I move my Saturday appointment?' is matched against their existing appointment record. The bot suggests new slots that respect the same staff member's schedule and the customer's preferences, then deep-links into Bookly's reschedule flow. Cancellations follow the same pattern: the bot confirms the customer's identity, surfaces the cancellation policy, and links to the existing cancellation flow.

Group services with capacity are read from Bookly's config, and the bot quotes remaining seats accurately. So a yoga class with 12 spots and 9 booked returns '3 spots left' from real data. When a class fills up, it drops out of suggestions until a cancellation opens a seat. Capacity changes propagate through the same retrieval layer, so an admin who increases capacity sees the new number reflected in the bot's answers within minutes.