Yes. First-year, transfer, international, and graduate flows can run as separate bots via display conditions, or as one bot with the system prompt routing by user input. Most universities run three or four bots so each admissions team can own its tone, deadlines, and CRM handoff. Conversation logs stay separate per bot, which makes review by team easier.

If your catalog is on WordPress (or synced into a public page), the bot reads course numbers, prerequisites, and offerings. For real-time enrolment data, link to your registrar's system rather than trying to mirror it. The bot can then explain the catalog accurately and point students to the live registration portal for current seat counts and waitlist position.

The bot answers from public pages only. It doesn't access student records, transcripts, or aid-package details. For account-specific questions, the bot routes students to the authenticated portal where FERPA-compliant access controls apply. This is a design choice, not a limitation: protected data should never be in a chatbot context, and the boundary keeps the bot's role clear.

Yes. 50+ languages supported by the underlying LLMs (OpenAI, Anthropic, Google). Mandarin, Spanish, Korean, Hindi, Arabic, French, and Portuguese all work natively, with output quality matching the model's training depth in each. The bot reads your English source pages and answers in the prospect's language, which matters for international flows where phone support is asynchronous at best.

Yes. Hand off leads via webhook to Slate, Salesforce, or any university CRM with a public endpoint. The bot includes the conversation summary, programme of interest, and key context in the handoff, so admissions counsellors call back with full picture rather than starting from a name and email. Most teams configure different webhook destinations per admissions path.

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. The plugin doesn't add a new vendor to your data path, which matters for universities that already have strict procurement and DPA processes. Apply your existing WordPress access controls and retention policies to the logs.

Yes, at the policy level. The bot can explain registration windows, add/drop deadlines, and prerequisite waivers from your published policies. For specific account questions (am I eligible to register, is this hold lifted, what's my actual aid package), the bot routes the student to the authenticated portal. That's the right line, and current students appreciate the directness.

If your articulation agreements with community colleges or partner institutions are on a WordPress page, the bot reads them and quotes the equivalents accurately. For one-off course evaluations not in the agreement, the bot routes to the registrar's transfer-credit form rather than guessing. Many transfer applicants ask about this before applying, and a clear answer here measurably improves transfer-applicant conversion.