SleekAI reads your live WordPress data. The ship date and the allocation cap are usually stored as postmeta on the product, often _preorder_ship_date and _preorder_max_units. The data source wizard maps those keys once and the bot quotes the values at query time, so when the launch team updates the ship window the chatbot answers update with it. No retraining required.

Yes, if you store an incrementing counter on each pre-order. SleekAI can read that counter against the total allocation cap and tell the shopper their slot number. This is a powerful conversion trigger ('you'd be slot 142 of 500'), but it also sets expectations honestly so shoppers further down the queue understand they may be moved to the next allocation if cancellations are low.

The bot quotes your published cancellation and delay policy, usually stored as a published terms page or a postmeta block on the pre-order product. Many stores set a slip threshold (often 2 or 4 weeks) above which the customer is entitled to a refund. The bot states the threshold clearly so the policy is in the shopper's hands at the moment of commitment, not buried in a terms page they did not read.

SleekAI does not process payments directly; it quotes the deposit and balance values from your product data. The actual billing happens through your existing WooCommerce pre-order extension or custom code. The chatbot's role is to make the timing and amount clear in plain language, which dramatically reduces the chargeback rate that comes from shoppers who forgot the balance was coming.

Yes. The bot reads the postmeta fields that pre-order plugins set, regardless of the specific plugin. WooCommerce Pre-Orders, YITH Pre-Order, custom code, and bespoke deposit setups all leave their data in postmeta or product attributes, and SleekAI can be pointed at any of them through the data source wizard. The integration is at the data layer, not the plugin layer, which makes it portable.

Yes. SleekAI supports multibot, so each launch can have its own chatbot with a launch-specific system prompt, ship window, vocabulary, and quick replies. A hardware drop and an apparel collab can run side by side on the same site with completely different tones, which matches how launch teams actually think about each campaign.

If those numbers are stored in your data (per-country VAT rules, shipping calculations, duty estimates), the bot can quote them when asked. Many stores fudge this by deferring duty calculation to checkout; the bot can match that policy by saying 'duties are calculated at the balance-charge step' instead of inventing a number. Either way, the answer matches your real pricing logic.

Yes. Before the pre-order goes live, the bot can run in waitlist mode, capturing emails and the variation a shopper plans to reserve. When the pre-order opens, those waitlist contacts get a notification through your existing email tool with the conversation context attached. This is how stores convert hype-period traffic that is too early to commit but committed enough to leave an email.