Automations

Automations eliminate the most tedious recurring tasks: reminding students to top up their balance, alerting an admin about missed lessons, assigning follow-up tasks to the right person. Configure a rule once — the system handles it from then on.

Ready-made recipes

To avoid starting from scratch, the Automations → Gallery section includes ~12 ready-made recipes. Each one is enabled with a single toggle:

Recipe	What it does
2 lessons remaining	Reminds the student to recharge their balance
2 consecutive absences	Notifies the administrator
Homework overdue	Reminds the student to submit
Critical churn risk	Creates a task for the manager to call
New invoice	Sends the student or parents a payment link
Trial lesson tomorrow	Sends the lead a reminder

Ready-made recipes are the fastest way to start — enable the ones you need and see results the same day.

Above the gallery, a summary strip always shows how many recipes are enabled and how many times they’ve fired in the last 30 days, and an “All / Enabled” filter narrows the list down to what’s already running.

On your first visit, a short guided tour of the gallery runs automatically — it walks through the summary strip, the first recipe, the filter, and the custom rule builder. If you skip it or want to see it again, a callout above the page lets you relaunch it any time.

Rule builder

For custom rules, the builder uses three steps:

Step 1. When (trigger)

The trigger is the event that fires the rule. Examples:

• Student misses a lesson.
• Balance drops below N lessons.
• Invoice is overdue by more than N days.
• Homework deadline passes without a submission.
• Student’s risk score changes.

Step 2. If (conditions)

Conditions narrow down who the rule applies to. Examples:

• Consecutive absences ≥ 2.
• Student age ≤ 18 (notify parents instead).
• Student tag = “VIP”.

Conditions can be combined with AND/OR logic.

Step 3. Do (action)

The action is what the system executes. Available actions:

• Notify the student — in-app message, email, or Telegram.
• Notify parents — same channels, sent to the student’s parent accounts.
• Notify a staff member — a specific admin or manager.
• Create a task — an action card in the task list, with full context (who, what, when).

Plain-language preview

Below the builder, a sentence preview always shows what the rule will do in plain English — for example: “When a student misses a lesson for the second time in a row — send a message to Elena (manager) and create a task ‘Call student’.”

Read it aloud: if it sounds right, the rule is configured correctly.

Anti-spam

Every rule has a required “No more than once every N days” field per student. Without this limit, a single rule could fire dozens of times in a week if the situation doesn’t change. Minimum is 1 day; 7 days is recommended for most reminder-type rules.

Notification channels

• In-app — appears in the Mimiao notification centre.
• Email — sent to the student’s, parents’, or staff member’s address.
• Telegram — if the student or parents have connected the school’s Telegram bot.

Execution history

Every time a rule fires, it is recorded in Automations → History: which rule, for whom, when, what was sent or created, and if it was skipped — why (e.g., anti-spam cooldown, missing email address).

This lets you confirm that automations are actually working, not just switched on.

---

Automations react to risk signals — but to know which students need attention, you need the churn-risk zone.