Residential schools · CRM
Keep one record per family from the first message to the fee receipt.
A CRM for a residential school is the single list where every enquiry, visit, test and offer for a family is recorded with the next step and the person responsible. GullySales works on setting it up around your admission year and training the office to use it.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

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.
Also for residential schools
- Lead generation for residential schools
- Follow-up systems for residential schools
- SEO for residential schools
- Local SEO for residential schools
- Social media marketing for residential schools
- Content marketing for residential schools
- Buyer persona for residential schools
- WhatsApp marketing for residential schools
Sales and marketing for residential schools, the overview.
Last updated 14 Nov 2026.
For residential schools
Where it usually goes wrong, and what we would do.
“Admissions run on memory and notebooks”
The office remembers that one family visited in September and another asked about a mid-year seat. When the person who remembers is on leave, the family waits for a reply that no one else knows to send.
“A boarding enquiry passes through stages”
Enquiry, campus visit, entrance test, interview, offer, deposit and joining each need a different message. A record that shows the stage tells staff what to send next.
“Siblings, cousins and referrals link records”
A family joining a younger child after an elder one, or a cousin introduced by a current parent, is part of one network. The CRM records the link so the right person is thanked.
“A register nobody updates is worse than none”
If the office finds the system slow, it returns to paper. The set-up has to match how the desk works, with few fields and fast entry on a phone.
What we do
What we deliver for residential schools.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A pipeline built on your admission stages
Stages named in your own words, from first enquiry to joining, with the action due at each one.
Result: A board showing every family and the stage they have reached.
Standard fields for a boarding enquiry
Present class, city, board, reason for the move, who referred them and the preferred visit dates.
Result: Every record holds the same facts.
Connection to the website and WhatsApp
Forms and click-to-chat messages going straight into the CRM, so no enquiry depends on someone copying it.
Result: Website and WhatsApp enquiries appear in the list without retyping.
Reminders and task owners
Each record has a next step, a date and a named person, with reminders for the office.
Result: No family is left without a named person.
Training for the admissions desk
A session and a one-page guide for the staff who use the system daily.
Result: The office knows what to enter and when.
A season read-out
A report on enquiries, visits, tests and joinings read with the admissions head at the close of the cycle.
Result: A list of where families dropped out.
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
Keep these fields on every family record.
- Class sought and board
- Filled at the first contact. It lets the registrar see how many families are waiting for each class and which board they come from.
- Boarding or day interest
- Filled at the first call. It lets the hostel warden count likely boarders and the desk send the right pages.
- Stage: enquired, visited, tested, offered, paid
- Updated by the owning staff member. It shows the principal where families stop, so the next effort goes to that step.
- Referral link to current family
- Filled by the desk with the referrer's permission. It lets the school thank the family and see which parents bring in new ones.
- Sibling or cousin link
- Filled when known. It connects the records of related children, so the desk does not ask a family the same question twice.
Who it is for
This is written for these residential schools.
- Boys' boarding schools following ICSE or CBSE
- Girls' boarding schools with a hostel run by women staff
- Co-educational residential schools with separate houses
- Hill-station boarding schools with long-standing alumni
- Sports-focused residential schools and academies
- Residential schools for children of defence and transferred families
- Gurukul-style and values-based residential schools
- Residential junior colleges attached to a school
Before you decide
When this may not be the right fit.
- The desk does not yet agree on stages, and a tool would hold each person's private version of them.
- You plan to keep detailed notes about each child's health or behaviour in it, which needs its own care and policy.
- No one is named to keep the records current, and an out-of-date tool misleads more than a notebook.
Before you decide
Agree the work. Know how to judge it.
CRM for residential 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 residential schools. Anything missing is noted in the written scope, with who will supply it.
- Last season's enquiry notebook or sheet
- The existing record, however untidy, becomes the starting data. If the desk kept nothing, the CRM starts empty and the first season is spent building the habit, with no earlier figures to compare against.
- A list of who joined the school
- The names of families who took a seat last year, held by the accounts or admissions office. We use them to mark outcomes, and without them the record can show enquiries but not the paths that ended in a seat.
- A decision on which staff see what
- The principal, the admissions head and the desk need different views. The school must say who may read a family's notes, because a CRM with open access spreads private remarks about parents across the staff room.
- Time from the desk for training
- The people who will enter the data must sit with us on real calls. If they are only told how to use it afterwards, the register is abandoned by the second week of the season, so we ask the head to free the time.
- The school's data-protection practice
- Tell us how the school stores children's details and who approves new systems. We follow the school's rule and your own adviser's view on data about minors, and we do not decide it.
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
Draw the admission stages on a whiteboard
We meet the admissions head and the desk staff and draw the path of a boarding family as the school really handles it: first call, brochure, visit, entrance test, interview, offer, fee, joining. You tell us where the school differs from this order, such as a waiver or a board-specific form. The stages in the software come from this drawing, not from a template.
- 2
Decide the fields a boarding family needs
We list what the desk must record for every family: the child's class, the city, the deciding parent, the source and the next step with its date. You remove fields the school does not need and decide which details about a child belong in the record at all. Anything medical stays out and sits in the school's own file.
- 3
Move last season's enquiries into the new record
We take the notebook or spreadsheet the desk used and load it with the desk member, matching siblings and referrals as we go. The desk names the families who joined, so the record starts with real outcomes. Entries that cannot be matched are marked and left for the desk to resolve, not guessed.
- 4
Connect the form and the WhatsApp number
We link the website's enquiry form and the admissions WhatsApp number to the record and send test enquiries from a phone. The desk confirms that each arrives with its source label and a named owner. A message that lands without an owner is the failure we look for, and we correct the rule before the season begins.
- 5
Train the desk with real families
We sit with the desk and enter a day's calls together, then watch them do it alone. Reminders are tuned to the pace of the desk, not to a vendor's default. You decide who may see the full record and who sees only their own families, and the principal sees a summary.
- 6
Read the season against the starting record
At the close of the admission season, we read the record with the admissions head: how many enquiries became visits, tests and seats, and where families stopped. We compare it with the notebook totals taken before the software. You decide which stage or source needs a change for the next year.
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.
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.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
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.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Which CRM should a school use?
Can it hold information about the child?
Can the CRM hold information about the child?
Which CRM should a school choose?
Can the CRM be the same system as the school's fee software?
What happens if the admissions head leaves in the middle of the season?
How long is the contract?
How soon will we see results?
Who will actually do the work?
What do you need from us?
More for residential schools
Related work to consider.
Closest to this: leads and follow-up
Also for residential schools
Or start from the overview: sales and marketing for residential schools.
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.