Best CRM for a Small Study Abroad Agency (1 to 5 Counsellors)
Choosing a CRM for small study abroad agency teams of one to five counsellors: what you need, what to skip, per-workspace pricing and a one-week setup plan.
A small study abroad agency does not need the CRM that a 200-seat consultancy runs. It needs the few things that stop students slipping between two or three people, set up in days rather than months. This guide is for owners and counsellors choosing a CRM for small study abroad agency teams of one to five people in India: what matters at this size, what you can safely skip until you grow, how to read a price list, and a one-week plan to get running.
Key takeaways
- At one to five counsellors the enemy is not chaos, it is silence: a lead nobody called, an offer nobody chased, a visa file that sat for a week. Buy for those failures, not for dashboards.
- Five things are non-negotiable even at three people: several applications per student, documents on the student record, WhatsApp and calls that stay with the record, Meta leads that arrive on their own, and a clean export.
- Skip territory routing, approval chains, escalation rules and custom objects until you have a second branch or a second team.
- Pricing per workspace usually beats per-seat pricing at this size, because the owner, a part-timer and the visa person all need their own logins.
- A working setup takes a week if you freeze the old sheet, import active students first and switch your Meta forms across last.
What a small study abroad agency actually needs
Take a hypothetical agency in Kochi. Priya owns it and counsels. Arun makes first calls and handles WhatsApp. Sherin prepares visa files two days a week. They receive about 120 new enquiries a month, mostly from Instagram ads and referrals, and send roughly 25 applications a month to the UK, Ireland and Germany.
Their problems are specific, and none of them is "we lack reporting".
| Problem at this size | What causes it | What the CRM must do |
|---|---|---|
| Meta leads called a day late | Someone has to remember to download the CSV | Pull leads in on a schedule, with the campaign and form name attached |
| Two people message the same student | Arun's phone and Priya's phone hold different halves of the chat | One WhatsApp inbox, on the student's record |
| An offer deadline passes | It was in Priya's head | A deadline on the application that warns early |
| Sherin can't find the passport | It was sent to Arun on WhatsApp | Document folders on the student record |
| Nobody knows whether Arun called the new leads | Call history lives on his handset | Calls logged to the lead from his own phone |
| The month-end count is disputed | Three tabs, three answers | Reports that open the list behind each number |
Notice what is not on the list: lead scoring, territory rules, approval workflows, multi-branch dashboards. Those solve problems Priya does not have yet, and every one of them needs someone to administer it.
The five non-negotiables, even at three people
Several applications per student
Ananya applies to three universities. Your CRM must keep three application records under her one profile, each with its own stage and owner. If it can't, your "Status" column is wrong the day the second offer arrives. The mechanics are in how to track multiple university applications.
Documents on the student, not on the application
A passport, marksheets and an SOP belong to the student and are reused by every application. If the CRM stores files per application, Sherin uploads the same passport three times and finds the wrong version once.
WhatsApp and calls that stay with the record
Meta's opt-in rules require you to clearly state the business's name a person is opting in to hear from, and to honour opt-outs. That is easier to prove when the chat sits on the student's record rather than on a personal phone. For calls, ask for one of two routes: the counsellor's own SIM with the call synced to the CRM, or a cloud number that records on any phone. Our SIM call recording vs cloud telephony comparison walks through the cost model of each.
Meta leads that arrive on their own
Meta's Help Centre says leads data can be downloaded for up to 90 days after it is submitted. A small agency that downloads "now and then" eventually loses a form. You want a connection that pulls leads on a schedule with the campaign name, and you want to know how often it runs.
A clean export
Ask to see a full export of students with their notes and application history. Then ask whether it costs anything. If either answer is vague, your data is a hostage.
What you can safely skip until you grow
The enterprise tier is built for problems that arrive with headcount. Here is when each one starts to matter.
| Feature | Built for | You need it when |
|---|---|---|
| Territory or country-based routing | A UK desk and a Canada desk | Two people both take new leads and argue about who gets which |
| Approval chains | Franchise networks | A second branch has its own manager |
| Escalation to a manager on a missed follow-up | Large telecalling floors | There is a manager who is not also a counsellor |
| Custom objects and field builders | Internal IT teams | Your process has entities a study-abroad template lacks |
| Multi-branch dashboards | Owners who cannot walk over to ask | A second office opens |
| Applicant-facing portal | Universities running online applications | Students, not counsellors, fill the application forms |
| Dedicated implementation weeks | Migrations from another CRM | You have more than a few thousand records to map |
A useful rule: if a feature needs a person to administer it and you have no such person, it is a cost, not a capability. Vendors will not tell you this because the enterprise tier pays their commission.
A worked example: 120 leads a month through three people
Assume 120 leads a month, 40% reachable on the first day, and a 5% enrolment rate, which gives six enrolments a month. These are assumptions, not industry averages.
- Day 0. Twenty leads arrive from a weekend Instagram campaign. If Arun downloads the CSV on Monday, the youngest lead is already 36 hours old. If the CRM pulled them in on Saturday with the form name attached, Arun's Overdue list on Monday shows exactly which ones nobody touched.
- Day 3. Priya qualifies eight students and shortlists universities. Each shortlist becomes applications under the student, with a per-application deadline for the offer reply.
- Day 20. Two offers arrive on the same day for the same student. The CRM shows one conditional and one unconditional, and Sherin knows which one the visa file will rest on.
- Month end. Priya clicks "enrolled this month" and sees six names. If the list showed nine because three students had three applications each, she would stop trusting the report. A student should count once.
If late calls lose you one enrolment a quarter, that is four a year. Put your own fee against that number before deciding a subscription is expensive.
How to read a price list when you are five people
Small agencies over-pay in three ways.
- Per-seat pricing. Sherin works two days a week but needs a login, because a shared login breaks call attribution and audit trails. Per-seat plans make her cost the same as a full-timer, so agencies share logins and then cannot tell who called whom. Per-workspace pricing avoids the problem: everyone gets a login and the price does not change when the part-timer joins.
- Message and call charges hidden in the pitch. WhatsApp messages are billed by Meta or by your WhatsApp provider, never by the CRM. Cloud telephony adds per-minute charges and number rental; a SIM-based route has no per-minute charge. Ask for these separately so the subscription is not compared against a number that leaves them out.
- Onboarding and export fees. Both should be stated up front. A migration fee for a spreadsheet of 800 students is hard to justify.
Xale's plans are priced per workspace in rupees; the current pricing page lists what each includes. We do not print amounts in blog posts because they change.
A one-week setup plan
You do not need a consultant. You need a frozen spreadsheet and five focused afternoons. For the import step in detail, use our plan to move a consultancy from Excel to a CRM.
| Day | Do | Done when |
|---|---|---|
| Monday | Pick the study-abroad template. Rename stages to your words. Add the statuses you actually use (documents pending, conditional offer, deposit paid, visa filed). | A student can move from enquiry to enrolled without hitting a status that does not exist |
| Tuesday | Clean the sheet: one phone format with country code, remove duplicates, map columns to stages. Import active students first. | The import report shows which rows were skipped and why |
| Wednesday | Connect the WhatsApp number and the Meta forms. Send one test lead through each. | The test lead appears with its campaign name and the WhatsApp reply lands on its record |
| Thursday | Create three roles: owner, counsellor, visa. Set follow-up rules and the document folders you expect for every student. | Sherin sees visa-stage students; Arun sees his own leads; Priya sees everything |
| Friday | Go parallel: every new lead into the CRM only, the sheet becomes read-only. | Nobody has added a row to the sheet today |
| Next Monday | Review the Overdue list, the source report and a full export. | The export opens in Excel with notes and application history intact |
Two mistakes to avoid: importing closed history before active students (it doubles the cleaning work for no immediate benefit), and moving the Meta forms on day one (a broken sync on Monday costs you a weekend of leads).
Twelve questions for a thirty-minute demo
Ask the vendor to use a sample of your own students. Then ask:
- Show one student with three applications at different stages.
- Where does a passport live, and does the second application see it?
- How often do Meta leads sync, and does the campaign name come with them?
- Show a WhatsApp reply from the shared inbox landing on the student record.
- How are calls from a counsellor's own phone logged, and where does the recording come from?
- What does an iPhone user do for call recording?
- Show the Overdue list for one counsellor, and explain what "overdue" means by the calendar.
- Click a report number and count the list it opens.
- What can a part-time visa officer see, and what can she not see?
- Is pricing per seat or per workspace, and what changes when a sixth person joins?
- What are the WhatsApp and telephony charges, separately?
- Export everything now. Did it work, and did it cost anything?
How Xale handles this
Xale is our product, so weigh this section accordingly. A Study Abroad workspace starts with Inquiry → Qualify → Application → Deposit → Visa → Enrolled, with statuses for documents pending, conditional and unconditional offers, deposit and visa steps, all editable. Each university application is its own deal under one student record, and documents live in folders on the student, shared by every application. Meta Lead Ads sync about every 15 minutes with campaign and form attribution. WhatsApp runs through Meta's Cloud API (including Coexistence with the WhatsApp Business app) or an existing Wati, Gallabox or UrbanChat account in one inbox; Gallabox chats can't be answered from the inbox yet. 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, so Arun's and Sherin's dates never collide, and every report number opens the leads behind it.
The honest limits for a small agency: there is no applicant-facing portal, no pre-loaded university library (you import your own list), and no calendar or video-meeting integration. Pricing is a subscription per workspace, so a part-timer's login costs nothing extra. Read more on our study abroad CRM page, or the two call routes on CRM with call recording.
Frequently asked questions
Do we need a CRM with only three people, or is a spreadsheet enough?
A spreadsheet works while one person owns every student end to end. It stops working the moment two people share a student, because the chat, the documents and the call history split across two phones. If you run ads, the spreadsheet also depends on someone remembering to download leads before they expire. Three people with ads and two or more roles is usually the point where a CRM pays for itself.
Should a small agency choose per-user or per-workspace pricing?
Per-workspace pricing generally suits teams of one to five, because a part-time visa officer or a weekend telecaller needs a login of their own for call attribution and audit trails. Per-seat pricing pushes small teams into sharing logins, which quietly destroys the history you bought the CRM for. Whichever you choose, get WhatsApp and telephony charges quoted separately.
How long does it take a small agency to set up a CRM?
About a week of afternoons if you freeze the old sheet first. Configure stages and statuses on day one, clean and import active students on day two, connect WhatsApp and Meta forms on day three, set roles and follow-up rules on day four, and go live with the sheet read-only on day five. Closed history can be imported later, once the team trusts the live system.
Can we record calls without a call-centre setup?
Yes. There are two routes. The counsellor's own Android phone can sync each call to the right lead and attach the phone's own recording, with no per-minute charges. Or a cloud telephony number records calls on any phone, iPhone included, for a per-minute charge and number rental. Tell students calls may be recorded and take your own advice on consent.
What happens to our data if we stop paying?
Ask this before you sign, not after. A fair answer is a full export of students, notes, documents and application history that you can run yourself at any time, at no charge. Test the export during the trial by opening it in Excel and checking that notes and application stages survived. If the vendor can only export on request, treat that as a real cost of leaving.