A training company website gets two distinct audiences: individuals exploring an open-cohort enrolment and corporate buyers scoping a private cohort or licensing deal. They need wildly different conversations. The individual wants prereqs, dates, payment options, refund policy. The corporate buyer wants customization, headcount pricing, delivery format, certification, and timeline. SleekAI splits the two on the first message and runs the right qualifying conversation for each.

The bot reads your course catalog, your cohort schedule, your enrolment options, your corporate packages, and your case studies from WordPress (post types, ACF fields, taxonomies, the data-source wizard handles each). When an individual asks about the next data engineering cohort, the bot quotes start date, price, prereqs, and payment plan options. When a learning lead at a 500-person company asks about a custom cohort, the bot quotes the licensing structure and books a scoping call with the corporate partner.

BYO API key means OpenAI, Anthropic, Google, or OpenRouter and you pay only your provider. Conversation logs stay in WordPress with model name, token usage, and page URL, so the company sees which course pages generate which inquiries and where the next investment in editorial would do the most good.

A training company website carries two completely different products in the same shop window. The open cohort product is a consumer purchase: a learner browses, compares dates, weighs payment plans, and either clicks enrol or walks away. The corporate cohort product is a B2B sale: a learning and development lead scopes a custom program for a team, negotiates seat pricing, and signs a contract over the course of weeks.

Treating both audiences with the same generic course FAQ leaves both audiences underserved. The learner doesn't get clear answers on the next start date, prereqs, and payment plan options. The corporate buyer doesn't get a real scoping conversation; they get a generic "contact us for enterprise pricing" link.

A chatbot that splits the two on the first message and runs the right conversation for each replaces the entire triage layer. For learners, the bot answers the practical questions (start date, prereqs, capacity, payment plan, refund policy) and hands off to the LMS for enrolment, which is the path the learner wanted anyway. The friction that loses individual enrolments is mostly procedural friction, and a bot that resolves it in chat closes the gap.

For corporate buyers, the bot qualifies headcount, format, customization, and timeline, then routes to the corporate partner with the full transcript attached. The corporate scoping call opens with the cohort shape already drawn rather than with the partner running discovery from scratch, which compresses a typical B2B sales cycle by at least a meeting. The cohort-schedule integration is the multiplier.

Most training companies maintain a schedule that updates frequently (new cohorts, capacity flags, early-bird pricing windows) and that schedule is the single most valuable piece of information on the site. A bot that reads the live schedule from the custom post type and quotes the next three start dates accurately, including capacity flags, means the visitor never sees stale information. That removes the most common reason individual learners abandon the funnel: the suspicion that the date they're seeing might not be current.

And because the conversation logs sit in WordPress with the model name, token usage, and page URL captured, the company gets a structured view of which course pages generate which kinds of inquiries, which directly informs editorial investment, sample case studies, and which cohorts to add to the schedule next.