Admissions
From inquiry to student, in one step.
What this covers
- 1A pipeline that is already the right shapeSix stages seeded per institute
- 2Course interest, captured earlyCourse interest panel on the admission
- 3The fee conversation, on the admissionFee summary at admission
- 4Convert to a student, onceOne dialog, not a re-entry
- 5Phone-first, because admissions is a phone jobCall actions from the row
- 6Fields an education team actually needsCourse or program and batch preference
In short
What does admissions do in RaivatEdu?
Admissions in RaivatEdu is a staged pipeline seeded per institute as Inquiry, Demo Class Scheduled, Demo Done, Fee Discussion, then Enrolled or Dropped. Each admission captures course interest and shows a fee summary, and a single dialog converts the admission into a student record with that context carried across. Phone-first actions sit on the row so a counselor can call straight from the list.
- seeded pipeline stages
- 6
- admission to student
- 1 step
- phone-first actions
- On the row
What admissions does today.
Every line here is a feature that exists in the product right now. Anything still being built is listed further down, on the same page.
01
A pipeline that is already the right shape
New institutes get six stages seeded for them: Inquiry, Demo Class Scheduled, Demo Done, Fee Discussion, then Enrolled or Dropped. Nobody has to design an admissions funnel before they can log their first inquiry.
- Six stages seeded per institute
- Stage progression on the record
- Dropped tracked as an outcome, not a deletion
02
Course interest, captured early
An inquiry that names a course is worth more than one that does not. Course interest is captured on the admission, so the counselor picking it up knows what the conversation is about.
- Course interest panel on the admission
- Carried into the student record on conversion
03
The fee conversation, on the admission
A fee summary sits on the admission itself, so the Fee Discussion stage is an actual conversation about actual numbers rather than a promise to send something later.
- Fee summary at admission
- Linked to the fee structure for the course
04
Convert to a student, once
This is the step that used to mean retyping a family's details into a second system. It is one dialog, and the course interest and fee summary come with it.
- One dialog, not a re-entry
- Course interest carried across
- Fee summary carried across
05
Phone-first, because admissions is a phone job
Actions sit on the row in the list. A counselor working a list of fresh inquiries calls, logs the outcome and moves the stage without opening three screens per student.
- Call actions from the row
- Stage change from the row
- Built for working a list, not a single record
06
Fields an education team actually needs
The custom fields are seeded too: course or program, batch preference, academic year, parent name, parent phone, scholarship eligible, fee amount, and the fields you need for staff and partner records.
- Course or program and batch preference
- Academic year
- Parent name and parent phone as standard fields
- Scholarship eligible
- Student, staff and partner entity types seeded
Where this stops
What admissions does not do.
We would rather you read this before you buy than discover it in week two. If something here is a requirement for you, tell us and we’ll be straight about the timeline.
Ask us about a gap- Parent name and parent phone are stored and callable as standard fields. There is no separate surface for a parent to log into.
- Counselor incentives and agent commissions are not available to education institutes, because commission accrual depends on a module that is switched off for this vertical.
FAQ
Admissions, answered plainly.
No. Six stages are seeded per institute, shaped for coaching: Inquiry, Demo Class Scheduled, Demo Done, Fee Discussion, then Enrolled or Dropped. You can work with them as they are from the first day.
You convert the admission into a student record from a single dialog. The course interest and the fee summary travel with it, so nobody retypes a family's details into a second place.
Yes. Parent name and parent phone are seeded custom fields on the record, so you can store and contact a parent today. There is no parent-facing surface, so treat those as fields your team uses, not a login you hand out.
Yes. Phone-first actions sit on the row, along with the stage change, because working a list of fresh inquiries by phone is the actual job.
Yes. A fee summary renders on the admission itself, linked to the structure for the course, so the fee discussion happens against real numbers.
No. Dropped is a stage, so the inquiry stays in your history and in your reporting rather than disappearing.
Next in the product
- Students & BatchesOne record per learner, documents attached, and batches with real seat limits.
- Enrollment & RenewalsEnroll onto a batch, then price it — plus renewal rules you set once.
- CommunicationWhatsApp, email, SMS and calls from the student record, on one timeline.
Your next student is already looking for you.
Give your admissions team one place to capture, connect and convert every opportunity.
Rather talk it through? Request a callback or talk to sales.
- 30-minute walkthrough
- Your workflow, not a script
- No card required