Yes. SleekAI uses Amelia's REST endpoints to check availability, so the bot will not suggest a slot that's already booked. The check happens at retrieval time, which means a slot that just got booked by another customer does not get offered to a visitor 30 seconds later. Employee day-offs and break times are honored automatically, since they're already in Amelia's availability calculation.

It pre-fills the booking form with the right service, employee, time and any package selection, then hands off to Amelia's standard checkout for payment and confirmation. This keeps payment, deposit logic, intake forms and confirmation emails on Amelia's existing flow rather than building a parallel system in chat. Direct-create flows are possible as a custom integration but not the default.

Yes. Amelia packages with their included services and pricing are part of context. A visitor asking about a 'wellness day' gets the real package returned, with all included services listed and the bundle price quoted. Packages are linkable from chat the same way individual services are, so the visitor lands on Amelia's package checkout with the right selection prefilled.

Each Amelia location is linked to services and employees, so the bot scopes answers correctly when visitors ask about a specific branch. A multi-location spa with Manhattan and Brooklyn shops can run two scoped bots, each only surfacing its own staff and rooms. Display conditions on the chat widget tie each bot to the matching landing page, so the right corpus loads automatically.

Yes. SleekAI works alongside WPML, Polylang and TranslatePress and responds in the visitor's language using the same service and pricing data underneath. Service names and descriptions get returned in the visitor's locale where translations exist; prices, durations and times are universal. International spa chains end up with one bot rather than one per locale.

Yes. Amelia events behave like services with capacity, and the bot reads them the same way including remaining seats. So a visitor asking about a workshop gets capacity, current registration count and the price quoted from the event record. Sold-out events drop out of suggestions automatically. Recurring events get exposed as discrete instances, so 'next Pilates class' is a concrete date.

Deposit rules per service are read into context and quoted accurately. The bot can say 'a $25 deposit is required to hold this slot, balance due at the appointment' from the actual Amelia setting. The handoff to checkout preserves the deposit collection step, so the customer pays the right amount up front and the rest follows Amelia's existing rules without needing parallel handling in chat.

Yes. Amelia custom fields and intake forms are preserved through the booking handoff. The chatbot does not collect the intake answers in chat by default, since intake forms often have legal or privacy implications, but it can prompt the visitor to fill the standard intake form on the checkout page. For specific custom fields the business can opt to ask in chat and prefill, but the default keeps intake on Amelia's existing UI.