Platform

Built like infrastructure.

Identity, roles, documents, chat, scheduling, workflow and an audit chain that no one can quietly edit.

Identity

One profile per person.

Mobile and email are both verified and both unique. The first sign-up creates the ID, and every later application reuses it.

Step 1
Email verifiedOTP sent to anaya@example.com✓ Verified
Step 2
Mobile verifiedOTP sent to +91 98xxx xx210✓ Verified
Step 3
Unique ID issuedOne profile for every applicationVA-27-004182
Later
Same mobile used againBlocked. The existing profile is opened instead.No duplicate
  • A second sign-up with the same email or mobile is blocked
  • A near match, such as the same mobile with a different name, goes to a merge queue for staff
  • Changing email or mobile needs an OTP on the old and the new one, and is logged
Roles and documents

Pick a role to see what it can open.

Scope also limits by programme, intake, campus and assignment. A reviewer sees only the applications assigned to them.

Chat

Two kinds of conversation, kept apart.

Applicants talk to staff in threads tied to their application. Staff talk to each other in internal channels that applicants can never see.

Applicant thread · Anaya D.Visible to the applicant
Hello, my marksheet upload failed. Can I send it again?
Of course. Please upload it under Documents and we will check it today.
Your interview is booked for Saturday 11:00. A reminder will come by WhatsApp.
Staff channel · B.Tech CSE🔒 Staff only
Anaya's marks are verified. Over to Prof. Iyer for the department round.
Noted. I have assigned Dr. Khan as the second reviewer.
@Admin please check her category certificate again.
  • Mentions, attachments and read receipts, with attachments limited by the same document roles
  • Retention rules, export for disputes and moderation by the admin
  • Every message is an entry in the audit chain
Chatbots

Ask the university. Ask the rulebook.

Applicants ask about courses. Staff ask about rules and ordinances. Each bot answers only from documents your institution has approved, and shows the source.

Applicant assistant · course informationApplicants
Ask me something. Pick a question below.
Staff assistant · rules and ordinancesStaff
Ask me something. Pick a question below.

Example answers and clause numbers. In the product the bots answer only from the documents you upload and approve, say so when they do not know, and hand over to a person. They never make or change a decision.

  • Answers cite the document and clause, so staff and applicants can check them
  • Questions the bot cannot answer go to a counsellor or the admissions office
  • Conversations are logged and follow the same privacy and retention rules as every other message
Scheduling

Bookings that cannot clash.

Scheduling · Saturday12 of 16 booked
10:0010:3011:0011:3012:0014:0014:3015:00
WhoCounsellor Rao, interview panel B
Conflict checkNo double booking for staff or room
RemindersEmail and WhatsApp, a day before and 2 hours before
RescheduleOne tap, with the old slot released
  • Applicants book campus visits, counsellor calls, tests and interviews from live calendars
  • Capacity and conflict checks for staff and rooms
  • Reminders on email and WhatsApp, with no-shows followed up
  • Each booking is tied to the profile and logged
Workflow engine

Stages, owners and deadlines.

ScreeningCounsellor or admissions teamEligibility check against programme rules. Fails go to a reason list.2 days
DocumentsVerifierEach document accepted or returned with a reason. The applicant is told at once.3 days
Department reviewOne or many reviewersRubric scores and comments. A decision needs your set number of sign-offs.5 days
CommitteeChair and membersFinal say if reviewers disagree. Reservations and quotas applied by rule.3 days
DecisionAdminOffer, waitlist or reject, with the reason recorded and the letter generated.1 day
  • Admin assigns one or many staff to an application, by rule or by hand
  • Reviewers can be reassigned if someone is away, and conflicts of interest are blocked
  • Late stages escalate to the admissions head
Audit chain

Each entry contains the one before it.

Digital footprints such as logins, document views, downloads, messages, decisions, payments and settings changes are signed and chained. Edit any past entry and every hash after it stops matching.

What is recordedWho did what, to which record, when, and from which session.
How it is checkedVerification recomputes the chain. A break is reported with the exact entry.
What it does not claimIt makes tampering visible. It is not a promise that nothing can ever go wrong, so access controls and encryption still do the front-line work.

Example values are illustrative.

Connects to

Your gateway, channels and systems.

PaymentsUPI, cards, net banking and offline challan, through your payment gateway, with daily reconciliation.
MessagingEmail, WhatsApp Business and SMS with approved templates and delivery status. SMS uses your DLT registration.
Rank filesImport CET, JEE and similar files with a column map for each exam.
DocumentsUpload, or fetch from DigiLocker with the applicant's consent where your institution is registered.
Your systemsWebhooks, an API and file export to your student information system, ERP, LMS and accounts.

Tell us how your admissions run today.

We will set up your programmes, seat matrix, fees and letters for the demo.