The Student Is One Person. The Record Is Not.
Recruitment holds the enquiry, admissions holds the application, the faculty holds the results, and advancement holds the alumnus - four systems describing the same person at four points in their life. Nobody set out to build it that way. It is what happens when each department solves its own problem well, and the join between them is a spreadsheet somebody maintains by hand.
The whole learner lifecycle, on one platform.
Recruitment, admissions, enrolment, student success, parent communications and advancement each get their own view of the same learner record - so nothing is re-keyed between teams, and Agentforce works across all of it. Pick a stage to see what changes.
Every enquiry in one pipeline, not five spreadsheets.
Open days, education fairs, agent submissions, web forms and WhatsApp all land in the same Education Cloud pipeline, tagged by programme and intake. Recruitment officers see source, interest and follow-up status on one screen, and programme marketing journeys keep prospects warm between enquiry and application.
Applications that move themselves.
Document checklists, eligibility rules, conditional offers and committee routing run as configured logic rather than email chains. Faculty reviewers open a complete file, applicants see exactly what is outstanding, and every decision is time-stamped for internal and MQA reporting.
From offer accepted to first class, without the queue.
Digital acceptance, fee status, registration and orientation onboarding in one flow, with your SIS and finance system kept in step through Boomi. Registration week stops being a counter with a queue in front of it.
See a student slipping before the semester does.
Data 360 brings attendance, LMS activity, advising notes and fee status into one student view, so an early-alert flag reaches the right advisor with a recommended next step attached - not a report at the end of term.
Parents and staff, answered the first time.
One household record ties a parent to every child they have at the school - and to the siblings who came before them, or the alumni parent who did. So announcements, attendance, fees and consent go out per family rather than per class list. For universities, a service desk where students and staff get transcripts, fee balances, timetables and IT access resolved by an Agentforce assistant, with a human on anything sensitive.
Alumni who stay, donors who return.
The record that started as an enquiry becomes the alumni and giving record: constituent history, campaign and pledge management, event attendance and volunteering, all reportable in one place - so advancement stops rebuilding a database it already has.
Agents that carry the routine load
Agentforce answers programme enquiries around the clock, chases missing documents, and briefs advisors before a meeting - grounded in your own policies and scoped to what each user is allowed to see. Anything with consequence still goes to a person.
What changes when every team reads the same learner record.
More Of The Enquiries You Already Have Become Students
The leak is rarely lead volume - it is follow-up that arrives late and offers that go cold. When every enquiry, application and offer sits on one record, each has an owner and a next step, and offer holders are worked until they register.
Offers Out While They Are Deciding
Checklists, eligibility rules and committee routing run as configured logic, so decisions land in days rather than weeks.
Students Reached In Week Six
Attendance, LMS activity, advising notes and fee status combine into one early-alert view, while intervention still changes the outcome.
Staff Time Back On Students
Admin work moves off registry and recruitment teams onto configured process and AI agents, without adding headcount.
One Conversation Per Family
Parents, guardians and siblings sit on one household record, so communications go out per family, not per class list.
Alumni Giving From A Record You Already Own
The record that began as an enquiry becomes the alumni and giving record, so advancement segments by faculty, year and giving history instead of rebuilding a database.
Institutions running this are already seeing the return.
Regional delivery, phased scope, senior people throughout.
We have delivered Salesforce programmes across Malaysia and Indonesia where the stakes are compliance, reporting and public trust - the same conditions a registry works under. Education engagements start with one intake or one faculty, not the whole institution.
Frequently asked questions
Do we have to replace our student information system?+
No. Education Cloud sits above your existing SIS as the engagement and process layer, integrated through Integration Platform. Salesforce is releasing next-generation SIS capabilities in modules, so you can adopt registration, advising or student financials when they fit your roadmap rather than migrating everything at once.
Does this work for schools, or only universities?+
Both, with different scope. Universities and colleges typically start with recruitment, admissions and student success. International and private schools usually start with enquiry-to-enrolment and parent communications, then add a staff service desk.
Can it handle families with more than one child at the school?+
Yes. Students, parents, guardians and siblings sit on linked records under one household, so a parent with three children enrolled gets one consolidated view and one set of communications rather than three. Sibling history and alumni parents are visible on the same record, which also makes them straightforward to recognise in enrolment and advancement.
How is student data privacy and PDPA handled?+
Access is permissioned by role and every change is logged, with personal data handling configured to your institution’s PDPA obligations and internal policy. AI features run with guardrails and human review on anything student-facing that carries consequence.
Can it handle agent and counsellor-sourced recruitment?+
Yes. Agents, counsellors and partner institutions get their own submission channel, with attribution carried through to enrolment - so commission reporting and channel performance come out of the same system.
How long before we see something working?+
A first phase is typically scoped to one intake cycle. We work backwards from your intake deadline and put the highest-cost process live first, usually enquiry-to-offer.
What usually comes next.
Customer Engagement
Programme and intake journeys that nurture prospects properly.
Explore →Data & Integration
Connect SIS, LMS, finance and HR into one learner view.
Explore →AI & Automation
Agentforce assistants for students, parents and staff.
Explore →Customer Service
One service desk with SLAs across the institution.
Explore →