Three sources: the delivery_slots custom post type with start_time, end_time, capacity, and zone_id; the shipping_zones table that maps postcodes to zones; and the cart or order details for weight, volume, and shipping address. SleekAI exposes all three as mapped variables so the system prompt can ask the model to filter accordingly.

Yes. SleekAI supports function-call style actions where the model can call a webhook with structured arguments. A 'book_slot' action takes a slot_id and order_id, runs server-side capacity checks, and returns success or a reason for failure. The bot then confirms the booking conversationally.

Capacity logic stays on the server, not in the model. The webhook receives the booking request, takes a row-level lock on the slot, decrements capacity inside a transaction, and either returns the confirmation or a 'slot just filled' message the bot relays to the customer. The model never has authority to commit a booking by itself.

Yes. WooCommerce shipping zones and cart data are accessible as mapped variables. Many users keep the delivery_slots structure in a custom post type rather than a Woo extension because it gives more control over capacity, vehicle assignment, and cutoff rules without paying for an addon.

The bot can read the existing booking from the order and offer a reschedule window, then call a 'reschedule_slot' webhook that releases the old slot and books the new one in a single transaction. Cancellations work the same way. Every action is logged with timestamps so customer service can audit later.

Yes. Each slot can carry a price postmeta. The bot quotes the price difference when offering a premium window and the booking webhook applies the surcharge to the order. Customers see the price up front in the conversation instead of being surprised at checkout.

A small, fast model handles the conversational layer well because the heavy lifting is in your webhooks, not in the model's reasoning. GPT-4.1 mini, Claude Haiku, or Gemini Flash are usually plenty. You can upgrade to a stronger model for the bot if the conversation tone matters more than per-message cost.

Scheduling plugins give you a calendar widget on a page. The chatbot lets the customer book in the same conversation as their other questions, which is closer to how phone bookings work. You can keep the calendar widget as a fallback and let the bot handle the customers who prefer to ask rather than click.