Yes. Sensei stores courses, lessons, and quizzes as standard WordPress posts, and per-student progress as comments on the lesson posts. SleekAI can include all of that in the bot's context. Other students' progress never enters the prompt, since SleekAI scopes data to the currently logged-in user.

Yes. Sensei Pro fields stored as post or user meta can be exposed to the bot just like core ones. Pro features like advanced quizzes, certificates, and groups all surface as variables that the bot can reference, since Sensei keeps everything in standard WordPress shapes that SleekAI's data sources understand.

Yes. Display conditions support post type and specific posts, so each Sensei course can have its own dedicated bot, with its own system message and tone. The same install can run a corporate training bot, a customer-education bot, and a public marketing bot, each scoped to its own pages.

Push transcripts into an OpenAI Files vector store of up to one gigabyte per file so the assistant can retrieve only the passages that match the question. That keeps the prompt compact even on multi-hour video courses, and it makes the bot's answers cite specific moments rather than summarise the entire lesson.

Only if you choose to include them. The Wizard maps fields one at a time, so the quiz question and answer key can be left out of the prompt while the score and weak-spot summary remain. That keeps the bot useful for review without revealing answers ahead of a future attempt.

Inside WordPress, with model name, token usage, and page URL attached to every conversation. Instructors can review which modules trigger the most questions and use that as a quiet feedback loop on the curriculum, since recurring confusion almost always points at a lesson section worth rewriting.

Yes. Sensei stores lesson length on each lesson post, and SleekAI can include the remaining lesson durations in the system message. The bot can then give a real time-to-finish estimate for the specific student, broken out by module if you map that level of granularity.

Yes. Sensei Groups are stored as taxonomy terms or custom post relationships depending on your setup, and SleekAI reads them as it would any other field. Display conditions can scope the bot to a specific group, useful when a single Sensei install is shared across departments or external training partners.