Every applicant and every student leaves a trail in your systems. Act on it the day it appears.
An application saved at the documents step and never submitted. A deposit paid, then three weeks of silence. Two weeks with no lesson opened. Most institutions record these in the admissions system, the fee ledger and the LMS. Here each one starts a journey on the channel the student or the parent answers, checks your records first, and stops the moment they act.
The moments that matter.
Each one is a moment the platform can act on. Here is what it does.
- 01Session rule
An application saved at the documents step, never submitted.
A session rule sends one WhatsApp with a link back to the step and the deadline your system holds, and stops when they submit.
- 02Segment entry
A deposit paid, then three weeks of silence.
The student enters a segment you defined and gets one message with the next step, from admissions, not a bulletin. A reply reaches a person.
- 03Wait until date
A fee still unpaid three days after the due date.
The journey waits until the date your ledger holds, sends Pay now to the payer, and escalates by channel until your ledger says paid.
- 04One message, then a person
Two weeks with no lesson opened.
One push and Inbox message to pick up where they left off. If no lesson opens in three days, a WhatsApp from the tutor, then a task in your system.
- 05Parent answers
Attendance below the line you set, for the second week.
A consent check for the parent, then one WhatsApp with two buttons, Call me and I am aware. The answer is written back and the tutor gets the task.
- 06Your catalogue decides
The final module completed.
Your catalogue confirms the next course is open and not yet taken, and one WhatsApp offers it with a tap to enrol.
- 07Your billing decides
A plan ending in thirty days, with a lesson opened this week.
Your billing system confirms the plan and the early-bird price, and one WhatsApp offers the renewal, once, while they are still learning.
- 08Your system confirms
A mock exam scored below the pass line.
Your system confirms no session is booked, then one WhatsApp offers tutoring with the open slots to pick from.
- 09Consent per contact
A timetable change published for one programme.
Push and Inbox to students on the app, SMS to parents per consent, and SMS to any student who has not read it.
Signals from four places, one student record.
Your admissions system, LMS and fee ledger send the application status, the deposit, the module completed, the attendance mark and the due date by API. The app and the portal send what students do, and the session itself. The reminders you already send become events. Every reply, read and tap comes back to the same record, whether it came from the student or the parent.
Your reminders are already behaviour data.
A template declares which of its fields count as an event. The fee reminder you send today becomes a fee-due event with amount, programme and due date, with no SDK and no release. Behaviour history starts on day one, from the traffic you already send.
Catch the student who is leaving quietly.
Nobody withdraws. The portal logins stop, the lessons go unopened, the attendance slips a day at a time, the deposit is paid and then nothing. Segments on your own definitions catch each one, RFM scores logins and lesson completions on the windows you set, and entering a segment starts a journey. One message, on their channel, then a person.
Offer the next course the day the last one ends.
The final module completed starts the journey. It asks your catalogue whether the next course in the track is open and not yet taken, and only then sends one WhatsApp with Enrol or Not now. A tap goes to your system to enrol them. No sales call, no term-start campaign, no offer for a course they already hold.
Sell the next step on the signal, not the term calendar.
A mock exam below the pass line is a tutoring session. A plan ending in thirty days with a lesson opened this week is an early-bird renewal. Three courses completed in one track is the certificate. Each signal checks your system for what the student already holds and what is open, then sends one offer on the channel they answer. If they do not act, the journey ends. Nobody gets the same offer twice.
Turn a stalled application into a submitted one.
The form saved at the documents step, the upload never started, the session over. A session rule sends one WhatsApp with a link back to that step and the deadline your admissions system holds. Consent checked first, one reminder before the deadline, and the journey stops when the application is submitted.
See where the portal and the app lose people.
The SDK and the web tracker capture what applicants and students do. Funnels show where the application, the first login and the first lesson stop. A session rule turns what did not happen into a trigger: a lesson opened and the quiz never attempted, a fee reminder read and the payment never started. Ask the question in plain language and get the answer this session, not a ticket to the data team.
Onboard the first week with Stories you can measure.
A text says one thing and reports one delivery. A Story in your app, on your domain or inside an email walks the student through collecting the ID, finding the timetable and paying the fee, page by page, and reports views, completion, the drop between pages, poll answers and form submissions. The first week, a course explainer, an exam checklist: built in the builder, withdrawn in one action, no release.
Parents and students, separately.
Consent per channel, per contact, with secondary identifiers, so a parent's number and a student's app are one relationship, correctly addressed. The fee reminder goes to the payer, the lesson nudge to the student, the absence to both, and each journey checks consent before it sends.
Remind on the real date, then escalate.
A fee journey waits until the due date your ledger holds, sends Pay now to the payer, stops the moment your ledger says paid, and escalates on the channel that gets answered if it does not. A local-time send lands at a sensible hour for every timezone in the cohort.
Reach the parent about an absence, and keep the answer.
Call the parent, escalate to WhatsApp, then SMS, capture the keypad answer and branch on it. A branch per response, a deadline per branch, a path for silence, and the answer written back to your records. The same shape serves an unexplained absence and a safeguarding check.
Push your data protection officer can approve.
Results, fee notices and absence alerts never transit a third-party network. Each message is encrypted to a key held only on the student's or the parent's device. Device-targeted, not end-to-end, and the platform says so.
Data that stays on campus.
Student records in their own databases. A dedicated or in-country installation with high-availability pairs and a separate disaster-recovery site, for the institution that cannot send minors' data abroad.
A journey you could ship in the pilot.
Final module completed (your LMS) → next course open? already enrolled? your catalogue → WhatsApp: Enrol / Not now → tap: your system enrols them → confirmation with the start date → no tap: silence.
Playbooks you can configure.
Ten journeys an institution can configure, from the next course on the day of completion to the fee reminder on the real date, each drawn as it runs in the builder.
- 01Offer the next course the day the last one ends.
- 02Offer the early-bird renewal while they are still learning.
- 03Finish the application that stopped at the documents step.
- 04Catch the deposit that went quiet.
- 05Reach the student who stopped opening lessons.
- 06Act on attendance the week it falls.
- 07Turn a low mock score into a tutoring session.
- 08Remind the fee on the real date, then escalate.
- 09Tell students and parents about a change, each their way.
- 10Welcome the accepted with a Story, and catch the melt.
These are configurations you build in the pilot, not documented deployments.