Recruitment & Admissions
Admissions on the record the registrar keeps.
Salesforce is well established for recruiting and admissions. What matters is where the funnel writes: on one platform, every prospect, application and decision lands on the same student record the rest of the institution runs on.
Functional scope
Prospect to enrolled, on one record.
The admissions cycle is a sequence of records about one person. Here it is a sequence of updates to one record.
- Prospect management
- From first contact, the person is on the student record — not in a separate list waiting to be matched later.
- Events and visits
- Open days, campus visits, school events — attendance recorded against the person, not a spreadsheet.
- Application intake and review
- Applications, supporting documents and review workflow held in one place.
- Decisions and offers
- Decision workflow and offer communication, with the full history retained on the record.
- Deposit through enrollment
- The steps between an accepted offer and an enrolled student, tracked to done.
- Funnel reporting
- The pipeline by stage, term and program, read from the record rather than assembled from exports.
Our approach
Admissions operations is a specialism.
The questions that decide the build are operational, and we answer them from experience.
- People who have run a cycle
- Our team has worked inside admissions offices. You will not spend the first month explaining how yours works.
- Built for concurrent cycles
- Rolling intakes, several programs, separate calendars. Parallel cycles run on one record, each with its own requirements.
- Standalone or alongside the SIS
- Recruitment and admissions ships on its own. Build the student record on Salesforce later and everything you have already built still fits.
- A clear line with the student system
- We scope admissions tightly so it lands fast, and we know precisely what sits on the other side of that line, because we build that too.
What it runs on
The stack, named.
- Education Cloud, Recruitment & Admissions
- Individual Application, Application Review and Application Decision as native objects, on Person Accounts.
- Experience Cloud
- An applicant portal with live status, requirements and next steps.
- OmniStudio / Screen Flows
- Conditional applications that adapt to the program and the applicant.
- Marketing Cloud
- Nurture and journeys built on the same record as the application.
- Feedback Management
- Recommendation letters collected in-platform, on the file.
- Your student system
- Integrated to Banner, Colleague, PowerCampus, Jenzabar or Anthology, alongside Common App and standardized test score files.
AI
Agents doing admissions work today.
- Document checklist verification
- An agent classifies every upload as it arrives — ID, transcript, essay — and tells the applicant immediately when a file is blurry or in the wrong slot, instead of a counselor finding it a week later.
- Inbox triage
- Admissions inboxes get routed by intent, with mixed-intent messages ordered by priority, so the file that needs a human reaches one first.
- Student navigator
- A support agent that knows who it is talking to, handles routine changes on the spot, and escalates the sensitive ones into a case with the full transcript attached.
- Transfer credit in minutes
- TondroAI Extract evaluates transcripts and writes credit onto the record — the answer a rolling transfer applicant is waiting for.
Implementation
Six phases. Thirty-six weeks to a live cycle.
- Align · 2 weeks
- Stakeholders, decision rights, and what a successful cycle looks like in your terms.
- Envision · 6 weeks
- Current state, cycles and calendars, integration scope.
- Iterate · 14 weeks
- Data model, application, review workflow, communications, portal and SIS integration, built in working increments.
- Validate · 6 weeks
- Tested against a real cycle with your admissions team.
- Onboard · 6 weeks
- Cutover, training and a full application-to-decision round.
- Hypercare · 2 weeks
- The team that built it stays on daily through the first live weeks.
Rolling admissions changes the cutover, not the build.
There is no quiet season to launch into, so we move one population at a time — a single intake goes live and runs a complete application-to-decision round before the next follows. Your team owns the platform from day one, and we make sure they can run it.
Insights & events
Admissions, in practice.
Case study · Nov 11, 2025
Flagler College: A Case Study in Resilience and Partnership
How Flagler College restarted a failed Salesforce Admissions implementation with a partner who already understood admissions operations.
Explainer · Nov 1, 2024
What in the Education Cloud: Applicant Portal
Education Cloud ships one portal for every constituent — here is why separate applicant, student and alumni portals are usually easier to live with.
Start here
Bring this cycle’s funnel.
Where prospects arrive, where applications live, and where things get re-keyed — the first conversation maps your cycle as it actually runs, then looks at what one record changes.