Yes. SleekAI maps the Bookly payments and appointments tables into named variables your system message references on each request. For a logged-in customer the bot resolves to that customer's own bookings and payments, so the deposit amount and the remaining balance are real numbers from your database, not a guess.

Out of the box the bot reads data and answers, which removes the most common deposit questions. For a fully conversational refund you expose a tool endpoint that wraps the refund flow your payment gateway already supports. SleekAI's PHP and JS hooks make that integration straightforward.

Yes. Deposit Payments lets you set a fixed amount or a percentage per service. SleekAI maps the per-service deposit rule into a variable, so the system message includes the right number for the service the customer is asking about, with no manual templating in the prompt.

Display conditions let you scope a chatbot to logged-in users with a particular role. SleekAI variables resolve to that user's own bookings and payments, so a customer never sees another customer's row. Guests on the public booking page see only generic deposit-policy answers.

Whatever Bookly stores. The payment row includes the payment method, last four digits if your gateway exposes them, and the status. SleekAI maps that into the prompt so the bot can say "Visa ending 2210" rather than "card on file" when you allow it to share that level of detail.

Yes. Some studios charge a deposit and then split the balance into smaller payments. SleekAI reads the payments table, so if Bookly records multiple payment rows against one appointment, the bot can list each one and sum them to confirm the remaining balance without manual logic.

Conversation logging is per chatbot, with user messages, assistant replies, model name, token usage, and page URL stored inside WordPress. Studios use the log to audit what was promised about a refund before a chargeback and to refine the cancellation copy on the booking page.

Yes. SleekAI reads from Bookly's payments table, which is gateway-agnostic. Whether the deposit was taken via Stripe, PayPal, Mollie, or any other Bookly-supported gateway, the bot sees the amount and method recorded against the appointment without provider-specific code.