# Admissions & applicant journey

Use admissions & applicant journey in the school workspace. Connect family enquiries, counsellor follow-ups, reviewed applications and student admission.

Category: School office
Guide: https://avkul.in/docs/guides/screen-school-admissions/
Guided sample demo: https://avkul.in/docs/demo/screen-school-admissions/
Snapshot: 11 October 2026

## Features

- Start application
- Log call
- Review application
- Schedule visit
- Save guardian
- Save visit
- Create student & guardian
- Preview student fee
- Queue
- Leads due a follow-up, oldest overdue first
- Pipeline by stage and by source, with conversion
- List
- History
- Record a contact attempt and move the lead on

## Access and setup

Intended access: Assigned account with the required permissions
- A school account with the permissions shown below.
- Choose the relevant school, academic session or child before working.

Permission keys: admission:view, admission:update, admission:create, admission:manage

## Workflow

1. Record or select an enquiry and log the next follow-up.
2. Open a linked application and review guardian details.
3. Receive and verify required documents and review readiness.
4. Select session, class and section before admitting the applicant.

## Fields and controls

- Student name
- Parent name
- Phone
- Guardian email
- Enquiry source
- Class applying
- Include leads never scheduled
- Find an applicant
- Guardian name
- Email for parent portal
- Relationship
- Visit date and time

## Current limits

- Application access links and parent invitations are separate from an existing family login. Admission is subject to readiness and school/session ownership.

## Actual application access

- https://avkul.in/en/school/admissions

## API reference

- GET /api/v1/admissions/work-queue — Queue; admission:view
- GET /api/v1/admissions/enquiries/due — Leads due a follow-up, oldest overdue first; admission:view
- GET /api/v1/admissions/enquiries/funnel — Pipeline by stage and by source, with conversion; admission:view
- GET /api/v1/admissions/enquiries — List; admission:view
- GET /api/v1/admissions/enquiries/:id/follow-ups — History; admission:view
- POST /api/v1/admissions/enquiries/:id/follow-ups — Record a contact attempt and move the lead on; admission:update
- POST /api/v1/admissions/enquiries — Create; admission:create
- PATCH /api/v1/admissions/enquiries/:id — Update; admission:update
- DELETE /api/v1/admissions/enquiries/:id — Remove; admission:update
- GET /api/v1/admissions/applications — List; admission:view
- GET /api/v1/admissions/applications/funnel — Where applicants are, and how many converted; admission:view
- POST /api/v1/admissions/applications — Open an application, optionally from an enquiry; admission:create
- POST /api/v1/admissions/applications/:id/advance — Move the application one legal step; admission:manage
- GET /api/v1/admissions/applications/:id/journey — Get; admission:view

## Demo access

No login is required for the guided sample demo. Its fictional records and actions stay in this browser tab; they do not modify ERP records or send messages/payments. An assigned account is required for the actual ERP links.

Source inventory checked on 11 October 2026. This source inventory is not a certification of every external provider or device flow.