How to choose a language-school CRM: a practical checklist
Seven practical CRM checks for language schools: schedules, payments, payroll, access, reminders, migration and costs. A checklist for your trial.
In this article
Choose a language-school CRM by testing your own working week. One group reschedules a lesson, another pays for a subscription, a teacher checks homework and an administrator answers a new family’s question. Does the system help without making people enter the same information twice?
Before comparing services, list your essentials: perhaps groups by level, remaining paid lessons and payroll based on completed lessons. List possible future needs separately. This helps you compare the right plan, rather than the longest feature list.
1. Scheduling and attendance
Create a recurring lesson, move one session and replace its teacher. Check time-conflict warnings and what the student and administrator see after the change.
Then complete a lesson and mark attendance. Test presence, a chargeable absence and a non-chargeable absence under your school’s rules. A calendar entry is not yet a completed lesson.
Ask: “Which action uses a package lesson, and how do we correct an attendance mistake?”
2. Payments and correction history
Create an invoice, confirm payment and check the package balance. These describe different things: money due, money received and lessons available. A monthly subscription may follow different rules.
Check whether you can trace the original entry, the reason for a correction and the related invoice. Find out who may confirm payments and export records.
Ask: “How are refunds and incorrect payment entries handled?”
3. Teacher earnings and payouts
Test your actual rules: fixed rates, percentages, substitutes, cancellations and paid absences. Compare the calculation with a known example. Another school’s rules may not fit yours.
Accrued earnings and money actually paid to teachers should be understandable separately. Rescheduling a planned lesson does not by itself create earnings.
Ask: “Which changes affect earnings, and how do we check amounts already paid?”
4. Portals and access
Try the owner, administrator and teacher roles. Teachers need their groups and materials; access to school-wide finances should be decided separately.
If you teach children, check the parent portal: can a parent find schedules, assignments and invoices for several children? For an adult school, the student’s own portal may matter more.
Ask: “How do we limit a staff member’s access to the groups and records they need?”
5. Learning materials and reminders
Try a teacher’s daily tasks: prepare a lesson, assign homework, review an answer and reuse materials. Language schools may also need vocabulary practice between lessons. Not every team needs these tools to the same extent.
For reminders, check the channel, trigger conditions and frequency limits. A list of students missing lessons can help decide whom to contact; it cannot explain their reasons without a conversation.
Ask: “Which messages can we configure, and how do we prevent repeated notifications?”
6. Migration and support
Prepare a small file without unnecessary personal data to check the format first. Inspect column mapping, errors and duplicate handling. Agree separately on historical records and opening balances.
Do not judge migration only by upload speed: your team also needs to reconcile records and learn the workflow. Check how to get support and export your data when leaving the service.
Ask: “What imports automatically, what needs manual review, and who helps resolve discrepancies?”
7. The full cost of your workflow
Compare plans for your teacher and active-student counts. Check storage limits, branches, staff access, learning tools and fees for external services. Confirm billing currency and renewal terms.
Ask: “What will our required features cost now and after we add another teacher?”
Trial checklist
- Create one group and its recurring schedule.
- Test lesson completion, rescheduling and cancellation.
- Have the person responsible for records reconcile a payment, package balance and teacher earnings.
- Check staff, student and parent views where relevant.
- Try importing, exporting and contacting support.
- Calculate the price with the limits you need.
A system does not need every possible feature. It needs to support your essential work, with clear limitations before you pay.
If you are considering Mimiao, explore the website, plan comparison and public demo. The demo requires no registration and is read-only. You can test your own records and create lessons during a 14-day trial without a card.