Yes. SleekAI reads any WordPress post type, including LearnDash sfwd-courses, sfwd-lessons, and sfwd-topics, plus Tutor LMS courses and lessons, plus Sensei LMS posts. The data-source wizard maps the post-type fields you want exposed (title, summary, learning outcomes from ACF or post meta) and the bot answers from those fields directly. No re-authoring of content into a separate dataset.

Yes. The 28+ display conditions include user role and logged-in state. Set the post-purchase bot to fire only when the user is logged in and has the role assigned by LearnDash, Tutor LMS, or your membership plugin (MemberPress, Paid Memberships Pro, BuddyBoss). Visitors who aren't enrolled see the pre-purchase bot only; enrolled students see the support bot on lesson pages.

Yes. Configure the prompt to surface preview content (preview module URL, curriculum PDF, lead-magnet PDFs) when the conversation reaches the right intent signal. The bot can also offer first-time-enroller coupons via your WooCommerce, EDD, or LearnDash Stripe integration. Coupon codes themselves are configured in your store; the bot only references them when the prompt rules say to.

When you publish a new lesson or update an existing one, the bot reflects the change on the next conversation. No retraining, no re-indexing for small edits. For large curriculum overhauls, the OpenAI Files vector store option scales to 1GB per file, which covers most courses' full lesson transcripts plus reference material. Most creators run with direct-read for landing pages and vector for transcripts.

Yes, if you publish the transcripts. The student-support bot reads lesson transcripts, code examples, and homework solutions from WordPress and answers 'why did module 3 import pandas as pd before reading the CSV?' by quoting the relevant transcript section. For courses where homework is graded, the bot can describe the rubric and point to the model answer without giving away the solution to ungraded prompts.

Logs stay in your WordPress database. Bring-your-own-key sends prompts directly to OpenAI, Anthropic, or Google with no third-party processor in between. That matters for student support: enrolled students share work-in-progress code, datasets, and sometimes confidential employer context. You control retention and redaction, and the plugin doesn't add a new vendor between you and the model.

The bot describes your refund policy (14-day money-back, pro-rated cancellations for monthly plans) and captures the request, but it doesn't process the refund itself. Most creators route refund intents to a tagged email queue or a Zendesk-style ticket, with the bot summarising the reason captured in chat. This keeps the human-review step intact for accounting and prevents bot-driven refund loops.

Yes. Multibot lets you run a separate bot per course, each with its own curriculum data source, tone, presets, and pricing context. Most creators with three or more courses run one bot per course on the relevant course landing pages, plus a top-level 'pick a course' bot on the home and pricing pages that routes prospects to the right course based on goal and background.