Best CRM for Education Consultants: 7 Questions

Every vendor will tell you theirs is the best CRM for education consultants, and every demo runs on tidy sample data that makes the claim look true. The way through is to arrive with seven questions and your own untidy students, and to make the vendor answer on screen rather than on a slide. This guide gives you those questions: why each one matters to a consultancy, what to ask the vendor to show, and the answer that should end the conversation. It is written for owners, admissions heads and senior counsellors in India who are about to sit through demos.

Key takeaways

Bring a demo pack of real, anonymised students, and don't let the vendor swap it for their sample data.

The first question, how the CRM handles several applications for one student, rules out more tools than the other six together.

Ask about WhatsApp and calls as routes: which connection, which phones, who owns the number, who sends the bill.

Access and reports cause the arguments after go-live. Check what a branch manager cannot see, and whether a report number opens a list of exactly that many students.

Score every answer the same way, weighted for your consultancy, on the day of the demo.

Build your demo pack before the first call

A vendor's sample data has one student per country, no duplicates and nobody on leave. Yours does not. Hand every vendor the same pack:

Five anonymised students, including one with three applications in two countries and one duplicate enquiry under a different spelling.
One live lead form from your Meta ads, so a real enquiry can arrive during the call.
Your stage names and the documents you collect at each stage, on one page.
Two counsellors' actual phones (an iPhone too, if anyone uses one) and your front-desk WhatsApp number.
Logins to test: owner, branch manager, counsellor and telecaller.
Last month's enquiries, applications and deposits, to check the CRM's reports against.

If a vendor cannot run the demo on this pack, write that down. It is a preview of implementation.

Question 1: How does it handle several applications for one student?

A consultancy's unit of work is the application, not the student. Take a hypothetical student, Rahul, applying for a master's at two UK universities and one in Canada. Each application has its own status, owner, fee and outcome. Store them as three fields on one record, or as three leads, and your conversion numbers are wrong from week one: one status hides two outcomes, or Rahul is counted three times.

Ask them to show	Follow-up question	Red flag
Rahul created once, with three applications under him	Reject the Canadian application. Do the two UK ones stay where they were?	"Add a custom field for each university"
Each application with its own stage and owner	Can the UK files go to one officer and Canada to another?	One owner per student, however many applications
The conversion report after one UK deposit	Does Rahul count once or twice?	Enrolment counts that change when you add an application

Our guide to tracking multiple university applications goes deeper on the data model.

Question 2: Where do documents live, and what enforces the deadlines?

Rahul's passport, marksheets and bank statements serve all three applications. If documents attach to each application separately, counsellors upload the same passport three times and one copy goes stale.

Deadlines stack backwards from the course start. GOV.UK says the earliest you can apply for a Student visa from outside the UK is 6 months before the course starts, and a decision usually takes 3 weeks. The same page requires an offer from a licensed student sponsor first, and allows arrival up to 1 month before a course longer than 6 months.

Worked example. For a hypothetical course starting on 21 September, Rahul's visa window opens on 21 March and he can arrive from 21 August. An internal rule of "submit by 15 July" leaves room for the 3-week decision and for flights. That date belongs on the UK application, with an early warning, not in a counsellor's diary.

Ask them to show a passport uploaded once and visible from all three applications, an application blocked from "Submitted" while the SOP is missing, and a deadline that clears itself once the target status is reached. The red flag is a date field nobody is reminded about.

Question 3: Which WhatsApp route does it support, and do we keep our number?

WhatsApp is most consultancies' main channel, and its number is on every banner. Three things decide whether a CRM's WhatsApp works for you: the connection it uses (the Business app, Meta's Cloud API, or a provider such as Wati or Gallabox), whether you keep your number, and who bills you for messages. Our explainer on the WhatsApp Business app vs the API vs Coexistence covers the trade-offs.

Coexistence changed the old either-or. Meta's developer documentation says a business that brings its WhatsApp Business app number onto the Cloud API can still send one-to-one messages from the app, with chats from the most recent 6 months synchronised if the business approves. The same page lists what stops working on that number: group chats, disappearing messages, view-once messages, live location sharing and broadcast lists. If your front desk relies on broadcast lists, plan for that first.

Ask them to show: a chat on the student record, a reply from a second counsellor, and where opt-in is recorded.
Follow-up question: "We already pay a WhatsApp provider. Can we connect that account?"
Red flag: a click-to-chat link that opens the counsellor's own phone, so the conversation never reaches the record.

Question 4: How are calls logged and recorded, on the phones we actually carry?

Counsellors call students from their own mobiles, and many decisions are made on those calls. A CRM can capture them two ways. Call-log sync uses an app on the counsellor's phone to file each call on the matching lead, usually with the phone's own recording. Cloud telephony routes calls through a business number and records them in the provider's cloud on any handset, with the provider's charges on top. Neither wins every time. In the demo, with your counsellors' phones:

Call from a counsellor's own phone and time how long the call takes to appear on the lead, with direction, duration and outcome.
Play the recording from the lead.
Call from a number that is not yet a lead. Does it create one?
Show how the iPhone user's calls are covered.
Show who can hear recordings, and whether capture can be off for some roles.

The question buyers forget: who owns the number when a counsellor resigns? With personal SIMs, students keep the counsellor's number; with cloud telephony, it stays with you. The red flag is "we record every call" with no word on the route.

Question 5: Can each role keep its own follow-up?

One student passes through a telecaller, a counsellor, an application officer and a visa officer, often at once. If the CRM keeps one "next follow-up date" per lead, the visa officer's date overwrites the counsellor's, and one of them silently stops calling. The second trap is how "overdue" is defined: a call due at 10 a.m. that slipped to the afternoon is still today's work, and a list that says otherwise hides it from the day's plan.

Ask them to show the telecaller setting a follow-up for tomorrow and the counsellor one for Friday on the same student, and confirm both survive. Open the manager's view for Overdue, Today and Later by counsellor and branch. Then ask what happens to a follow-up when the student is reassigned. The red flag is one follow-up field per lead, however many people work the student.

Question 6: What does a branch manager see, and what can't they?

Once you open a second office, access is a business question: a branch manager who sees every branch's students, or a counsellor who can export the database, can take them along when they leave. It is also a legal question. The Press Information Bureau's backgrounder on the Digital Personal Data Protection Rules, 2025, notified on 14 November 2025, lists penalties of up to ₹250 crore for failing to maintain reasonable security safeguards, and says requests to access, correct or erase personal data must be answered within ninety days. Limiting who sees and exports student data is part of that work; take legal advice on the rest.

The branch manager sees their branch and their own assigned students, nothing else.
A student transferred between branches keeps their history.
A counsellor's export is limited to what they can see, or blocked.
Phone numbers can be masked in lists.
One student's full record is quick to find for an erasure request.

The red flag: "Everyone sees all leads, but you can filter." A filter is not access control.

Question 7: When I click a report number, does the list match?

Reports are where trust in a CRM is lost. The owner sees "Deposits this month: 42", the branch manager counts 38, and Monday morning goes on deciding whose number is right. Often both are right about different things: 42 applications from 38 students, or a report dated by stage change while the list filters by enquiry date. Our post on why a CRM report doesn't match the leads list covers the usual causes.

Ask the vendor to click any dashboard number and count the list it opens. Ask what the unit is (students or applications), which date each report uses, and whether a counsellor sees it limited to their own students. Then hand over last month's numbers from your pack. The red flag is a number that cannot be opened, or "we'll build that during implementation" for something as basic as enquiries by source.

Scoring the seven answers

Score each question 0 (fails), 1 (works with a workaround) or 2 (works on your data), weighted by what breaks first for you. Take a hypothetical consultancy with three branches, 12 counsellors and a WhatsApp-heavy front desk:

Question	Weight	Vendor A	Vendor B	Vendor C
1. Applications per student	25	2	1	2
2. Documents and deadlines	15	1	2	2
3. WhatsApp route	15	2	2	1
4. Calls and recording	15	0	2	2
5. Follow-ups by role	10	1	1	2
6. Branch access	10	2	2	1
7. Reports that open lists	10	1	0	2
Weighted score (out of 200)	100	135	145	175

Two rules keep this honest. A zero on a question weighted 15 or more is a veto, whatever the total: Vendor A's counsellors would keep calling off the record. And when your shape changes, change the weights, not the questions; a two-counsellor office might put branch access at 0 and calls and WhatsApp at 25 each.

Only then compare price and ask how you would export everything if you left. For the wider process, see how to choose a study abroad CRM; for tools grouped by kind of institute, the best education CRM by use case.

How Xale handles this

Xale is our product, so weigh this section accordingly. Each university application is its own deal under one student record, with its own stage, owner, payments and chat, and the student counts once in conversions. Documents sit in folders on the student's record, shared by all of that student's applications. Stage requirements can block a move until named documents are in place, and status-to-status deadlines warn early and close themselves when the student reaches the target status. WhatsApp runs on Meta's Cloud API, including Coexistence, or an existing Wati, Gallabox or UrbanChat account, in one role-scoped inbox.

Every counsellor call logged and recorded, two routes. The Xale Android app syncs each call from the counsellor's own phone to the right lead with direction, duration and outcome, no per-minute charges, and attaches the phone's own recording. TeleCMI cloud telephony records calls from a business number on any phone, iPhone included.

Follow-ups are one per role per lead or deal, on India calendar days. Counsellors see their leads, branch managers their branches, and any report number opens the exact leads behind it. The limits: a document requirement checks the file's name, not its contents; Gallabox chats can't be answered from the inbox yet; and there is no applicant portal. See how each role in a consultancy uses Xale.

Frequently asked questions

How many CRMs should an education consultancy demo before choosing?

Three is usually enough, four at most. Fewer and you have nothing to compare against; more and the demos blur together while the decision drifts. Shortlist on the first question alone, how the tool handles several applications for one student, because it removes unsuitable options fastest. Then run the same pack and the same seven questions in every remaining demo, and score each on the day.

Should we let the vendor use their own demo data?

Only for the first ten minutes, to see the product's shape. After that, insist on your own anonymised students, your stage names and a live lead from your own form. Sample data hides what causes trouble after go-live: duplicate enquiries, students applying in two countries, counsellors sharing a WhatsApp number. A vendor who cannot load a few of your students is showing you what implementation will be like.

Is the cheapest CRM a bad choice for a small consultancy?

Not necessarily. What matters is whether the tool passes the questions that carry weight at your size. A two-counsellor office can give branch access almost no weight and put most of it on applications, calls and WhatsApp. A cheap tool becomes expensive when it scores zero on one of those, because the team works around it in spreadsheets. Compare the full cost, including WhatsApp, telephony and setup time.

What should we ask about leaving the CRM later?

Ask how you export every student with their applications, documents, notes and call history, in what format, and whether export is self-service. Ask what happens to your data after you stop paying. Then test it during the trial by exporting a handful of students and opening the file. If a vendor is vague about leaving, better to learn that before three years of student history goes in.