Use rules for work that repeats.
A class reminder needs the correct time and recipient, not a language model. An overdue-fee reminder should stop when payment is recorded.
Start with schedules, attendance, payment status, and message history in one workflow. Then every automation can act on a reliable source.
Five automations to start with.
- Lead follow-up queue
- Flag enquiries without a reply, trial booking, or next action after your chosen interval.
- Missed trial follow-up
- Prepare a considerate follow-up and a rescheduling link after a missed trial.
- Make-up slot matching
- Offer valid slots based on teacher availability, capacity, location, and the student’s schedule.
- Fee reminders
- Remind students only while an invoice is unpaid. Stop as soon as you record payment, including UPI, Pix, or PromptPay.
- Daily operations digest
- Review today’s sessions, unpaid fees, untouched leads, and schedule changes in one short list.
Give AI the language work.
Use AI when a draft or summary saves time. Review the output before it reaches a parent or changes a class.
- Draft, do not send. Prepare replies for enquiries, missed trials, overdue fees, and cancellations. Let the teacher approve the message.
- Summarize, do not decide. Turn lead notes and message history into a short handover for another teacher or admin.
- Classify, then review. Organize enquiries by subject, age range, location, or urgency so the next reply is easier to find.
- Explain, do not fabricate. Answer from approved schedules, fees, and policies. Escalate questions the source does not cover.
Keep people in control.
Do not let AI invent availability or make sensitive student decisions. Share only the data needed for the task and keep an audit trail.
ClassOps connects leads, schedules, attendance, payments, and make-ups. Its AI assistant asks for confirmation before making changes.