Xale

Customer story · University admissions team

How Jain University's admissions team brings every enquiry into one pipeline

Xale connected Jain University's campus website, spreadsheet forms and Meta Lead Ads into one admissions pipeline, with qualification and programme fields, a deal per programme and role-based follow-ups.

  • On Xale since April 2026
  • Kochi campus
Xale CRM student record showing role-based follow-ups on one student: the counsellor’s follow-up at 11:30 AM about the budget call, the visa officer’s follow-up at 4:00 PM on the University of Leeds application after biometrics, and the telecaller’s follow-up the next morning, each with its own note.
The counsellor, the visa officer and the telecaller each keep their own follow-up on the same student. A real Xale CRM screen, shown with sample student data.

Jain University on Xale, at a glance

Campus website, spreadsheet form responses and Meta Lead Ads, with nobody copying enquiries by hand
Three channels, one pipeline
Each programme a student is weighing tracked as its own deal, with its own stage and owner
Per programme
Current qualification, programme of interest and the student's WhatsApp number, straight from each form
Every answer on the lead
Telecallers and counsellors each keep their own follow-up on the same student
Per role

What Xale did

What we built and moved for Jain University

  1. The website connector

    The campus website posts each submission to Xale's website connector, protected by an API key. A no-code field mapper matches the form's fields to the lead, and we tested the mapping against a sample submission before switching it on.

  2. The spreadsheet feed

    Form responses collected in a spreadsheet are posted to the same protected endpoint by a small script on the sheet, so they follow the website's mapping and rules and arrive as leads like everything else.

  3. Meta Lead Ads

    The campus's Page and ad account are connected, so leads from admission campaigns arrive with their campaign and form, and each form question maps straight to a field on the lead.

  4. Fields that match admissions

    Selector fields for current qualification (Plus Two completed, pursuing Plus Two or others) and programme of interest fill from the form answers and work as filters in the lead list and reports.

  5. Programmes as deals, work by role

    Each programme a student is seriously considering is its own deal, with its own stage, owner and payments. Telecallers work new enquiries, counsellors see the students assigned to them, and each keeps their own follow-up.

The story

The team

This is the admissions office at Jain University's Kochi campus. Telecallers make the first call on every enquiry, counsellors take interested students through programme choice, eligibility and fees, and a manager watches the whole funnel for campus leadership.

Enquiries arrive from several directions at once: the campus website's form, form responses collected in a spreadsheet, Meta lead ads during admission campaigns, walk-ins and referrals.

What they needed

  • One place for every enquiry. Website submissions, spreadsheet rows and Meta leads had to land as leads without anyone copying them across.
  • Every form answer on the lead. Students and parents prefer WhatsApp, so the number typed into a form had to reach the lead along with the student's qualification and the programme they asked about.
  • Clear ownership. Telecallers call new enquiries and counsellors own interested students, each seeing their own work.
  • Each programme choice on its own. A student may weigh more than one programme, so each choice needed its own stage, owner and payments.

One pipeline for every channel

The campus website posts every submission to Xale's website connector, protected by an API key. We mapped the form's fields to the lead with the no-code field mapper and tested the mapping on a sample submission before switching it on. The spreadsheet responses post to the same endpoint through a small script on the sheet, so both channels follow one set of rules.

For admission campaigns, the campus's Meta Page and ad account are connected. Leads arrive with their campaign and form, and every form question lands in a field. Selector fields for current qualification and programme of interest fill from those answers, so the team can filter the lead list, and the reports, by either one.

How the team works

A telecaller starts on the dashboard, with follow-ups split into Overdue, Today and Later. Each call ends with a status and the next follow-up date. Once a counsellor picks up a student, they keep their own follow-up without disturbing the telecaller's, and due follow-ups reach them as a browser popup, a mobile push and an inbox alert.

When a student settles on a programme, that programme's deal moves on with its own stage, owner and payments, while the student's other choices stay where they are. When a student enquires again, the enquiry is logged on the original lead and the people working that lead are alerted, instead of a duplicate starting from zero.

The manager works from reports: which sources bring enquiries, how far those enquiries get, and which programmes they end up in. Any number opens the list of students behind it, and each person sees only what their role allows.

Timeline

How the work ran

  1. April 2026

    Jain University's admissions workspace goes live, with the campus website and spreadsheet forms feeding enquiries into it.

  2. August 2026

    Qualification and programme-of-interest fields added, with form answers mapped straight into them.

In the setup

What runs in the workspace

  • Website connector
  • Spreadsheet form feed
  • Meta Lead Ads
  • Qualification and programme fields
  • A deal per programme
  • Payments on deals

The product behind it

Read how each part works