If your seat count lives in a custom field (ACF or postmeta) on the cohort post, yes. SleekAI reads the value on every conversation, so when an admin manually decrements after each enrolment, the bot reflects the new count in seconds. For automated decrement, fire a webhook from your checkout to update the field. Some creators just publish a soft 'fewer than 10 left' indicator instead of an exact number; the bot quotes whatever you publish.

Yes. Put your prerequisites on a dedicated page or in the syllabus and the bot will read them. For nuanced cases (senior eng manager wants to take a PM-101 course), tune the system prompt with examples of when to recommend it anyway versus when to suggest skipping ahead. The bot then handles experienced edge cases honestly rather than gatekeeping by default.

Yes, and accurately. Most generic chatbots invent a 14-day or 30-day refund window because that's what training data says. SleekAI reads your published policy. If you offer 'full refund through end of week 2 if it isn't a fit', the bot quotes that exact phrasing. Same for recording access (lifetime, 12 months, 90 days post-cohort).

Indirectly. SleekAI is a WordPress plugin, so it reads from WordPress. Most cohort creators run a landing page in WordPress and host the actual course on Maven, Teachable, or Circle. The bot reads your WordPress sales page and hands off to your Maven cohort page, Teachable checkout, or Circle community via deep link. Webhooks let the bot fire enrolment events to your CRM.

Yes, via multibot. Most creators with multiple courses run one bot per course landing page, each with its own system prompt, source pages, and tone. Conversation logs stay separate so you can review enrolment patterns by course rather than scrolling through one mixed log. Display conditions can also restrict by URL pattern, so alumni see a different bot than first-time visitors.

Configure the prompt with your evergreen behaviour: 'When the current cohort is sold out, recommend the next one with its start date and waitlist link.' The bot then redirects warm prospects to the next launch instead of dropping them. Logging cart-close-day overflow is useful: it shows which cohorts could justify a faster relaunch.

Yes. Most cohort sales pages have an outcomes section with skills, deliverables, or 'by the end of this course you will...' bullets. The bot reads these and uses them to answer the 'will this get me what I need' question with specifics from your page rather than a generic 'you'll learn a lot' deflection. Outcome citation in answers also tends to lift conversion.

Yes, and many creators use this to reduce 'no-show' applications. Configure the prompt to ask 2-3 qualifying questions in conversation (current role, goal, time available) before passing the prospect to the application link. The bot logs answers so admissions sees the qualification pre-filled when the application arrives, cutting review time by half.