Yes. The sync add-on writes a Google event ID onto each appointment row. SleekAI maps that column into a named variable, so the bot can list bookings that pushed cleanly and bookings that still need attention. You do not need to expose the raw table to the prompt.

From Bookly. Bookly is the source of truth for working hours and existing appointments. The Google Calendar Sync add-on then pushes those rows to staff calendars. The bot answers availability questions from Bookly directly, which means there is no extra Google API quota hit on each chat reply.

Yes. Multibot lets you run several chatbots on one site. A common setup is a staff bot inside WP Admin scoped to administrators and shop managers, plus a public bot on the booking page with no access to internal admin data. Each bot has its own system message and data sources.

No. SleekAI does not call the Google Calendar API. It reads the sync state stored by Bookly in WordPress, which is enough to answer the most common questions. If you want the bot to push or edit Google events directly, expose a tool endpoint that wraps the Google client your sync add-on already configures.

Display conditions let you scope a chatbot to logged-in users with a particular role or to a specific page. A customer-facing bot on the booking page can be given only the variables a customer should see, like generic free slots, while a separate admin bot in WP Admin has access to the full appointment list.

Yes. Bookly stores the connected Google account per staff member, and SleekAI reads staff metadata along with appointments. The bot can answer "is Lisa free" and "is Marco free" with each staff member's own schedule, even when they are connected to different Google accounts.

Yes. Conversation logging is per chatbot, with user messages, assistant replies, model name, token usage, and page URL stored inside WordPress. Owners use the log to spot repeated questions about the sync and to retire confusing menu items in the admin interface.

SleekAI's data mapping is point-and-click and stored separately from the add-on. If the next release renames a column, you adjust the mapping in the SleekAI Wizard and the bot keeps working. There is no hard-coded SQL in the chatbot logic to break on an update.