How to choose a study abroad CRM in 2026.

1. Map your actual workflow, not someone else's

Before you look at a single demo, write down how your consultancy works today. Where do leads come from? Who calls them first? Who hands a student over to whom, and at which point? What has to be true before an application is submitted or a visa file is opened? The most common mistake is buying the CRM a friend's consultancy uses without checking that your workflow matches theirs.

2. Test follow-ups when several roles share a student

A student is rarely one person's job. A telecaller makes the first call, a counsellor shortlists universities, and an application or visa officer takes over each application. If the CRM holds one follow-up per lead, every new owner overwrites the last person's date and work slips at each hand-off. In the demo, give two roles on one student their own follow-ups and check that each person gets their own reminder when theirs falls due. Then ask to see the team's overdue follow-ups the way a manager would, by person, branch and role, and ask whether follow-up dates can be set automatically when a student reaches a stage. Finally, ask for a follow-up per role on every track: a loan, an interview preparation or a visa filing that runs beside the pipeline should carry its own assignment and its own follow-up for each role, independent of the stage the student is in.

Go deeper: Follow-up management CRM

3. Verify access by stage, branch, track and export

Access rules decide whether the CRM scales with you. Log in as a counsellor in one branch and try to find another branch's lead: in the list, in search, in reports and in exports. Branch managers should run their own teams and admins should see everything. Then check the finer controls: can access differ by pipeline stage, can a country manager see their countries without being assigned each lead, and can you stop staff exporting students' phone numbers? Ask for per-track levels too: a loan officer on Own should see only the students on the Loan track assigned to them, while the track head on Manage sees every student on it. 'Team-based access' is not the same as branch visibility, so ask specifically, and check that scheduled report emails follow the same rules.

Go deeper: Role-based access control CRM · Multi-branch CRM with role-based access

4. Open the automation log, retry a failed run and ask the AI to draft a rule

Automations do the unglamorous work: assigning new leads, dating follow-ups, moving applications on and sending the first WhatsApp template. When a rule fails quietly, nobody notices until a student does. Ask the vendor to show the automation log: which runs succeeded, failed or were skipped, and what each action did. Open a failed run and retry it. Ask whether a rule can be tested without changing real data, whether a rule can be kept inside business hours, and what stops two rules triggering each other in a loop. Ask whether a rule can move or sync a student's applications as a group, with exceptions per application. For a high-volume team, ask whether distribution respects an overdue limit, so a counsellor already holding too many overdue follow-ups is skipped and the lead goes to someone who can act on it. Then ask for an AI you can talk to that drafts your automations and runs your reports: describe a rule in plain words and see whether it lands in the builder, trigger, conditions, actions and dials, for you to preview and save.

Go deeper: CRM automation for counselling teams · Xale AI: talk to it, and let it draft your automations

5. Check how much of your study abroad work it models

A generic CRM stores a university as free text. A study abroad CRM should let one student hold several applications, each moving through its own stages with its own owner and payments. Check how it handles intakes, test scores, document checks before a stage moves, and deadlines such as offer to deposit. Visa steps change often, so check that you can edit visa stages, statuses and document requirements yourself, without custom development, and ask whether students can follow their own application's progress. Ask what ships on day one.

Go deeper: Xale CRM for study abroad consultancies · University application tracking

6. List your channels and test WhatsApp end to end

For an Indian consultancy, WhatsApp and Meta Lead Ads are usually where leads start, and phone calls are where most counselling happens. Ask how each channel gets into the CRM. WhatsApp can run on Meta's Cloud API, alongside the WhatsApp Business app with Coexistence, or through a provider such as Wati, Gallabox or UrbanChat, so check that the CRM works with the route you already use. For Meta leads, check that each carries its campaign and form. If your counsellors call from their own phones, ask how those calls and recordings reach the lead. Then run a real WhatsApp test with your own number: templates with variables such as name, course and intake, a broadcast to a filtered segment, replies threaded against the lead, the 24-hour customer service window respected, and a template sent by an automation when a lead is created.

Go deeper: WhatsApp CRM for education · CRM with call recording

7. Check that the reports can be trusted, and that you can build your own

Every CRM has dashboards. Fewer let you check them. Pick a number, such as last month's conversions for one branch, and ask to open the list of leads behind it. If the count and the list disagree, or if 'conversion' means something different on each screen, your team will spend meetings arguing about data instead of acting on it. Then ask for a custom report builder and use it for a question of your own, such as applications by country and intake: group the rows, add a second column level, filter with AND/OR/NOT conditions, switch between a table, a chart and a KPI tile, and open a cell to see the rows behind it. Ask the CRM's AI, by voice if it lets you, for the same figure and check that it matches the report. Ask how cost per lead is calculated and whether counsellors see only their own numbers.

Go deeper: CRM reports and analytics · The Custom Report Builder

8. Demand a real demo with your own data

Don't sit through a generic sales demo. Bring ten anonymised leads from your spreadsheet. Ask the vendor to import them, configure your pipeline, and set up a WhatsApp template, an assignment rule and a follow-up automation while you watch. If they can't, the product probably isn't ready for a multi-branch consultancy, whatever the slide deck says. A hands-on setup session tells you more than any feature list.

9. Check that pricing scales with you

Many CRMs are cheap at five users and expensive at fifty. WhatsApp message charges, support tiers, extra pipelines and field limits are the usual surprises. Project your usage 24 months out, price each shortlisted CRM against that projection, and get the total in writing.

Go deeper: Xale pricing

10. Call references, run a real pilot and plan your exit

Ask for references similar to you in size, and ask what they migrated from and what surprised them. Then put one branch or one intake on the CRM before you commit: import real leads, connect your real WhatsApp number, and measure speed to first call, missed follow-ups and stage conversion before and after. Finally, ask how you would leave. Can you export every lead with its fields, notes and history in a machine-readable format, whenever you want? Decide on those numbers, not on the demo.