The challenge
Global Edge runs eight study-abroad branches across India (Delhi, Mumbai, Bangalore, Hyderabad, Pune, Chennai, Kolkata, Ahmedabad) and one in Dubai. Each branch had been operating semi-autonomously, and the stack reflected it:
- Three different CRMs across branches (HubSpot, Zoho, and a homegrown PHP app from 2017)
- Eleven different WhatsApp numbers across the branches
- No central view for the founders — quarterly numbers came from a finance analyst stitching CSV exports
- Cross-branch lead theft — a counsellor in Pune occasionally messaged students originally captured by Hyderabad
By Q3 2025, the founders had decided to consolidate. They evaluated Salesforce (rejected: 6-month implementation, $$$$), HubSpot Enterprise (rejected: WhatsApp add-on pricing was punitive at their volume), and Xale.
Why Xale won the bake-off
Three reasons, in Sneha's words:
- "Branch-level data isolation was a real feature, not a hack." Xale's RBAC and tenant model meant we could give each branch their own workspace view while founders see everything. HubSpot's Team feature wasn't strict enough — UK counsellors could still occasionally see US records.
- "WhatsApp wasn't an upsell." Xale shipped WhatsApp Business native, with no per-message markup. At our volume (40k+ messages/month), HubSpot's add-on math didn't work.
- "The study-abroad module was already there." We didn't have to spend a quarter modelling universities, programs, IELTS bands, and visa stages on top of generic objects.
What we built
The migration ran over six weeks (most of which was data cleanup and stakeholder buy-in, not Xale work):
- Single workspace, eight branches configured with hard data isolation. Each branch has its own admin, its own counsellors, its own pipeline.
- Branch-aware lead routing — Meta Lead Ads from branch-specific Pages route to the correct branch automatically. WhatsApp inbound on the branch's number stays in that branch.
- Founder-level dashboard showing all eight branches side by side. Conversion rates, response times, counsellor performance, intake-mix, all comparable.
- CSV migration of ~80,000 historical leads across the three legacy CRMs.
- Approved WhatsApp templates rebuilt once and shared across branches with branch-specific variables.
- Single billing relationship replacing three different vendor contracts.
The outcome
After two quarters:
- All eight branches consolidated on Xale; PHP app and HubSpot decommissioned
- Tool spend reduced 55% (replacing HubSpot, Zoho, BSP WhatsApp, plus a few smaller tools)
- Zero cross-branch data incidents — data isolation is enforced at the query layer, not by counsellor discipline
- Quarterly reporting time dropped from 4 days (the analyst's stitching) to instant (founder dashboard)
- New branch onboarding time dropped from 6 weeks (the old setup process) to 2 days
What Sneha tells peer multi-branch operators
"Before Xale we operated like eight independent agencies that happened to share a logo. Now we operate like one company with eight regional teams. That distinction shows up everywhere — in our marketing buys, our hiring, our pricing power with universities."
The bigger picture
Multi-branch consolidation is the hardest problem in study abroad operations. The temptation is to either (a) leave each branch on its own stack and accept the chaos, or (b) bulldoze everyone onto a generic enterprise CRM and absorb 6 months of pain. Xale gives you a third path: a CRM that was designed for multi-branch from day one, where the isolation is in the engine, not the policy.
"Eight branches, full data isolation per branch, single workspace. UK counsellors can't see US leads. Branch managers run their own teams. Exactly what we needed."