Placement test booking
Students pick a test date and time, see the room or online link and receive a reminder before the test.
Language school students want to book a placement test, move up a level or book a makeup conversation class without a long email chain. We design a customer self-service app for language schools that handles those requests, the reminders and the attendance records in one place.
A language school receives a steady flow of small requests. A student asks to move from the A2 class to B1 after a placement test, a parent wants a Saturday slot for a teenager, and a learner needs a letter confirming attendance for a visa application. Each request arrives by email, a messaging app or a voicemail, and each needs someone to check a timetable before replying.
The breaks come when the timetable changes. A tutor takes leave, a group is merged, and the students in the affected class have to be told by hand. Records of who attended which session often sit in a separate sheet, so an attendance letter takes an afternoon to produce. The self-service app should remove the manual checks that cause those delays.
The owner will ask whether the school's front office gets fewer routine emails once the app is live. Record how many level change, makeup and attendance letter requests arrive each week before launch. That count is the baseline for judging whether the app is doing its job.
A customer experience lead will test the edge cases: a student who is already in a full class, a placement test that clashes with a work shift, or a learner who wants a refund after moving countries. Each case should end with a clear status and a note the staff can act on, rather than a request that waits in an inbox.
Start with the requests students make every week: placement test bookings, level changes, makeup conversation classes and attendance letters. Each lands in one list with the learner's current level, class and teacher, so staff can approve or decline quickly and the learner can see the outcome.
Homework portals, grammar exercises and video libraries can wait. Those need content production and their own quality checks, and they do not reduce the request load the school carries now. Once the request queue is running well, the school can decide which learning content is worth building next.
Students pick a test date and time, see the room or online link and receive a reminder before the test.
Learners ask to move up or down a level, and the academic lead's decision appears with a short note.
Missed sessions are rebooked into a conversation class with a matching level, shown in local time.
A letter confirming enrolment and attendance is produced from the verified record and sent securely.
Each request shows whether it is pending, approved or declined, with the reason written by staff.
Language schools have strong seasons. September and January bring new intakes, summer runs intensive courses, and exam seasons for English tests push up the number of placement and practice requests. Staff who handle those peaks alone tend to fall behind on replies in exactly the weeks when students are most anxious.
The app should open extra placement slots automatically when a period fills, and it should show students a realistic reply time during busy weeks. For online classes, the timetable needs to display time zones clearly, since a learner in another country may book a session that lands at an unexpected hour.
Corporate groups add a different rhythm. A company booking lessons for a team of twelve wants one invoice, a block of sessions and a named coordinator, so the app should let an employer request a block and see how many hours remain.
Start with the level structure, including the placement criteria for each level and the lesson length. Add the timetable with tutors, rooms and online links, plus the policy for makeup classes and the price list for private lessons and corporate groups. Those rules decide what a student is allowed to request, so they must be right before launch.
Also provide the attendance letter template, the wording used with families and the rules for any students on a student visa. Confirm who approves level changes and who may see personal records. Name one person who signs off copy and one who approves prices, so the build keeps moving.
A common error is letting students book any level they like. Placement results should decide the options a student sees, otherwise a learner can book a class far above their ability and leave within a week. Build the rule into the booking flow from the start.
Another is treating attendance as a footnote. Attendance drives attendance letters, visa paperwork and certificates, so it has to be recorded at the session, not reconstructed later. A school that enrols international students should also keep those records consistent with its certification duties.
Yes. A message route stays open for anything outside the request types, and staff can answer it from the same screen. Routine requests go through the app so the front office is not handling them one by one.
The letter is built from the attendance record the school already keeps, so it matches the official documents. The school's designated staff member approves each letter before it is released.
A parent creates the account and gives verifiable consent first. The app then stores only the name, age band, level and class details the school needs to run the lessons.
Yes, through a PCI DSS compliant card processor, so card numbers never reach the school's own systems. Invoices and receipts are issued in line with the price list you set.
Share your level structure and timetable, and we will show how a customer app would handle placement tests and attendance letters, with a scope and price.