The student who gets stuck does not come back, and almost nobody checks who stopped logging in

A student gets stuck in week two. They do not write in, do not post in the forum and do not ask for help: they close the tab and tell themselves they will pick it up on Sunday. By week four they are not logging in, and by week six they ask for a refund or simply disappear.

Almost no online school has anyone watching who has stopped logging in. Enrolment gets watched, since that is the number that goes up, while silence, the number that costs money, does not.

In online education, support is retention

There is an underlying misunderstanding worth clearing up. In a shop, customer service is a cost you try to reduce. In online education it is the opposite: every conversation with a student who was on their way out is an enrolment you do not have to sell again.

And the work does not spread out evenly. A school's calendar has peaks —every enrolment window, every launch— and long troughs. In the peak, queries multiply, along with failed payments and access links that do not work. And that is precisely when the team is preparing the course, recording or marking, which is exactly what they cannot stop doing.

The result is predictable: the enrolment window gets handled halfway, and the following month you lose students nobody connects back to that week.

The first 48 hours after enrolment

More gets decided here than it looks. The student has just paid, they are motivated, and that motivation has a short shelf life. Anything standing between the payment and the first lesson is charged to retention.

What goes wrong in those 48 hours is almost always the same, and almost always mechanical:

• Payments that do not go through. A declined card, a charge left half-made, an instalment that does not match what the student thought they were buying. If nobody spots it and gets in touch the same day, the student assumes they are in, finds the door shut, and gets annoyed with good reason.
• Access that never arrives. The welcome email in the junk folder, the account created without the course assigned, the link that expires before they open it. It is the number one reason for those first messages, and the cheapest to resolve.
• Platform questions that look trivial. Where the syllabus is, how the material downloads, why the video will not play, whether there is an app. None of them is an academic question and all of them stall the start.
• Miscalibrated expectations. The student expected live classes and they are recorded, or the other way round. Support does not fix that, but it is where it gets detected, and detecting it in week one means you can talk to them instead of reading about it in a review.

None of those four requires knowing the subject matter. They require somebody being available when the student writes, with permissions on your platform and your payment policy in front of them. It is the moment when having the role covered shows most, and the worst possible moment to be training somebody new.

Catching drop-off before it becomes drop-off

This is the part almost nobody does, and the one that gives the most retention back. It is not reactive support: it is looking at the data your campus already stores and acting on it.

Your platform knows who has not logged in for ten days, who stopped at lesson three of twelve, who has not handed in the first assignment, and who watches the videos at double speed without opening the material. No sophisticated model is needed: a weekly list is needed, and a person who writes.

What works is a short message, personal and with no blame in it. Not «this is a reminder that you have not logged in for ten days», which reads like a debt notice. More like: you stopped at module three, that is the one people get stuck on most, here is what most of them need to get through it, can I help with anything specific? The gap between those two versions is enormous, and anyone with your tone in their head can write the second one.

Two warnings. First: define the threshold before starting, or you end up writing to everybody or to nobody. Seven days without logging in, or two lessons behind the expected pace, are reasonable starting points. Second: this gets written down. Who gets stuck and where is the most valuable information your school produces, and it is lost if nobody records it.

Community moderation needs written rules

If you have a forum, a group or a community, you have two different jobs that often get conflated.

The first is answering what can be answered: access, calendar, where something is, how an assignment is submitted. Whoever handles support covers that, and the sooner it is answered, the fewer repeat questions pile up underneath.

The second is moderating, and that one does depend on you having written the rules. What happens with self-promotion, with someone asking for pirated material, with a discussion heating up, with a comment attacking another student, with someone criticising the course in public. Each of those cases has a reasonable and different answer, and none can be improvised in front of two hundred people.

The practical rule: what is in the rules gets applied without asking; what is not in the rules gets escalated with the case put together —who, where, what they said and what is being proposed. Without that list, moderating turns into asking permission for every message, and then you have delegated nothing. With it, community moderation holds up on its own.

And one thing worth watching even though it is not moderation: what repeats. Three students asking the same thing in the forum are not three queries, they are one badly explained lesson or one ambiguous brief. Each of those gets fixed once and stops generating questions forever.

What we would not delegate in your position

Course content and academic marking. That is your product, it is what the student bought, and whoever touches it has to command the subject rather than the platform. Nothing in this article is about writing lessons, reviewing assignments or grading.

And decisions on refunds outside policy. The case gets prepared and escalated —what the student asked for, what your policy says, how much of the course they have consumed— but you sign the exception. In education there is a specific reason: a badly granted exception travels round the community in an afternoon, and the next person claims it as an established right.

Academic admin, never urgent until it is

There is one more layer, entirely unglamorous, that piles up: registrations and withdrawals, certificates, instalments and receipts, records of students asking for proof of study two years later, payments left half-collected that nobody chased.

None of that is urgent on Monday, which is why it gets postponed. The problem is that it gets postponed for months and then arrives all at once, usually coinciding with a year-end or an internal review. It is volume work, with written criteria and no hard decisions: exactly what an admin role covers, and usually what frees up the teaching team's first useful hours.

Where to start

Start where students fall away, which is almost never where you think.

First, enrolment and access: failed payments, access that does not arrive, and platform questions in the first 48 hours. That is the exact moment a student decides whether to stay.

Then the student who gets stuck: a weekly list of who has stopped logging in, and a message written before they ask for a refund. Nobody does this for lack of time, and it gives the most back.

And the community once there is volume, with the rules written before the first conflict rather than after it.

If you want to see the whole path with the sector's own tools —your campus, your inbox, your payment gateway— it is on the online education page.

And if you measure nothing today, start with a single number: how many students from the last cohort have not logged in for ten days. It is uncomfortable to look at and it decides everything else.