Yes. If your Mandarin and Cantonese tracks live on separate WordPress pages, the bot routes the prospect by the first explicit signal (the question, the page they landed on, or the language they wrote in). Multibot lets you run a Mandarin-only bot on the Mandarin pages and a Cantonese-only bot on the Cantonese pages, each with its own tone, source pages, and exam-prep schedule. Most schools run both.

If your HSK 1 to 6 tracks live on WordPress pages with vocabulary ranges and grammar focus, the bot reads them. It maps a target HSK level and exam date to a realistic multi-cohort plan, with frequency and total weeks. The bot does not invent vocabulary thresholds; it quotes whatever you publish. Update one page and the bot updates immediately, which is exactly what you want when HSK syllabus revisions land.

Yes, in the first message. Prospects who say they speak Mandarin or Cantonese at home but cannot read, or who code-switch between Chinese and English in the first sentence, get routed to your heritage-speaker tracks. The system prompt sets the rule and the bot applies it consistently, which fixes the most common mismatch (heritage speakers in beginner conversation courses) without an admissions call.

Yes. Most Mandarin tracks default to simplified characters, most Cantonese tracks default to traditional, but exceptions are common. The bot reads your track pages and quotes whichever script you publish for each cohort. It also handles prospects who specifically request the other script (Mandarin learners targeting Taiwan, Cantonese learners targeting mainland publications) and routes them to the right teacher or private-tutoring option.

Yes. The underlying models speak Mandarin and Cantonese at native quality (simplified and traditional both). The bot mirrors whichever language the prospect writes in, including code-switching cases. For heritage-speaker enquiries that mix Chinese and English in the same message, the bot answers in whichever language led, with a short translation when useful. Test the bot's character output against a teacher's read before launching.

Yes. Calendly, Acuity, ClassPath, custom WordPress booking plugins, and LMS booking flows all work via deep link or webhook. The bot collects the preferred slot, track, and level in conversation, then either passes the prospect to your booking link with the slot pre-selected or fires a webhook that creates the enrolment server-side. Most schools use deep links for trial classes and webhooks for full enrolments.

Yes. Multibot supports an adult bot on the standard cohort pages and a kids or family bot on the Mandarin-for-kids pages, each with its own tone, source pages, and pricing. Conversation logs stay separate per bot, which makes it easier to review enrolment patterns by audience. Most schools that offer both run at least two bots, sometimes three when Cantonese-for-kids is a distinct programme.

Logs stay in your WordPress database. Bring-your-own-key sends prompts directly to OpenAI, Anthropic, Google, or OpenRouter with no third-party processor in between. That matters when prospects discuss heritage background, name preferences, or family context. The plugin does not add a new vendor to your data path. Apply your existing WordPress access controls and retention rules to the logs, and redact sensitive fields after enrolment completes.