Skip to content
GullySales

ICSE schools · CRM

Keep every admission enquiry in one record, from first call to the first day of school.

A CRM for an ICSE school is a shared record of each family's enquiry, visit, assessment and offer, so nothing depends on one person's memory. GullySales sets up the fields, stages and reminders, and trains the office to use them.

Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

A prospective student speaks with a university admissions adviser

What CRM means

A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.

Last updated 14 Nov 2026.

For ICSE schools

Where it usually goes wrong, and what we would do.

  • “The register is a notebook on one desk”

    When the admissions clerk is on leave, the enquiries on that desk wait. A shared record lets anyone in the office see where a family stands and what was last said.

  • “The principal's memory is the follow-up system”

    A principal who answers serious enquiries personally holds details in their head. A note after each call, entered by the office, keeps the follow-up going when the principal is in class or at a meeting.

  • “Stages differ for a school”

    A school sale runs through enquiry, campus visit, assessment, offer, fee and joining. A generic sales tool has stages that mean nothing here. The stages should match the steps a parent actually takes.

  • “Child and parent are one record”

    A family may have two children, or return a year later for a sibling. A record that links siblings and previous enquiries saves the office from asking the same questions twice.

What we do

What we deliver for ICSE schools.

The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.

  1. Fields and stages for admissions

    Fields for entry class, current board, source and stage, set to match your admission process.

    Result: Each enquiry shows its class, source and current step.

  2. A tool choice that fits the office

    A recommendation between a sheet and a CRM tool in ordinary use in India, based on staff and budget.

    Result: The office uses a tool it can maintain.

  3. A routine for entering enquiries

    A rule for who enters each call, form and walk-in, and by when it must be on record.

    Result: Every enquiry has an owner and an entry.

  4. Reminders for next steps

    Task reminders attached to each record, such as a call after a campus visit.

    Result: No visit ends without a next step on the record.

  5. A sibling and alumni link

    Fields that connect brothers and sisters and flag alumni families.

    Result: The office sees at once that a family already has a child in the school.

  6. A reading of the pipeline

    A plain summary of how many enquiries sit at each stage, prepared for the principal.

    Result: The principal can see where families wait.

How the result is measured

  • Enquiries logged in the CRM
  • Data completeness
  • Reports generated from CRM data

Recorded as a baseline before work starts, so every later report has an honest comparison.

Fields worth keeping

Fields an admissions office keeps for each family.

Child's name, class applied for and date of birth
Entered at the first call. It tells the office the eligibility and the right form for the class.
Current school and board
Entered by the office. It shows who is a board-change family and needs the bridging note.
Stage of admission
Chosen from a fixed list, such as visit, form, assessment, offer. It lets the principal see where each family waits.
Promises made on the call
Entered by whoever spoke to the parent. It prevents a second person from giving a different answer.
Sibling and alumni link
Entered at the first call, so the office knows the family is already known to the school.

Who it is for

This is written for these ICSE schools.

  • Long-established ICSE day schools run by a society or a church
  • ICSE schools with ISC classes for Class 11 and 12
  • ICSE schools for boys or for girls only
  • ICSE residential and boarding schools
  • Newer private ICSE schools in growing suburbs
  • ICSE schools run by a community trust
  • ICSE schools attached to a larger educational group
  • ICSE schools with a strong sports or arts programme

Before you decide

When this may not be the right fit.

  • Only the principal handles enquiries, and a record would be one more thing for an already busy office.
  • You have a small number of admissions each year and the register already tells you each family's status.

Before you decide

Agree the work. Know how to judge it.

CRM for ICSE schools: use these checks to prepare, choose the scope, and review what changes.

Bring the right evidence

List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.

Make the scope clear

Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.

Check the work in use

Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.

Know when to change course

If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.

These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.

Before we start

What to have ready before the work starts.

The records, access and decisions this work needs from ICSE schools. Anything missing is noted in the written scope, with who will supply it.

The old admission register in full
We need the register for the last cycle, in any form, including loose forms clipped together and a diary of visits. It is loaded as history, so that a returning family or a younger sibling is recognised at once. Without it the CRM starts empty and the first cycle gives little to read it against.
A decision on who sees parent data
The principal must decide who may read and who may edit records, since they hold family details. Keep it narrow. If undecided, we set read-only access for the wider staff and give editing to the front desk and the admissions head.
A named owner of the CRM
One person, from the office, must own the fields, the entries and the clean-up. They need authority to correct colleagues, to merge two entries for one child and to close a stale record. Without an owner, the record drifts within a season, and the reminders begin to point at families who have already joined.
The school's data consent wording
The form that parents sign should say how their details are used, how long they are kept and who in the school may see them. Check it with your own adviser. We need to see it, so the CRM follows it and no field collects what the form does not cover. If it is missing, we advise holding off any messaging from the CRM.
A list of staff who will use it
Please name the office staff, the admissions head and anyone who takes calls, including a reception temp who covers lunch. They are trained together, so that the habit is the same at every desk and nobody learns it second-hand. If the list is missing, training reaches one person and the others keep the notebook.

How it works

How the CRM work runs

The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.

  1. 1

    Follow one family from enquiry to offer

    We trace one family through the office as it happens today: the phone call, the notebook entry, the visit, the assessment, the offer letter. You and the front desk show the real register. The trace shows what the record must hold, who writes it and where the information is lost between desks. We note the paper that travels with the family, such as the transfer certificate request and the application form, since the record must point to them.

  2. 2

    Name the stages of an admission

    We agree the stages a family passes through: enquiry, visit, assessment, offer, acceptance, closed. You set the names and strike the ones the school does not use. The stages decide the reminders and the reading of the pipeline, so they are described in the office's own words. A family whose child is waiting for a seat gets a stage of its own, so the waitlist is visible and is not mixed in with families who are still deciding.

  3. 3

    Choose a tool the office will open

    We compare a shared spreadsheet and a simple CRM against the staff who will use it and the data you hold. You decide. A tool the front desk finds hard will be dropped, so we choose the simplest that holds the fields, reminders and the sibling and alumni link. Cost, the school's data rules and who will support the tool after we leave are put in front of you in plain terms before you choose.

  4. 4

    Load last year's families and set the fields

    We build the fields: child, entry class, parents, source, stage, next step, date. Then we help copy the previous cycle's register into it, with you checking the unclear entries. Child and parent are one record. Anything doubtful is left blank, not guessed. Where two siblings share a parent, the entries are linked so the office sees the family once, and alumni parents are marked so the principal can greet them as such.

  5. 5

    Train the office on real enquiries

    The front desk enters a few live enquiries with us beside them. We watch where they hesitate and adjust the fields, dropping any that slow the call. You decide who may see and change records, and who may export the list, which we keep to the fewest people. A one-page guide stays at the desk, covering the entry made after each call and a look at what is overdue.

  6. 6

    Read the pipeline against the first figures

    After an admission cycle has run through the CRM, we compare enquiries by stage, visits booked, offers made and families lost with the figures from the old register. You decide what to change in the stages or the habit. We report what the pipeline shows and promise no admissions.

Where this fits

Three pieces of sales work, in this order.

This work sits inside sales management. A target, a review routine and someone who owns the number.

  1. Step 1

    Sales audit

    Find where deals are being lost and what to fix first.

    Start here if you cannot say where orders are lost.

  2. Step 2

    Sales process design

    One written way to sell, from first enquiry to repeat order.

    Start here if every salesperson sells differently.

  3. Step 3 · you are here

    Sales management

    A target, a review routine and someone who owns the number.

    Start here if the team has targets and no routine.

Tell us what you need Your brief is read before we call. Scope, fee and term in writing.

FAQ

Questions owners ask before they call.

Not here? More answers, or ask on WhatsApp.

Is a spreadsheet enough?
For a small intake it can be, if one person owns it and the columns are fixed. A CRM tool earns its place when several people handle enquiries.
How do we keep parent data safe?
Limit access to the staff who need it, protect logins and collect only what admissions needs. Confirm your duties around parents' personal data with your own adviser.
Who should own the CRM?
A named person in the admissions office, with the principal reading the summary. Shared ownership leaves the records half-filled.
How do we keep parent data safe in a CRM?
Limit access to the admissions staff and the principal, use individual log-ins and keep sensitive documents out of the record. Rules on children's data differ, so check with your adviser. A shared password turns one lost phone into a leak.
Do we need to buy software at the start?
Not necessarily. A shared spreadsheet with fixed columns, protected cells and a reminder column serves a school with a modest number of enquiries. Software becomes worth its cost when several people update records at once or when reminders must reach different staff. We tell you when the spreadsheet stops being enough and what the software must do better, and you decide with the facts. We never move your data without your approval.
What happens to families who decline an offer?
They stay in the CRM with a closed stage and a reason, if the parent gave one. The record helps the school understand why families go elsewhere and whether to approach them again for another child. Parents who ask to be removed are removed. We set the rule for how long records are kept with your adviser, and we do not choose it for you.
How much does it cost?
There is no price list, because the work differs by business. The fee is scoped after we have read your brief and spoken to you, and put in writing before anything starts, split into our time, your media spend and production.
How long is the contract?
The term is agreed in writing after we have spoken, along with the fee and the reporting. It is never a default twelve months, and renewal is decided on the numbers against the baseline recorded at the start.
How soon will we see results?
It depends on the trade, the channel and what is already in place. After we have read your brief and spoken to you, we say what we would expect to move first and how it will be measured against the baseline. Nothing here is guaranteed.
Who will actually do the work?
The person you speak to before anything starts. We work from one office in Nagarbhavi, Bengaluru, with no account managers in between.

Your next practical step

Tell us what you are trying to grow, and we will read it before we call.

Eight short steps, mostly taps. Skip anything you would rather answer on the call.