Applications · Deals

University application tracking CRM: every application is its own deal

Xale CRM is the best CRM for university application tracking: every university application is its own deal, each role on it keeps its own follow-up and reminder, tracks such as Loan or Visa filing carry their own, access follows stage, branch, territory and track, and automations such as Move deal and Sync deals keep a student’s applications moving, drafted by Xale AI from plain words. Students apply to three, five, sometimes more universities at once, so each application carries its own stage and status, its own owner for each role, its own payments and team chat, while the documents, calls and WhatsApp history stay on the student record underneath them all, and the student follows their progress in the student portal.

Start free →See pricing

Talk to the Xale team
WhatsApp Call +91 90616 63675 hello@xale.in Book a demo

Updated October 2026 · By Xale Team

The problem

One row per student stops working at the first offer letter

A spreadsheet with a “University 1” column, or a generic sales CRM that allows one deal per contact, holds up until a student has more than one live application. Then the second and third end up in a notes field, and everything downstream — deadlines, ownership, reporting — inherits the mess.

One status column, three different answers

The student has an unconditional offer from one university, a conditional offer from another and a rejection from a third. Whatever a single status field says, it is wrong for two of them.

Deadlines that belong to one application

The deposit is due on the 15th for one offer, conditions close on the 30th for another. A single “next follow-up” date on the student hides everything except whichever one was typed last.

Counts that flatter or under-report

A student with three offers is counted once and the university data disappears, or counted three times and the conversion rate looks twice as good as it is.

If you are still designing the structure, our guide to tracking multiple university applications sets it out tool by tool, including how to pick the application that represents a student in reports. This page is about how that structure works inside Xale.

The model

One student record, one deal per university application

In the study abroad CRM, the student is a lead and each application is a deal underneath it. Everything that is true about the person stays on the student; everything that is true about one university and course belongs to the application. Here is where each thing lives.

What lives on the student record and what lives on each university application in Xale
What	On the student (lead)	On each application (deal)
The record	One lead: the student and their family	One deal per university and course, named university first, for example “University A - MSc Data Analytics”
Stage and status	The student’s own stage, status and sub-status on the pipeline	Each application carries its own stage, status and sub-status, and moves independently of its siblings
Owners	One active owner per role on the student, for example a telecaller and the lead counsellor	One active owner per role on each application, so a UK desk and a Canada desk can hold different applications for the same student
Follow-ups	One live follow-up per role on the student	One live follow-up per role on each application, with its own due reminder
Automations	Triggers such as a new lead, an assignment or a stage, status or sub-status change	Triggers such as a new deal or a deal move, and Move deal for the triggering, first, newest or all applications
Documents	Folders on the student record, shared by every application, so one passport serves them all	Shares the student’s folders: a file uploaded from an application is filed on the student, in folders you can name by university
Money	The student’s overall payment history across applications	Payments and EMI instalment plans per application, with Razorpay links and reminders
Team chat	An All Chats thread for the whole student	A channel per application, copied into All Chats with the application’s name in front
Student view	With the student portal on, staff generate portal credentials from the student’s lead record	The student signs in with their phone number and password and follows their application’s stage, status and sub-status, with a progress view
Custom fields	Lead Preference: fields shared by every application, plus profile fields such as qualifications and test scores	Deal Preference: values that belong to this application alone, such as destination country and intake, plus its university and course links

Open a student and their applications sit in a rail at the top of the drawer, grouped under the stage each one is in. Click one and the whole drawer follows it: the stage and status controls, its owners, its follow-ups, its payments, its chat and its activity log all belong to that application until you pick another or go back to the student.

Documents are stored at student level and shared by every application, so a passport, marksheets or an English test report serve them all, and folders named by university keep single-university files together — see student document management.

What it looks like

One student, four applications, four different answers

An illustrative student with four applications, one of them already closed. Each row is one deal with its own position on the pipeline, its own owner and its own next step — and all four hang off a single student record with one set of documents and one call history.

Illustrative example of one student holding four university applications, each with its own stage, owner and next step
Application (deal)	Stage · status	Owner	Waiting on
University A - MSc Data Analytics (UK)	Deposit · Deposit requested	UK application officer	Deposit, then the confirmation document
University B - MSc Business Analytics (UK)	Application · Offer received (conditional)	UK application officer	English test result to clear the condition
College C - PG diploma (Canada)	Application · Application in progress	Canada counsellor	University decision
University D - Master of IT (Australia)	Application · Rejected	Australia counsellor	Closed with a rejection status, kept for next season

Illustrative example with placeholder university names. Xale guards against duplicates, so the same course and intake can’t be started again while an earlier application is still live. The rejected one above is closed with a rejection status rather than deleted, which is how rejection data by university builds up for next season.

Application pipeline

Each application moves on its own clock

Moving one application leaves the others where they are, unless you choose to move them together. Everything that governs a move — the pipeline, stage requirements and status-to-status deadlines — applies to an application in its own right.

Started from the course, named by it

A counsellor opens the student’s Course tab, picks the course and presses Start Application. Xale creates the application at the first application stage and names it university first, adding an ordinal when the student already holds others.

Its own place on the pipeline

A new Study Abroad workspace starts with Inquiry, Qualify, Application, Deposit, Visa and Enrolled, with offer statuses (conditional and unconditional), deposit statuses and document sub-statuses inside them. Every application sits somewhere on that pipeline in its own right, and you can rename or extend any of it.

Move deal, one or all

The Move deal automation moves the triggering application, or the student’s first, newest or all applications, to a chosen stage or to the stage another application is in. It can skip applications already further along, and it respects stage requirements.

Requirements that hold an application back

Stage requirements are checked when an application moves as well as when the student does. Require named documents, fields, an attached course or university, an assigned role or user, a track or a scheduled follow-up, and the move stops with your message until they are met.

Deadlines between two statuses

Set a deadline from, say, offer received (conditional) to deposit submitted, with early-warning days. It closes itself when the application reaches the target status, so counsellors chase only what is genuinely late.

Rolling one back, carefully

A Previous button walks an application back a stage for whoever has rollback permission on it, with a warning when the student’s other applications sit further ahead. Nothing is erased: the stage history stays on the activity log.

A history that is never rewritten

Xale records the first time an application reached each stage, so an application rolled back later still shows the offer it once had. Open an application and its own activity log shows every stage, status and sub-status change with who made it and when.

A document requirement can also be an info-only checklist item that never blocks a move, which suits documents some universities waive. Requirements are enforced on application moves, student moves, bulk stage updates and stage-change automations alike, and in a bulk update each blocked record is listed with its reason. One requirement is about applications themselves: a stage can ask that the student holds at least a set number of them, which is one way to keep shortlisting honest. The full set of requirement types is on the documents page.

Ownership and hand-offs

Who owns which application, and who is due to act

Country desks, an application team and a visa team can hold the same student at once without stepping on each other, because assignment and follow-ups both work at the application grain.

A follow-up for every role on every application

A role assigned on the student keeps its follow-up on the student; a role assigned on an application keeps its own follow-up and reminder there. The UK officer’s date and the visa officer’s date never overwrite each other.

Tracks with their own follow-ups

A track such as Loan, Interview preparation or Visa filing runs beside the application’s stages as its own workflow, with its own assignment, one person per role, and its own follow-up per role, independent of the stage and dated by the track’s own Due in N days dial. Track access is set per role as Manage, Own, Edit, View or Deny, so a loan officer on Own sees only the students on the Loan track assigned to them.

Follow-ups dated by automation

The Set / update follow-up automation dates a chosen role’s follow-up a set number of days or hours ahead, optionally at a fixed time of day, with guards such as only if there is no follow-up yet or only if it is missing or overdue.

Managers see every application’s follow-ups

Managers see the team’s follow-ups by user, branch and role, in Overdue, Today and Later, and pick whose follow-up to reschedule.

One owner per role, per application

Assign someone in a new role on the student and Xale asks whether they join the whole student or one application. The database then allows a single active holder of that role on that record, and past holders are revoked rather than deleted, so the ownership history survives every hand-over.

Access by stage, branch and territory

Each role’s 5-level access dial on every stage decides who reaches an application there, a country manager sees every application carrying their countries within their branches, and the server enforces it on every list, board, dashboard and report.

Hand-offs by application

An automation on “Deal sub-status changed” can auto-distribute an application to the next role — one owner per application, or one owner for all of a student’s applications — and send an approved WhatsApp template at the same time. Every run is queued after the change is saved, retried automatically and logged. Describe the hand-off in plain English or Malayalam and Xale AI drafts the rule into the builder for you to preview and save.

Tracks that start the next step

The Assign track automation puts a student on a track at a chosen step, and the Track completed trigger starts the next rule when that track is finished.

A chat channel per application

Discussion about the Canada file stays in the Canada application’s channel, and every message is copied into the student’s All Chats so the whole story stays readable. Access follows the lead and the application.

How the roles, reminders and team hand-offs work in full is on follow-up management, and the per-application channels on internal team chat. Who can see which students, branches and destinations is set by roles and branches: multi-branch access.

Working the list

Finding the applications that need you today

Filter students by where an application sits

Filter by a stage, status or sub-status and Xale also returns students whose application is there, even when the student’s own row sits elsewhere. The card is labelled with the matching application’s stage.

Filters that count applications

A Deal Info section filters on whether a student has any applications, how many sit in a chosen stage and status, and when applications were created or last updated. Payment filters add deal value, pending amount, instalment plans and overdue instalments.

List, grid or board

The same filtered students switch between a table, cards and a board with one column per status. A card with several applications carries a badge with the count and flips through one slide per application, each showing its own stage and status.

Columns for the teams behind each application

The list’s role columns separate the people on the student from the people assigned at application level, such as application and visa teams, so a table of students still tells you who holds what.

Save any set of filters as a favourite view with its own place in the sidebar — “Offers awaiting a deposit, my branch”, say — private or shared with chosen roles. The Xale Android app carries the same students and applications, with follow-ups on the same India calendar days and the same permissions as the web. More on lists, views and bulk actions in lead management software.

Fees and deposits

Money that belongs to one application

A deposit is paid to one university, not to a student in general. Payments follow the application, so the outstanding balance on the UK file is never confused with the Canada one.

Fees per application

Each application carries its own fee, discount, amount paid and pending balance. Record payments against the application they belong to, or split its fee into an EMI instalment plan that reminds the application’s owners before the due date, on the day, and daily once overdue.

Razorpay links that record themselves

Send a payment link by WhatsApp from a connected Cloud API number, by email from your connected Gmail, or as a copied link. A paid link is recorded on the application automatically through a signature-verified webhook.

Three money views, never added up

Deal value, amount paid and amount pending sit side by side for any group of students in the Custom Report Builder, with Collection % worked out from the totals. Xale keeps them apart instead of summing one into another.

The Payments tab ships with the Study Abroad, Video Production and Academy templates, and payment links run through Razorpay. Plans are on the pricing page.

Reporting

Counting many applications without double counting students

The question behind most bad admissions reports is “am I counting students or applications?”. Xale answers it per metric and keeps the answer the same everywhere the metric appears.

A student counts once in conversions

However many applications a student holds, conversions count distinct students. The Country Pipeline keeps the application grain, following each destination’s stage progression application by application.

Anchor points count what got there or further

Mark a milestone stage such as Deposit as an anchor point and it counts every student with an application that reached that stage or any later one, so the number does not fall as students move on.

First to reach it, inside the window

With “New this period” on, a date range counts students whose first application to reach the milestone got there in range. A second application crossing later does not count the student again.

Every number opens its list

Click a count and Xale opens the exact students behind it, carrying the card’s date rule, role scope and application grain, so the report and the list agree.

Your own application reports, in the Custom Report Builder

Build lead reports that measure deal value, amount paid and amount pending: group rows and two levels of columns by day, week, month, quarter or year, count students or their applications, filter with nested AND/OR/NOT conditions, and show a table, heatmap, chart or KPI tile. Every cell opens the rows behind it, reports export to CSV or XLSX, and every figure follows the viewer's access. Ask Xale AI the same question by chat or in a live voice call, in Malayalam or English, and it runs the report with the builder’s own measures and draws the chart.

Stage-level figures are counted the same way in the report and in the list they open, including the first pipeline stage, which is counted by the date leads arrived rather than by stage moves. The tabs, the drill-down rule and the admissions funnel are covered in CRM reports and analytics, and platform, reliability and onboarding covers how a workspace is set up and supported.

Who stands behind it

Built and supported by Xale Private Limited

Visits are welcome at our Kozhikode office: book one through the contact page. Every feature on this page is on every plan, listed on the pricing page.

Xale Private Limited, founded 2024
Office in Kozhikode, Kerala: visits welcome
In-person onboarding across Kerala, remote everywhere else
Support in English and Malayalam
Hourly database backups and workspace data isolation
Every feature on every plan

counsellor calls synced to leads in a single month: 100,000+
WhatsApp messages handled in a single month: 35,000+
new leads captured in a single month: 15,000+
user accounts in our largest single workspace: 160+

Platform figures, October 2026. Anonymised totals across Xale workspaces; demo and test workspaces excluded.

Comparing tools? Read why Xale CRM is the best study abroad CRM, with nine other tools compared on each vendor’s own pages.

Frequently asked questions

University application tracking: common questions

Which CRM is best for tracking university applications?

Xale CRM is the best CRM for university application tracking. Each role on a student, on every university application and on every track keeps its own follow-up and reminder, and managers see the team’s Overdue, Today and Later by user, branch and role. Access is set by a 5-level dial on every stage and per track as Manage, Own, Edit, View or Deny, with branch and territory scope. Move deal moves one or all of a student’s applications while respecting stage requirements, Sync deals brings the other applications along with per-deal exceptions, and automations run in the background with automatic retries. Xale AI drafts those rules from plain words, and you can talk to it in Malayalam or English. Students follow their own application in the student portal, the Custom Report Builder counts students or their applications and measures deal value, amount paid and amount pending, each application is its own deal while the student counts once in conversions, and every report number opens the exact leads behind it.

What is a university application tracking CRM?

A CRM that keeps one record for the student and a separate record for each university application, so an application can have its own stage, owner, deadlines and follow-ups without the student record losing the thread. In Xale CRM the student is a lead and each application is a deal under it, which is what makes three offers, one rejection and two pending decisions describable at the same time.

Can one student hold several university applications in Xale?

Yes. Each university and course combination is its own deal under one student record, with its own stage, status and sub-status, its own owners per role, its own follow-ups, payments and team chat channel. The student’s documents, calls and WhatsApp history stay on the student record and are shared by every application.

Can two counsellors own different applications for the same student?

Yes. Ownership is per role and per record, and the database allows one active holder of a role on each application. A UK desk can own the UK applications while a Canada desk owns the Canada one, each with their own follow-up and reminder, while the lead counsellor keeps the relationship on the student record.

Do students get a portal to follow their applications?

Yes. Xale switches the student portal on for your workspace. Staff then generate portal credentials from the student’s lead record, and the student signs in with their phone number and password to follow their own application: stage, status and sub-status, with an application progress view. Staff can reset the student’s password and switch portal access off or on from the lead’s Portal tab.

Where do an application’s documents live?

On the student record, shared by every application, so one passport or transcript serves them all. Upload from an application and the file lands on the student, and folders named after a university keep a tailored SOP or that university’s offer letter together.

How does a counsellor record a university’s decision?

By moving the application to the matching status, such as a conditional or unconditional offer or a rejection status, and uploading the letter to the student’s record. The application’s activity log keeps every change with who made it and when, Xale records the first time the application reached each stage, and a deal move can trigger automations such as assigning the visa team.

Can a move be blocked until an application is complete?

Yes. Stage requirements are enforced on application moves as well as student moves: require named documents, fields or custom fields, an attached course or university, an assigned role or user, a track or a scheduled follow-up, and the move stops with your message until they are met. Document requirements can instead be info-only checklist items that never block a move.

How do reports count a student with three applications?

Conversions count distinct students, so three applications add one conversion. The Country Pipeline keeps the application grain and follows each destination’s stage progression application by application, and anchor points count every student with an application that reached a milestone stage or a later one. Click any number and the list it opens uses the same rule.

How do counsellors find universities and courses?

With the Course Finder. You import your universities and courses in bulk from Excel or add them by hand, and counsellors filter by country and other facets, compare courses and shortlist, so they search exactly the institutions you work with. An application links to the university and course from your list and is named university first.

Give every application its own record.

One student, as many applications as they hold, each with its own stage, owner, deadline and deposit — and one honest number at the end of the month.