Yes. SleekAI reads WooCommerce products, including HPOS order data, postmeta, shipping classes, and custom taxonomies, so product-level return rules are available as context. The policy page itself can live as a regular page or a custom post type, and the bot reads both. For sites using a non-Woo cart, the data-source wizard maps whatever post type and field shape your store uses.

For logged-in customers, yes. The bot can be scoped to logged-in role and given access to the customer's order data via display conditions, so a question like 'can I return order 18293' pulls real order line items, ship date, and item flags. For anonymous visitors, the bot answers from the policy and asks for an order number plus email before escalating, no data leakage to unauthenticated chats.

Yes, if exceptions are encoded on the product. A 'return_eligible' ACF flag, a final-sale shipping class, a perishable taxonomy term: the bot reads these and applies the right rule per item. For a bundle that contains both eligible and non-eligible items, the bot can answer at the item level, not the order level, which is usually what customers want to hear.

Yes. When the question exceeds policy (damaged item, gift return, international duty refund) the bot collects the order number, item details, the customer's reasoning, and their preferred outcome, and forwards a payload to Help Scout, Zendesk, Gorgias, or your CRM via webhook. The human reply starts with all the context already gathered.

The bot reads the policy page on every request, so any edit is reflected on the next reply. There is no fine-tune retraining, no scheduled re-index. Some teams pair this with a 'policy bot' running on /policies/returns specifically, scoped via display conditions and multibot, so the policy author can iterate without affecting cart or checkout bots.

Yes. The system prompt can encode an exchange-first stance for apparel and footwear, where size and color are common reasons for return. The bot offers the exchange flow first, mentions the no-restocking-fee benefit, and falls back to refund if the customer prefers. This is a small UX touch that retail teams consistently report as the biggest revenue win from the bot.

International returns are the highest-friction category, with carrier choice, duties, and longer windows in play. The bot can encode your specific international rules, with a deferred 'we'll confirm by email within 24 hours' for cases where customs paperwork is required. Conversation logs surface which destinations drive the most policy questions, useful signal for ops.

SleekAI is a one-time WordPress plugin license, not a per-conversation SaaS subscription. You bring your own OpenAI, Anthropic, Google, or OpenRouter API key, so you pay the provider directly at standard API rates. There is no token markup, no resolved-conversation fee, and no monthly seat cap, even during a holiday-returns spike.