Any plugin that stores points balance in WordPress, which is almost all of them. WooCommerce Points and Rewards stores balance in usermeta, YITH Loyalty stores it in usermeta and custom tables, Advanced Coupons stores it in usermeta. SleekAI's data source wizard maps the relevant keys once. If your loyalty system is bespoke, the bot can be pointed at any custom table or postmeta where balance and history live.

Both options are supported. The light-touch flow has the bot quote the balance and matches, then link the customer to the standard redemption page. The deeper flow has the bot fire a redemption action via the loyalty plugin's API or a custom REST endpoint when the customer confirms in chat, creating the discount code or store credit on the spot. Most stores start with the light-touch flow and add the action layer once the data flow is proven.

Yes. The bot reads the tier on the user record and adjusts the system prompt accordingly. Gold customers can get suggestions weighted toward higher-value redemptions, Silver customers see entry-level options, and Platinum customers get exclusive access mentions. Multibot lets each tier have a separate bot if the program is large enough to warrant the differentiation; otherwise one bot reads the tier field and adapts.

If your loyalty plugin tracks points by earn date (most do), SleekAI can read the per-block expiration data and warn customers when points are nearing expiry. The bot can also be configured to proactively bring up expiration when the next-to-expire block is within 30 days, so customers redeem before the silent zeroing happens. Expired points are one of the loudest forms of program churn; visible expiration prevents the worst of it.

Partially. For non-logged-in visitors, the bot can explain how the program works, the redemption tiers, and how to earn points, but it cannot quote a personal balance because there is no user record to read. Once the visitor logs in, the bot picks up the balance from usermeta. For email-only signups (no full account), the conversation can ask for the email and look up the linked points record if your loyalty system supports that.

Yes. Many programs run both: a points balance for earn-and-burn behavior and a store credit balance for refund handling. SleekAI reads each from its respective storage location and can quote both balances in a single answer. The customer asks 'what do I have', the bot answers '1,840 points (worth 18 USD) plus 12 USD in store credit', which is the unified view the customer actually wants.

No. The bot reads live stock on the catalog and only surfaces redemption matches that are buyable today. Redirecting a customer to a redemption option that is sold out is a worse experience than not surfacing it at all, so the bot filters by stock state before quoting matches. If your redemption catalog is small enough that everything is occasionally out of stock, the bot can fall back to suggesting an in-stock category gift card.

Yes. SleekAI logs every conversation with the redemption choice the customer made. A simple SQL query against the chat log joined with the loyalty plugin's redemption history shows which conversations led to actual redemptions and the points value of each. That report tells the loyalty team which kinds of suggestions land best and where the program copy is still missing the mark.