WooCommerce Deposits stores its product settings under postmeta keys like _wc_deposit_enabled, _wc_deposit_type (percent, fixed, or plan), _wc_deposit_amount, and _wc_deposit_payment_plans. Payment plan definitions live in wp_wc_deposits_payment_plans, and scheduled future payments land in wp_wc_deposits_scheduled_orders with their due date and amount. SleekAI maps those fields as named variables so the bot answers with the exact deposit configured on each product.

That makes deposit questions one-shot. A shopper asks how much they need to pay today for a $1,200 frame and the bot reads _wc_deposit_type=percent and _wc_deposit_amount=25 and returns $300 down, with the remaining $900 due on the configured plan. An existing customer asks about their balance and the bot reads the related scheduled orders and lists each remaining instalment with its due date.

Display conditions can scope the bot to deposit-enabled products and the My Account orders pages, so checkout traffic on non-deposit products keeps hitting the standard support bot. Conversation logs capture each deposit and balance question with model name and token usage, useful when finance teams want to audit how the bot describes payment timing or measure how many balance questions are getting answered without a human.

Deposits and partial payments are the most paperwork-heavy transactions a WooCommerce store handles. Every product has a different rule: 25 percent down here, a fixed $100 deposit there, a 4-instalment plan over there, balance-on-ship for custom work. The numbers are obvious to the admin who configured them, but invisible to the shopper standing on the product page or checking their card statement two months later.

Most stores end up writing a deposit FAQ, linking it from the cart, and still answering the same three questions in every other email. WooCommerce Deposits already structures the data. The deposit type is in postmeta, the amount is in postmeta, the schedule rows are in wp_wc_deposits_scheduled_orders, and the status of each future charge is right there with the due date.

A chatbot that reads the same fields turns every "how much today" and "what is left" into a one-shot answer, and only the genuine edge cases (a customer who wants to combine two plans, or a failed instalment that needs a payment method update) reach the inbox. Generic chatbots cannot do this. They have no idea what your deposit percentage is, let alone which row in scheduled_orders is due next.

They will either send the customer back to the product page they just left or guess at a number, which is worse than guessing at a tracking number because money is involved. The variable mapping between the bot and the actual deposit meta is what makes the answer trustworthy. It is also what makes the bot honest when a plan has a failed row attached, because the status is right there and the instruction tells the model to acknowledge it instead of pretending the schedule is on track.