Yes. LifterLMS stores progress as user meta keyed by course and lesson, and quiz attempts as their own table. SleekAI can include the logged-in student's progress and last attempt in the system message so the bot answers from real data. Other students' progress never enters the prompt, regardless of what is asked.

Yes. Display conditions support specific posts and post types, so each LifterLMS course can run its own dedicated bot. A creative-writing course can use a warmer system message and a technical one can use a stricter style, all under multibot on the same SleekAI install.

Only if you map them. SleekAI's data sources expose fields one at a time, so the quiz question and answer key can be left out entirely while still letting the bot reference the score, percentage, and which question types the student got wrong. That keeps the bot useful for review without leaking the next attempt.

Yes. Push transcripts, workbooks, and supplementary PDFs into an OpenAI Files vector store of up to one gigabyte per file. The bot retrieves only the passages that match the question, which is a better fit for long course content than stuffing everything into the prompt.

Both. SleekAI ships a floating widget, a shortcode, and a PHP embed function, so the bot can live in a corner of the lesson page or sit inline next to the lesson content as part of the template. The same chatbot can be embedded in multiple places without duplicating its system message.

Yes. Conversations are logged inside WordPress with the user, page, model, and token usage attached. Instructors can review which lessons trigger the most questions and either rewrite the lesson or update the bot's system message to address the recurring confusion.

Yes. LifterLMS drip schedules are stored as standard meta on the lesson, so the bot can include the unlock date and explain when the next lesson becomes available to the specific student asking. That avoids the typical 'why can't I see Lesson 6 yet' email entirely.

Yes. LifterLMS access plans and memberships are stored as posts and user meta, which SleekAI reads like any other field. Display conditions can also gate the bot to specific membership levels, so a paid tier sees a more capable bot and free users see a lighter one.