Learner operations layer

Answer learners fast. Keep them enrolled.

Handle admissions questions, enrolment steps and course support, and nudge learners who stall — without pretending this is a K-12 school OS.

Built for Course academies, cohort programmes and edtech teams.

Scope this with us

The problem

Prospective students ask the same questions before enrolling, and current learners drop off when support is slow or absent.

In practice

A learner stuck on module three asks a question at 11pm, gets a clear answer with a link to the relevant lesson, and a follow-up two days later checking they are back on track.

11pm

Questions still get an answer

Grounded in the lesson they are on

Fewer

Enrolment drop-offs

The same five questions stop blocking checkout

Nudged

Quiet learners

A check-in when the cohort moves on without them

Routed

Payments and exceptions

Humans get the record, not a blank ticket

The shift

From a community dump to a learner who knows the next step

From this

  • ✕The same admissions FAQs in email, Instagram and WhatsApp.
  • ✕Enrolment dying at payment because nobody replied.
  • ✕Course questions living in a noisy group chat.
  • ✕Learners who vanish after module two.
  • ✕Tutors repeating timestamps instead of teaching.
  • ✕Refunds and special cases lost in the same inbox.

To this

  • ✓Admissions answers from the actual curriculum and dates.
  • ✓Enrolment steps in the thread, with a human on payment exceptions.
  • ✓Lesson-level answers with a link, not a vibe.
  • ✓A nudge when someone goes quiet — written like a person.
  • ✓Tutors see the stuck learners, not the FAQ pile.
  • ✓Special circumstances arrive with the enrolment record open.

What's included

From first enquiry to a learner who finishes

Admissions Q&A

Dates, eligibility, what the cohort actually covers — from your course data, not a hallucinated syllabus.

Enrolment walkthrough

The steps, the payment, the WhatsApp community link. Exceptions go to a person.

Lesson support

‘Where was the API bit?’ gets a timestamp and a resource, grounded in the module they are on.

Stall detection

Quiet for a few days while the cohort moved? A nudge with the next lesson, not a guilt trip.

Tutor inbox

The questions the corpus cannot answer land with context: module, attempt, what they already tried.

Community hygiene

The group chat is for peers. The repetitive questions leave it.

Certificate / progress

Where they are, what is left, when the live session is — without opening five tabs.

Refunds and special cases

Policy-aware routing. The layer does not invent a refund; it starts the request.

Every role connected

Built around how each desk actually works

For the academy desk

Stop answering ‘when does it start’ at midnight.

  • Prospects get the real dates
  • Enrolment exceptions flagged

For tutors

Teach the hard bits. The timestamps are automated.

  • Stuck learners visible
  • Context on every escalation

Go-live

Implementation without a year-long project

  1. 1

    Week 1

    Corpus

    Curriculum, FAQs, enrolment policy, the LMS you already run.

  2. 2

    Week 2

    Admissions + enrolment

    The public questions and the checkout path.

  3. 3

    Week 3

    In-course support

    Lesson answers and stall nudges on one cohort.

  4. 4

    Week 4

    Tune

    What it must never say about outcomes, jobs, or refunds.

Ideal for

Cohort programmes and course businesses — not a full school OS

Deployment

On your LMS, WhatsApp and the site you already have

Commercials

Scoped per catalogue and cohort size

How we approach it

  1. 1

    The AI answers admissions and curriculum questions from your course data, and walks prospects through enrolment.

  2. 2

    For enrolled learners, it answers content questions and points to the right lesson or resource.

  3. 3

    It spots learners who have gone quiet and sends a personalised nudge.

  4. 4

    Anything requiring a human — payment issues, special circumstances — routes with context.

Scope this for your team

FAQ

Questions about education & online courses

Is this a school ERP?

No. K-12 operations (attendance, fees, report cards, RTE) live on the School Management use case. This layer is for course academies and edtech.

Will it invent job-guarantee language?

No. Outcomes and refunds are bounded by your published policy. The model does not get to market for you.

Can it teach the course?

It points at the lesson you already made. It is not a replacement tutor.

Want learners answered without another community dump?

Bring the syllabus and the questions you answer every week. You leave with a written plan for admissions and in-course support.

We’ll tell you if a platform already fits better.

Book a discovery call