Step 2 of 6 · Student intake and lifecycle
Try this experience Student inquiries
Capture family interest, desired placement, contact details, and follow-up status before creating a student record.
Student inquiries in LiveSchools365 Admissions
Student inquiries is a Admissions workflow in the Student lifecycle area of LiveSchools365 school management software. Capture family interest, desired placement, contact details, and follow-up status before creating a student record. Schools use it so A documented admission lifecycle with traceable decisions, complete student records, and controlled placement changes.
Move prospective learners from first inquiry through registration, record verification, promotion, and transfer. The people who typically work here are Admissions team, Administrator, Principal. The rest of the module stays one click away, so an inquiry, register, invoice, or stock movement does not have to be re-typed into another product.
What this workflow changes
- Prospect capture This sits inside Admissions rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- Follow-up status tracking This sits inside Admissions rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
- One-click conversion to registration This sits inside Admissions rather than a separate spreadsheet, which keeps the audit trail on the same student, staff, or item record.
How it fits the rest of Admissions
Open these related Admissions guides when you want the step before or after Student inquiries:
- Admissions dashboard — Prioritize new inquiries, overdue follow-up, qualified applicants, and the next admission task.
- Student registration — Create the authoritative student, family, placement, health, and document record after an inquiry qualifies.
- Student records — Find registered students, filter by placement, review details, edit records, and open the printable admission form.
- Printed admission form — Produce the official admission form for review, signature, filing, or handover after registration details are verified.
- Student promotions — Advance an enrolled student into the next academic year, campus, grade, and section while preserving placement history.
- Student transfers — Move an active student between campuses, grades, or sections without losing the previous enrolment context.
How schools evaluate this screen
During a demonstration or trial, Admissions team, Administrator, Principal should complete one realistic example: a new inquiry, a section register, a fee receipt, a notice, or a stock issue, depending on the module. Then confirm that the same record appears on the dashboard, the related report, and the next workflow. That is the test of a school ERP: one operational picture instead of parallel files.
Trend Developers can walk this exact screen against your admission, attendance, exam, or fee process. You can also start a 14-day trial and use the matching live form after sign-in.
All Admissions workflows · Start a trial · View pricing · Request a demonstration
Guide depth
Interface
Fields, controls, and effects
Use this reference to understand what each area accepts and what it changes.
Inquiry dateDate · Input
- Purpose
- Record when the family first contacted the school.
- Rules
- Required; use the actual contact date.
- Application effect
- Starts inquiry aging and follow-up measurement.
Parent contactName, phone and email · Input
- Purpose
- Identify the responsible adult and provide channels for follow-up.
- Rules
- Parent name and phone are required; verify the number before saving.
- Application effect
- Supports calls, messages, and later guardian setup.
Student nameText · Input
- Purpose
- Identify the prospective learner.
- Rules
- Required; use the name supplied by the family.
- Application effect
- Carries into registration when converted.
Desired placementCampus, grade and section selects · Input
- Purpose
- Record where the family wants the student enrolled.
- Rules
- Campus and grade are required; grade and section options depend on the selected campus.
- Application effect
- Directs availability checks and pre-fills registration context.
StatusSelect · Input
- Purpose
- Progress the inquiry through New, Open, Contacted, Qualified, or Closed.
- Rules
- Use Qualified only when the family is ready for registration.
- Application effect
- Updates dashboard totals and the officer action queue.
MessageTextarea · Input
- Purpose
- Keep the family's request or follow-up context with the inquiry.
- Rules
- Record useful operational facts and avoid unnecessary sensitive data.
- Application effect
- Gives the next officer context for contact.
Row actionsEdit, view, convert and delete commands · Input and output
- Purpose
- Correct details, inspect the inquiry, or convert a qualified prospect.
- Rules
- Confirm the selected family before conversion or deletion.
- Application effect
- Conversion opens registration with inquiry context linked.