Lead Routing for Multi-Campus Institutes

Multi-campus institutes rarely lose enquiries because of poor marketing. They lose them in the handover, a Pune enquiry landing with the Delhi counsellor, a B.Des query sitting in the MBA team's list, or a Tamil-speaking parent waiting for someone who can call back in their language. When every lead drops into one shared queue, the fastest-clicking counsellor picks the easy ones and the rest go cold. Lead routing fixes this by deciding, at the moment of capture, exactly who owns each enquiry.

Why one shared queue stops working

A single inbox is fine for one campus and one programme. Add a second campus, a dozen courses and two or three languages, and the same list now hides more than it shows. Counsellors cherry-pick, duplicate outreach annoys parents, and no manager can tell whether the Nagpur campus is actually being worked. The problem is not effort; it is that ownership was never assigned. Routing moves that decision from whoever gets there first to a rule you control.

Route by campus, programme and language

ASH captures leads from Meta, Google, your website forms, IndiaMART, Justdial and education portals, and every enquiry arrives tagged with the fields the source sent, such as campus, course interest, city and preferred language. You can route on any of these:

• By campus: a Pune location or landing-page tag sends the lead straight to the Pune counselling team.
• By programme: course-interest routing assigns a B.Des enquiry to design counsellors and an MBA enquiry to the management desk.
• By language: tag the preferred language on capture so a Marathi or Tamil enquiry reaches a counsellor who can actually converse.

Keep campus teams properly separated

Routing is only half the job; visibility is the other half. Each campus team should see its own pipeline, not the whole institute's. With role-based access, a Kochi counsellor works Kochi leads while the group admissions head sees every campus in one view. That separation keeps reporting clean and stops one campus's follow-ups from bleeding into another's numbers.

Automate the first response

Speed matters most in the first few minutes. With a no-code workflow, a newly created lead can trigger an instant WhatsApp acknowledgement, create a first-call task for the assigned counsellor, and notify the campus owner, before anyone opens the CRM. You are not promising an admission; you are making sure the enquiry is greeted and owned while interest is still high.

Getting started

Start with your busiest split, usually campus, and add one dimension at a time. Map each campus and programme to a team, set a fallback owner for anything unmatched, and let the workflow handle acknowledgement and task creation. Review the routing rules after a fortnight and adjust where leads are landing in the wrong place. See how this fits an admissions team on our education CRM page, or explore the full feature set.