Integrating Education Portals: Shiksha and Collegedunia

Counsellors lose more admissions leads to slow handoffs than to weak interest. An enquiry from a portal like Shiksha or Collegedunia is often at its warmest in the first hour, yet many institutes still receive those leads as an email that someone copies into a sheet the next morning. The ASH Education CRM is built to close that gap by giving portal enquiries a direct path into the same pipeline your counsellors already work.

How portal leads actually arrive

It helps to be honest about what these portals offer. Shiksha and Collegedunia do not publish a one-click push API you can simply switch on. They deliver enquiries by partner export or email, on their terms. What ASH provides is a live receiving endpoint, the education portals webhook, that those exports can be pointed at. You feed the portal's data into that endpoint directly, or through an email parser or a tool like Zapier, and from there ASH treats it as a first-class lead rather than an attachment sitting in an inbox.

Course mapping that drives routing

The education webhook does more than record a name and number. It reads the programme or course from the incoming enquiry and maps it onto the lead's course interest. That single field is what lets ASH send a design enquiry to your design counsellors and a management enquiry to a different desk, using the course-interest routing rules you set under lead settings. Get the mapping right once and the right counsellor is looking at the lead without a manager triaging anything by hand.

Deduplication, consent and scoring

Every portal lead runs through the same ingestion path as your website and Meta leads, so you get consistent behaviour regardless of source.

• Deduplication prevents the same student creating three records when they enquire on three portals.
• DPDP-aligned consent is captured with the lead so your outreach rests on a lawful basis.
• AI scoring gives counsellors a sense of which enquiries to call first.

Because the source is preserved as a tag, you can later see how Shiksha compares with Collegedunia in your reports without any manual tagging.

Setting it up sensibly

Treat the integration as a routing decision, not just a connection. Decide which programmes each portal sends, confirm how the portal exports to you, and point that export at the education webhook. Then check that your course-interest rules cover the programme names the portals actually use, since a mismatched course name is the most common reason a lead lands in the general queue instead of with the right counsellor.

Where it fits

Portal capture is one part of a wider admissions workflow that also includes an applicant portal, nurturing and reporting. If you are evaluating this for an institute, the Education CRM overview shows how capture, routing and follow-up connect, and you can pair it with nurturing sequences described in our guide on coaching nurture flows. The goal is simple: an enquiry from any portal reaches a counsellor while it is still warm.