Universities, schools & training
Enrolment season, answered.
Student services face the same concentration problem every year: a term of enquiries compressed into three weeks, on topics that are almost entirely procedural, from people making a decision under a deadline.
An illustrative reference architecture, not a customer
case study. No organisation is named and no deployment is described - this is
what the layers look like for a education organisation,
so you can map it onto your own estate.
Channelswhere the conversation starts
Inbound numberspublished lines
SIP / contact centreexisting estate
Outboundcampaigns and callbacks
In-appbrowser WebRTC
▼
VoiceKernelthe agentic voice layer
Conversationagent, voice, turn taking
Knowledge groundinganswers with citations
Tool callsreads and writes back
Transferto a human, with context
Tenant isolationownership registry
Audit and erasureper call, per mutation
▼
Integrationyour boundary, your rules
REST + typed SDKscoped API keys
Signed webhooksretried, replayable
Live event streamSSE
▼
Educationyour systems of record
Student managementenrolment, results, fees
LMScourse and timetable data
Admissionsapplications and offers
Financefee schedules and plans
CRMprospect and student contact
Only the bottom layer is specific to education. The
three above it are identical in every deployment, which is the point: the
voice layer does not need to know what industry it is in, only which systems
it is allowed to reach and what it may say.
What it changes
Mechanisms, not projections. Each of these follows from something structural
about the work, so you can check whether it holds for your own queues.
Peak season stops degrading serviceThe enquiry spike is absorbed rather than queued, at the exact moment a prospective student is comparing institutions.
International students get their own hoursEnquiries arrive across every timezone; coverage no longer depends on local working hours.
Staff move to the conversations that need judgementAdvisors stop quoting fee deadlines and start handling welfare and course advice.
Retention outreach becomes feasibleContacting every disengaged student is a volume problem, not a difficulty problem.
What the agent actually does
Enrolment and admissions statusAnswer where an application sits, what is outstanding, and what the deadline actually is.
Timetable, results and feesVerify the student, answer from the system of record, and set up a payment plan where one applies.
Attendance and retention outreachProactive contact for students who have stopped attending, with a human transfer the moment support is needed.
What keeps it deployable
Student privacyVerification before any result or fee balance is spoken.
Welfare escalationDistress detected in retention calls transfers immediately, and the boundary is enforced by tool availability.
Records retentionTranscripts held to your policy, in your systems.
Enrolment enquiries concentrate a year of contact into a few weeks, against a staffing level set for the average.
NextRead the source
Everything above is in the open-source Community edition. Nothing on
this page needs a licence.
NextRun it yourself
Point it at your provider account and put one queue through it before
you talk to anybody.
NextThen buy the guarantees
An Enterprise agreement adds the SLA and the
support contract when it carries real volume.