Platform
Retento checks in with every consenting student by SMS, works out what they need, answers what it can from your own services, and brings in a person when it matters. Nothing written by AI reaches a student until a member of your team approves it.
The support loop
01
Check-ins by SMS from a named persona your institution chooses. The AI is always disclosed, and students opt in first.
02
Each reply is read for what the student needs, across five support areas. Anything about safety goes straight to a person.
03
Everyday questions are answered from your own approved help articles and services, in your voice.
04
Risk builds from what students say and how they engage over time, never from grades, fees or attendance.
05
When a student needs a person, the case goes to the right member of your team with the whole conversation.
Five support areas
Every conversation maps to one of five areas. Fees, attendance, enrolment and census dates stay with your student systems; if a student raises one, Retento points them to the right team.
Stress, sleep, health and mental wellbeing.
Workload, study skills and getting back on track.
Rent, food, work hours and emergency help.
Belonging, isolation, clubs and peer support.
Placements, part-time work and life after study.
The Retento Workspace
One queue of students who need a person, sorted by urgency. AI drafts a reply; a case manager edits and approves it.
Safety disclosures, students waiting past your response target, and escalations with no outcome yet, so nothing sits unseen.
Check-ins to a group of students, approved before sending. Quiet hours and a weekly limit protect students from too many messages.
Reach, response and outcomes by support area, plus the common themes students raise, shown only when enough students share them.
Roles, caseloads, handovers when someone leaves, your safety reply, support hours and connections to your systems.
Two ways to run it
Your case managers work cases in the Retento Workspace: queue, approvals, notes and outcomes in one place. Suits teams without a case management system.
Escalations go into the support system you already run, such as ServiceNow, Salesforce, Dynamics, Zendesk or email, with a minimum set of fields and a return path for the outcome.
What you share
Minimum fields only. Retento never reads grades, fees, attendance or enrolment records.
Engagement layer

Australian-hosted
What flows back
Every escalation has a return path, so its outcome comes back and none is dropped.
Illustrative. Named systems are examples of what Australian institutions run; Retento works with any of them by file, webhook or email.
Scale
Every student who has opted in receives a check-in each cycle.
Two-way conversation in plain language, no portal or appointment.
Answers, links and referrals handled inside the conversation.
Prioritised, with full context, to the right case manager.
Illustrative volumes for a 12,000-student institution, shown to explain the model.
What that means for your team
Coverage scales with enrolment; case-manager load does not.
Reporting
Retention insights
Semester 2 · all students · updated daily
Cohort contacted
98.2%
+4.1 pts vs last cycle
Response rate
45.1%
+6.3 pts
Resolved at first contact
72.4%
+2.8 pts
Median time to human
3h 12m
−41 min
Students supported per week
Concerns by support area
Aggregate evidence of reach, response and outcomes, ready for the completion and equity reporting your executive already prepares. Small numbers are hidden to protect privacy.
Illustrative dashboard. Figures are examples, not client results.
Book a 30-minute executive briefing, or explore the Workspace with synthetic students in our demo.