Schools: enrolment, waiting lists and notices without the chaos

A tutoring centre doesn't have customers. It has groups. That sounds like a technicality until September arrives and your front desk is simultaneously answering the phone, slotting a teenager into Tuesday B1, explaining the enrolment fee for the fifteenth time, and telling twelve families the 6pm teacher is off sick. If you run a language school, a tutoring centre or a music academy, this is about splitting that chaos up: which parts an agent can carry, which parts it should never touch, and where to start.

Your year isn't nine months long. It's three weeks

On paper the academic year runs September to June, but front-desk workload isn't spread across it — it piles into two avalanches. September, which really starts in late August and eats the first three weeks of term. And January, shorter but just as sharp.

During those weeks you don't have an organisation problem, you have a physics problem. Four people asking about the same 5:30pm group at once, a parent wanting to know if their daughter can move up a level, someone requesting a placement test for tomorrow, and three messages from people who enrolled in June and now want the final timetable. Hiring an extra person for six weeks a year doesn't add up. Not hiring them means replies take two days — in the exact stretch of the year when people decide fastest.

The rest of the year, the front desk is calm. Which makes the maths here different from most businesses: you're not saving half an hour a day, every day. You're buying capacity in the three weeks that set your annual revenue.

Enrolment isn't a booking, it's seven steps

When someone books a table at a restaurant, that's it — one decision, one confirmation. Enrolment doesn't work like that. Between "hi, do you do English for adults?" and a student sitting in a classroom there's a long chain:

1. The first enquiry: which levels, what times, how much.
2. The placement test, which has to be scheduled and sometimes marked.
3. Group assignment, which depends on level and on the timetable that suits them.
4. Confirming there's actually a seat left in that specific group.
5. The paperwork: details, guardian details if it's a minor, direct debit.
6. First payment or deposit.
7. The final notice with room, teacher and start date.

Every step leaks. People drop out between 2 and 3 because nobody told them which group they'd landed in, or between 5 and 6 because the form stalled halfway and nobody chased it. An agent doesn't "do enrolment" — what it does well is hold the chain together. It answers step 1 instantly with your real prices, books step 2 into the slots you've defined, collects step 5 conversationally, and — this is the part that pays — chases the people who stalled. A next-day "hey, you didn't confirm your seat in Tuesday/Thursday B1, still interested?" recovers more enrolments than any ad campaign.

Waiting lists per group, not per school

This is what separates a school from a salon or a clinic. Your unit of sale isn't a free hour — it's a seat in a specific group. Tuesday/Thursday 7pm B1 with Laura has twelve seats, and they're not interchangeable with Monday A2 or with the morning B1.

So your waiting list can't be a list. It has to be many small lists, one per group, with people sitting on two or three at once in order of preference. When someone drops out of 7pm B1, what should happen is precise: notify the first three on that list — not the forty people who once said "English" — give a short window to confirm, and move down if nobody replies.

There's a business decision hidden in there that the agent should not make: when to split a group. If seventeen people want evening B1, someone has to decide whether to open a second group, buy the teacher hours and find the room. That's you. What the agent can do is put the number in front of you the moment it happens: "Evening B1: 12 seats full, 5 waiting, oldest 4 days." Without that alert, the information lives in your receptionist's head and surfaces in October, by which point those five have enrolled down the road.

The notices hurt more than the enrolments

Enrolments are seasonal. Notices never stop, and they're what actually burns out a front desk. Teacher off sick Tuesday. Room change because of building work. Make-up class for the bank holiday. Bounced direct debit. A student who hasn't shown up in three weeks.

They all share a shape: outbound, repetitive, obvious template, obvious recipient. It's the most automatable work you have and, oddly, the last thing anyone automates. An agent wired into your groups sends the room-change notice to those twelve students (and their guardians, if they're minors), collects the replies, and tells you who hasn't read it so you can phone that handful.

Two deserve their own mention:

• Bounced payments. Chasing money is uncomfortable, so it gets delayed, and the longer it's delayed the worse it collects. A dry, polite automatic message at 48 hours with a link to fix it resolves most of them without anyone making the awkward call.
• Students who quietly stop coming. Three unexplained absences in a row are almost never a coincidence — that's a cancellation that hasn't been announced yet. Getting flagged on the third absence instead of on the month-end invoice buys you a week to call and fix it. You make that call, not the agent. But the machine should be the one that tells you.

Minors, guardians, and what the agent shouldn't touch

If you teach children or teenagers — and nearly every school does — there's a layer here other sectors don't have. In Spain, a minor can only consent to the processing of their own personal data from the age of fourteen; below that you need consent from whoever holds parental responsibility (AEPD, the Spanish data protection authority).

In practice, that means concrete rules: the channel for a student under fourteen is the parent's mobile, not the kid's; enrolment data is collected from the guardian; and if a minor messages the school's WhatsApp, the agent redirects to the adult rather than handling admin with them. Add the obvious-but-awkward one: in separated families, who receives which notice is a field you need right, and an automated mistake there multiplies across every affected student. Review that list by hand before switching anything on.

Four more things worth ruling out on day one:

• A student's progress. "Is my son improving?" has no template answer. That goes to the teacher or coordinator, every time.
• Conflicts. A complaint about a teacher, a behaviour issue, an argument about an exam mark. Those escalate whole, with no automated reply in front of them.
• Financial exceptions. Sibling discounts, splitting a payment, freezing an enrolment because of a family situation. The agent can state the standard policy; it shouldn't decide the exception.
• The cancellation. When someone says they're leaving, that message is gold and goes straight to a human. It's the only chance you'll get to find out why.

Where to start, and how to know in a month

Don't open with full enrolment — it's the flashiest piece and the hardest to tune. Start with the boring, high-volume work, in this order: outbound notices first (class changes, make-ups, payment reminders), which are pure template and settle within days. Then the FAQs, with real timetables and real prices. Only once that's running, placement tests and per-group waiting lists.

To judge it, check four numbers at four weeks: how many enquiries were resolved without anyone on your team touching them; your average reply time on an enrolment enquiry; how many stalled enrolments a follow-up recovered; and how many freed-up seats were filled from a waiting list. That last one is usually the surprise.

If that shape fits, it's how our AI receptionist works: it answers on WhatsApp, web and email with your timetables and your prices, books by your rules, and escalates anything that needs human judgement. You approve, it executes.