From Lead to Alumni.
One Platform. Every Institution. Every Stage.
Whether you run admissions on your Lead CRM (e.g. Merritto, LeadSquared), SAMARTH, UCAS, a basic web form, or purely on WhatsApp — GUARDIAN unifies your entire student lifecycle from first enquiry to graduation, with compliance built in at every step.
GUARDIAN Across the Full Student Lifecycle
From the first enquiry through enrolment, fees and everyday student questions — GUARDIAN connects your existing systems, automates the admin, and keeps your team in the loop at every decision point.
Engine
Engine
Layer
Oversight
Which best describes your institution?
Choose yours. In Step 2, the problems that apply to you are marked ✓ — and Step 3 shows how GUARDIAN connects to the systems you already run.
The problems GUARDIAN solves for admissions and finance teams
Pick a problem to see what happens today, how GUARDIAN fixes it, and where your team stays in control.
Enquiries that arrive in the evening wait until tomorrow — by then, families have called other colleges.
Ravi's father sees your ad on a Sunday night, fills in the BBA enquiry form at 9:40 pm and sends a WhatsApp asking about fees and the hostel. Your counsellors see both on Monday afternoon, call twice, and reach him on Tuesday. By then he has booked visits to two other campuses.
Sound familiar?
- Monday mornings start with a pile of weekend enquiries
- Counsellors ask the same five questions on every call
- The same family appears twice in the CRM — once from the form, once from WhatsApp
- No one can say how many enquiries became enrolled students
Why it matters
- Speed decides who gets the visit — families enquire at several colleges at once.
- Counsellor time is your most expensive admissions resource, and it goes on enquiries that were never going to apply.
- Leads you paid for go cold before anyone speaks to them.
Where a person decides: GUARDIAN answers only from material you have approved. Anything outside it — scholarships, special cases, exceptions — goes to a counsellor. It never improvises a fee or an eligibility rule.
How GUARDIAN avoids wrong answers
- It answers only from your documents. Your brochure, fee sheet, eligibility rules and FAQs — nothing from the open internet, and nothing it makes up.
- If the answer isn't there, it says so. The question goes to a counsellor with the conversation attached. Scholarships, special cases and exceptions always go to a person.
- Fees change? Update one document. Replace the fee sheet and every answer uses the new figures from then on.
- Languages go live only after testing. Your staff check sample answers in each language before it's switched on.
- Every answer can show its source, so your team can see exactly which document it came from.
What setup involves: you share your brochure, fee sheet and common questions · we build the answer library and connect your form, WhatsApp number and CRM · your staff test the answers — and approve each language — before go-live.
What we'd measure in your pilot: time to first response, the share of enquiries qualified before a counsellor calls, and enquiry-to-application rate compared with last year.
For your IT team — how it connects
- Web forms post to GUARDIAN by webhook; WhatsApp runs on the WhatsApp Business API using your number.
- Leads are created or updated through your CRM's API, matched on phone and email so one family is one record.
- Answers come only from a knowledgebase of documents you approve; every answer can show its source.
- If you have no CRM (common for Type C colleges), GUARDIAN keeps the admissions record itself — no CRM migration needed.
Your staff check every marksheet photo by hand — and most of your applicants are 17.
Meera sends her Class 12 marksheet as a slightly blurred WhatsApp photo. Someone zooms in, types her marks into a spreadsheet and compares them with her application. Meera is 17. Under India's DPDP Act she is a child, so processing her personal data generally needs her parent's verifiable consent — and nobody has asked for it.
Sound familiar?
- Applications stuck in "documents pending" for weeks
- Blurry photos and the same document requested three times
- Marks typed into spreadsheets to check eligibility
- No record anywhere of a parent's consent
Why it matters
- Checking takes hours per applicant at exactly the busiest point of the year.
- Mistakes cut both ways — an ineligible student admitted, or an eligible one turned away.
- Many applicants are legally children. Under the DPDP Act anyone under 18 is a child, and processing their data generally needs a parent's verifiable consent — something most admissions processes don't capture today.
Where a person decides: a person confirms every applicant's eligibility. Unreadable documents and mismatches are flagged, never guessed — and document checks never decide an admission on their own.
How parental consent works
- Age check. Meera's date of birth on her application shows she is under 18.
- Parent's number. Human-BOT asks Meera for her parent's mobile number.
- A separate message to the parent on WhatsApp, in their language, explaining what data you collect, why, and how to withdraw consent later.
- Adult check. The parent shares a photo of an ID showing their date of birth. A member of your staff confirms it; the photo is then deleted and only the result is kept — "adult, verified by ID, on this date".
- Consent. The parent taps I agree. GUARDIAN records who agreed, when, how they were verified and which notice they saw.
- Withdrawal. The parent can reply "withdraw" at any time — processing pauses and your team is alerted.
GUARDIAN gives you the tools to capture consent. Confirm the requirements for your institution with your own advisor.
What setup involves: you share your eligibility criteria and document checklist · we configure the checks and the parent-consent messages · your admissions team tests with real sample documents before go-live.
What we'd measure in your pilot: days from application to "documents complete", the share of under-18 applicants with recorded parental consent, and flags raised per 100 applications.
For your IT team — how it connects
- Document reading runs inside GUARDIAN's privacy layer; ID numbers are replaced with tokens before any AI model sees the record, while marks stay usable for your eligibility rules.
- The consent log stores who consented, when, how, and which privacy notice they saw.
- Eligibility rules are configured from your published criteria — the AI does not invent them.
- Parent ID photos are deleted once staff confirm them; only the verification result is stored.
Your admissions team is re-typing every enrolled student into the ERP.
Ananya pays her admission fee on a Friday evening and her counsellor marks her Enrolled in the CRM. On Monday, someone in the admissions office opens the ERP and types her name, date of birth, programme, fee category and parents' details all over again — one of hundreds that week in July. One slip, and the misspelt name follows her onto her ID card and certificates, or the wrong fee category turns into the wrong fee demand.
Sound familiar?
- A data-entry backlog every July and August
- New students missing from class lists or fee ledgers in week one
- Name and fee-category corrections requested for months
- Her WhatsApp chats with counsellors live on one staff phone
Why it matters
- Errors are permanent — they travel into ID cards, fee demands and degree certificates.
- Staff time goes to copying, at exactly the moment counsellors should be converting the next applicant.
- You can't produce one record of what you hold about a student — something the DPDP Act lets her ask for.
Where a person decides: clean records go straight through. Anything GUARDIAN isn't sure about — a possible duplicate, a fee category your ERP doesn't recognise — stops for your admissions officer. GUARDIAN never guesses a value into your ERP.
How duplicate students are prevented
- Before creating anyone, GUARDIAN looks for the same person in your ERP — comparing phone number, date of birth and name.
- Clearly the same student? No second record is created; the existing one is used.
- Clearly new? The student is created.
- Anything in between — twins, siblings sharing a parent's phone, a student reapplying with a new number — waits for your admissions officer, with both records side by side.
- The same event twice (CRMs sometimes resend) never creates a second student.
What setup involves: your IT contact gives GUARDIAN access to your CRM and ERP (API, import file or on-site connector) · we match your CRM fields and fee codes to your ERP · you approve the mapping and test with sample students before go-live.
What we'd measure in your pilot: students created in the ERP per day, how many needed a person to decide, and name or fee corrections requested in the first term compared with last year.
For your IT team — how it connects
- Your CRM notifies GUARDIAN when a student reaches your "Enrolled" stage (LeadSquared and Meritto both support this); GUARDIAN then reads the full record through the CRM's API.
- The ERP record is created through your ERP's API, its bulk-import file, or a small outbound-only connector installed on-site for systems with neither.
- Each student is created once, even if the CRM sends the same event twice. Credentials sit in an encrypted vault; personal identifiers are tokenised before any AI model sees them.
After every due date, your finance team spends days chasing fees by phone.
Karthik's second-semester instalment was due on the 10th. On the 14th, an accounts assistant exports a defaulters list from the ERP and starts calling — including three families who paid on the 11th. Karthik's mother asks for a two-week extension on WhatsApp; whether she gets it depends on who reads the message.
Sound familiar?
- Defaulter lists exported and phoned one by one
- Reminders reaching families who have already paid
- Extension and concession requests arriving informally
- No record of who approved which concession
Why it matters
- Cash flow waits while reminders depend on someone having time to call.
- Routine chasing eats finance-team time every single term.
- Inconsistent concessions lead to fairness complaints and awkward audit questions.
Where a person decides: every extension, instalment plan or concession is decided by someone in finance. GUARDIAN never waives a rupee on its own.
What setup involves: you share your fee schedule and concession policy and connect your payment gateway · we set up the reminder messages · your finance team approves the wording and timing before go-live.
What we'd measure in your pilot: the share of fees collected within a week of the due date, average days overdue, and complaints about reminders.
For your IT team — how it connects
- Due dates come from your ERP; payment confirmations arrive from your payment gateway by webhook and stop reminders automatically.
- Reminders use pre-approved WhatsApp message templates.
- Payment and concession status are written back to your ERP only after the relevant step is complete.
Your whole admission process lives on one phone — usually someone's personal phone.
Every enquiry, marksheet photo and payment screenshot for your college arrives on the WhatsApp number your office manager carries. When she is on leave, messages wait. When a parent says they paid last week, someone scrolls back through hundreds of chats to check.
Sound familiar?
- Messages missed on busy days
- Documents saved in a phone's photo gallery
- Payments noted in a register or notebook
- Nobody else can take over when that person is away
Why it matters
- Admissions get lost or duplicated, and fee disputes can't be settled.
- One person is a single point of failure for your entire intake.
- Students' personal data sits on a personal phone — hard to defend under the DPDP Act.
Where a person decides: GUARDIAN can't admit or reject anyone. Your coordinator approves every offer.
What setup involves: your number moves to the WhatsApp Business API in a short, planned switchover · you share your course details and admission steps · your coordinator runs test admissions before go-live.
What we'd measure in your pilot: missed messages, days from first message to fee paid, and admissions recorded compared with last year.
For your IT team — how it connects
- Your number is moved to the WhatsApp Business API during onboarding; plan a short switchover.
- Documents are stored encrypted in GUARDIAN, not in a phone gallery.
- Seat confirmation is triggered by your payment gateway's confirmation, not by a screenshot.
Every merit round means days of re-ranking spreadsheets and calling waitlisted candidates.
Round 1 closes and 140 candidates decline or don't pay. Your admissions office exports the applicant list from SAMARTH, re-sorts it in Excel against the reservation rules, checks it twice, and then starts phoning the next candidates on the list. Round 2 goes out four days later — and some of those candidates have already joined another university.
Sound familiar?
- Applicant data exported from SAMARTH and re-worked in spreadsheets
- Reservation rules applied by hand, round after round
- Waitlisted candidates phoning the office to ask where they stand
- Seats still vacant when term starts
Why it matters
- Slow rounds lose candidates to institutions that confirm first.
- A ranking mistake is public — and can lead to complaints or legal challenge.
- The same work repeats every round, at the busiest time of year.
Where a person decides: GUARDIAN drafts; your registrar decides. Every rank can be traced back to the rule that produced it.
What setup involves: your registrar approves the ranking and reservation rules once · you share a sample SAMARTH export so we can read its layout · you run a trial round on past data before go-live.
What we'd measure in your pilot: hours per merit round, seats vacant at the start of term, and ranking queries or complaints.
For your IT team — how it connects
- SAMARTH exports are dropped into a secure folder or sent to a GUARDIAN inbox and read against a column layout agreed at onboarding.
- Ranking runs on rules your institution configures and approves — it is not an AI judgement.
- Candidate notices use approved WhatsApp templates or SMS.
Your faculty and office staff answer the same student questions all day — on their own phones.
It's the week before exams. Forty students message the same lecturer asking whether the timetable changed, three ask the office when fees are due, and one asks at 11 pm where the hall tickets are. Each gets a slightly different answer, depending on who replies.
Sound familiar?
- The same timetable and exam questions answered every day
- Staff personal numbers turned into help lines
- Different answers from different people
- Messages piling up at exam and fee time
Why it matters
- Teaching and admin time lost to questions a published document already answers.
- Inconsistent answers create confusion and complaints.
- Staff burnout at exactly the busiest points of the term.
Where a person decides: questions about a student's own marks, attendance or welfare — and anything GUARDIAN isn't sure of — go to a person. Distress or safety concerns go to your designated contact immediately.
What setup involves: you share timetables, calendars, fee deadlines and policies, and name who keeps them current (outdated ones expire automatically) · your staff test the answers before go-live.
What we'd measure in your pilot: share of questions answered without hand-over, response time for handed-over questions, and staff feedback.
For your IT team — how it connects
- Answers come only from documents you approve; outdated documents can be set to expire.
- Students' personal questions are answered only after identity is confirmed, and only if you enable it.
Your leadership sees last month's numbers — compiled by hand.
The trustees ask how admissions are tracking against target. Someone pulls figures from the CRM, fee collection from the ERP, and attendance from another report, pastes them into a spreadsheet, and emails it two days later. By then, a week of the admission season has passed.
Sound familiar?
- Monthly reports assembled by hand
- Figures from different systems that don't quite agree
- Leadership decisions made on stale numbers
- Staff pulled off their work to compile reports
Why it matters
- Slow numbers mean slow decisions — extra marketing, fee drives or intake changes come too late.
- Report-building is invisible work that repeats every month.
Where a person decides: the dashboard shows totals your team has defined — what counts as "enrolled" or "collected" is your decision, set once at the start.
What setup involves: you agree the definitions once (what counts as enrolled, collected or present) · we connect your CRM and ERP · leadership reviews the first version before it goes live.
What we'd measure in your pilot: hours spent preparing management reports, and how often leadership uses the dashboard.
For your IT team — how it connects
- Only aggregate figures are pulled; no individual student records are needed.
- Built once as an Insights Vending Machine setup task; refreshes do not consume AI Tasks.
How GUARDIAN connects to your systems
Three Siloed Systems. Zero Automation Between Them.
Your website, Lead CRM and ERP each hold part of the student's story. NEXUS connects them where they are — nothing is replaced, and your IT team writes no code.
Pick a Template. Connect It. Teach It Your Rules.
Every problem on this page comes as a designed workflow template for colleges, universities and training providers, set up with you in a pilot. You do not start from a blank page: choose one, give it your name, connect your systems and upload your own rules. Your team approves every important step.
- ChoosePick a template for your problem
- RenameGive it your own name
- ConnectLink your systems through NEXUS
- Set the startA new record, a file, a message or a time
- TeachUpload your rules, letters and FAQs to its expert
- TestRun it on your past cases
- ShadowIt runs on real work; your team checks every step
- LiveSteps go automatic only once your team agrees they are right
Every template has its own expert: the SME Agent
Each workflow step can ask its SME Agent (subject-matter expert) a question, such as "which documents does our policy accept here?". It answers from your material only, and always shows where the answer came from.
If it is not sure, it says so, and the step waits for your team. A step moves on by itself only when the rules are met and the confidence is high enough. Important decisions always go to a person.
- Current rulesRegulations and deadlines, kept up to date by Guideazy, with the date each rule starts
- Your policiesYour SOPs, limits and ways of working
- Your letters and formsThe wording and formats you already use
- Your historyPast tickets, customers and orders, read from your systems with personal details hidden
- Your team's decisionsWhat your approvers agreed or changed, so it learns your way
- Nothing sharedEach customer's expert is separate. The AI works on tokenised data, not real names or numbers.
Enquiry Answering and Qualification
Answers enquiries on WhatsApp and web forms from documents you approve, asks your qualification questions, and creates one CRM lead per family with the conversation attached.
What it needs
- Connects to
- Web form (webhook), WhatsApp Business Platform
- Your team approves
- Counsellor, Admissions head
- Its expert learns from
- Brochure and programme pages, Fee sheet with effective date, Eligibility criteria per programme and 2 more
CRM-to-ERP Enrolment Sync
When a student reaches your "Enrolled" stage in the CRM, creates their ERP student record using the field and fee-code mapping you approved, stops for a person on duplicates or unknown values, and writes the ERP ID back.
What it needs
- Connects to
- Lead CRM (LeadSquared / Meritto), ERP (read)
- Your team approves
- Admissions officer, Registrar
- Its expert learns from
- Field mapping sheet (CRM → ERP), Fee category and programme code tables, Rule for withdrawals and refunds after enrolment and 1 more
Admission Document Checks and Parental Consent
Collects marksheets and certificates on WhatsApp or e-mail, gets verifiable parental consent for applicants under 18, reads documents inside the privacy layer, checks them against your eligibility rules, and prepares each file for an admissions officer.
What it needs
- Connects to
- WhatsApp Business Platform, Lead CRM / application form
- Your team approves
- Admissions officer, Staff member
- Its expert learns from
- Eligibility criteria per programme and cycle, Document checklist per programme, Privacy notice and parental consent text and 1 more
Merit Rounds from Samarth Exports
Reads the applicant export your team takes from Samarth, drafts the next merit list with your approved ranking and reservation rules, gets the registrar's approval, notifies candidates and prepares the upload file for your staff.
What it needs
- Connects to
- Samarth export (file drop / inbox), Previous round results (GUARDIAN)
- Your team approves
- Registrar, Committee member
- Its expert learns from
- Admission policy and reservation rules, Seat matrix notification, Tie-break rules and 1 more
- Where there is no API
- GUARDIAN prepares the work; your team completes that step by hand, and it is recorded.
WhatsApp-Only Admissions
Runs the whole admission on your existing WhatsApp number: answers, application, documents and parental consent, coordinator approval, offer letter and fee link — with GUARDIAN keeping the record.
What it needs
- Connects to
- WhatsApp Business Platform, Payment gateway
- Your team approves
- Admissions coordinator, Finance / office
- Its expert learns from
- Course brochure and fee sheet, Admission steps and eligibility, Offer letter template and 1 more
Fee Reminders and Concession Requests
Sends staged fee reminders from your ERP schedule, stops the moment your gateway confirms payment, and brings every extension or concession request to finance with history and policy.
What it needs
- Connects to
- ERP fee schedule, Payment gateway, WhatsApp Business Platform
- Your team approves
- Finance officer, Finance head
- Its expert learns from
- Fee policy and instalment schedule, Concession and scholarship policy, Refund policy (UGC notice for the session)
Student Questions with Safe Hand-over
Answers routine student questions on the institution's number from approved, current documents, and hands personal, sensitive or uncertain questions to the right person — distress to the designated contact immediately.
What it needs
- Connects to
- WhatsApp Business Platform, Document library
- Your team approves
- Topic owners, Designated safeguarding / welfare contact
- Its expert learns from
- Timetables and exam schedules (with expiry), Academic calendar, Fee deadlines and 2 more
Leadership Dashboard (Totals Only)
Builds a leadership dashboard of enrolment, fees and attendance from totals only, using definitions you approve, refreshed automatically.
What it needs
- Connects to
- ERP / SIS (reports)
- Your team approves
- Definitions owner
- Its expert learns from
- Definitions of each measure, Targets for the cycle
UCAS Case Preparation
Prepares each UCAS application for a tutor — tariff points, statement summary against published criteria, qualification mapping from your tables. Every decision is made and recorded by a person.
What it needs
- Connects to
- SIS (SITS / Banner) or UCAS credentials, Course criteria
- Your team approves
- Admissions tutor
- Its expert learns from
- Course entry requirements, Equivalency tables for international qualifications, Admissions policy incl. contextual admissions and 1 more
- Where there is no API
- GUARDIAN prepares the work; your team completes that step by hand, and it is recorded.
Clearing Outreach
Matches opted-in prospects to Clearing vacancies on published requirements and contacts them first on WhatsApp or SMS; staff make every offer.
What it needs
- Connects to
- Vacancy list (upload / file), Prospect list
- Your team approves
- Admissions staff
- Its expert learns from
- Clearing policy, Published entry requirements, Call script
Direct and Apprenticeship Applications
Chases missing documents for direct and apprenticeship applications and collects a signed, timestamped employer confirmation, so admissions decide on complete files.
What it needs
- Connects to
- Web form (webhook), WhatsApp / e-mail
- Your team approves
- Admissions / apprenticeship team, Apprenticeship coordinator
- Its expert learns from
- Programme checklists, Apprenticeship evidence requirements for the current funding year, Safeguarding contact policy for under-18s
Approved Marks Sync (LMS to ERP / SIS)
Moves marks that the exam cell or exam board has approved from Moodle or Canvas into the ERP or SIS, checked against the roster and marks scheme. Never marks work.
What it needs
- Connects to
- LMS (Moodle / Canvas), ERP / SIS (read)
- Your team approves
- Exam cell / registry
- Its expert learns from
- Marks scheme per course, Exam regulations (moderation, corrections)
Faculty CAS Promotion Dossier
Assembles a faculty member's Career Advancement Scheme dossier from ERP records and uploaded evidence, checks it against the criteria your university adopted, and lists gaps for IQAC and the committee.
What it needs
- Connects to
- ERP (HR / service records), Faculty uploads
- Your team approves
- IQAC, Screening / selection committee
- Its expert learns from
- University's adopted CAS rules (UGC Regulations 2018, and any successor adopted), Proforma / application format, IQAC verification checklist
Student and Parent Data Requests and One-Click Erasure
Verifies the requester (including a parent for a child), maps the data held, applies your retention rules with Open Policy Agent, and after DPO and CISO approval erases the person's data in GUARDIAN by destroying their master key.
What it needs
- Connects to
- Request channels, All connected systems (via NEXUS), Consent log
- Your team approves
- DPO / data contact, CISO
- Its expert learns from
- Privacy notice, Retention schedule (academic records, finance, consent evidence), DSAR / grievance procedure
- Where there is no API
- GUARDIAN prepares the work; your team completes that step by hand, and it is recorded.
14 templates. Each one is fully designed and documented for our engineering team. We set it up with you in a pilot, and it starts in shadow mode before any step runs on its own. Some steps, like final approvals, never run on their own.
How the 4 Pillars Work Together — Education
Every Admissions Decision Is Made by a Person. Built In, Not Optional.
UK GDPR (Articles 22A–22D) and the EU AI Act (Article 14) set rules for automated decisions about applicants; India's DPDP Act focuses on consent, purpose and security. GUARDIAN's answer is the same for all three: a person makes every admissions decision. GUARDIAN's architecture makes compliance straightforward — by design, not by policy.
Three Deployment Models — Your Infrastructure, Your Choice
- No IT infrastructure investment — start with WhatsApp and your web form
- Secure partitioned data space per institution
- NEXUS connectors configured via encrypted dashboard
- Sized to your admissions volume — small colleges to large universities
- Dedicated GUARDIAN instance inside your private cloud
- NEXUS runs behind your corporate firewall
- Data never leaves your institution's jurisdiction
- White-label, custom SLA, dedicated engineering support
- Zero dependency on any external ERP or portal
- WhatsApp Business API provisioned by GUARDIAN
- Full admissions pipeline inside WhatsApp
- No website or IT team required
Plans for Every Education Institution
All plans include unlimited staff seats, NEXUS data connectors, HITL workflow gates, and compliance by architecture. No per-user pricing.
- NEXUS: Lead CRM connector (Merritto / LeadSquared)
- NEXUS: WhatsApp Business API integration
- NEXUS: Custom ERP read/write connector
- 2,000 AI Tasks/month · 5 GB sovereign storage
- Unlimited staff seats
- Multi-lingual: Hindi, Tamil, Telugu + more
- Document OCR & consistency checks
- HITL admissions & academic workflow gates (patent-pending GB2615329.6)
- Built to help you meet India's DPDP Act
- 1-click DSAR deletion · Full audit trail
- NEXUS: UCAS / SIS connector
- NEXUS: Web-form webhook (WordPress / Typeform)
- NEXUS: WhatsApp Business API integration
- 2,000 AI Tasks/month · 5 GB sovereign storage
- Unlimited staff seats
- Multi-language support — international students
- Personal statement summaries & tariff calculation
- HITL admissions approval gates (patent-pending GB2615329.6)
- Built for UK GDPR & EU AI Act Article 14 oversight
- 1-click DSAR deletion · Full audit trail
- Sovereign node inside your private cloud / firewall
- Custom AI Task volume & storage
- Unlimited seats + white-label
- UCAS / SAMARTH / ERP enterprise SLA
- SIS/ERP integration (Banner, SITS, Oracle, SAP)
- Custom qualification mapping framework
- Compliance documentation kit (UK GDPR · DPDP)
- Multi-campus deployment · Dedicated engineering
What a pilot looks like
You don't have to change everything at once. Start with one problem, prove it on your own data, then decide.
Ready to Unify Your Student Lifecycle?
14-day free trial. We configure GUARDIAN's connectors and your first workflow with you — no coding, no commitment. Connecting a CRM or ERP needs a little help from your IT contact.
Built to help you meet UK GDPR, India's DPDP Act and the EU AI Act. A person approves every admission decision.