Skip to content
GullySales

Children's hospitals · CRM

Keep one record of each family, so the desk knows the child, the doctor and the next dose.

A CRM for a children's hospital is the system that holds each enquiry, family and referral in one place, so nobody asks a frightened parent to repeat themselves. GullySales sets up the fields, stages and reminders around your front desk, vaccination clinic and referral log, with consent recorded.

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

Realistic editorial illustration of hospitals at work in India

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. Rules for this trade differ by state and professional body, and they change. We describe restrictions in general terms, so check the current position with your own council or adviser before you publish anything.

For children's hospitals

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

  • “The hospital system records visits, not relationships”

    A hospital management system holds bills and case sheets. It rarely holds the enquiry that never became a visit, the school that asked for a talk or the doctor who referred. A CRM keeps those next to the family.

  • “A family has several children and several reasons to return”

    A mother may bring a baby for vaccines and an older child for asthma. Records kept by child but linked by family let the desk greet the parent by name and see what is due for each child.

  • “Consent has to travel with the record”

    A reminder may only go to a parent who has agreed to it. The consent, the date and the channel need to sit on the record so any staff member can check before a message goes out.

  • “Staff change, notes should not”

    When a front desk executive leaves, the notes in a personal phone leave too. A shared record with clear stages means the next person continues the conversation rather than starting again.

What we do

What we deliver for children's hospitals.

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

  1. A simple structure for families, children and enquiries

    A set-up where a family links to each child, each enquiry has a source and a stage, and referrals are tied to a doctor.

    Result: The desk sees the family and the child on one screen.

  2. Stages for emergency, OPD, vaccination and surgery enquiries

    A short list of stages for each kind of enquiry with a named owner for each.

    Result: No enquiry sits without someone responsible.

  3. Consent fields and a reminder check

    Fields for consent, channel and date, with a rule that the desk checks them before a reminder or message is sent.

    Result: Messages go only to parents who have agreed.

  4. A referral register

    A sheet or module listing which doctor, school or nursing home sent which child, with the date and what was sent back.

    Result: Referral sources are visible and thanked.

  5. Staff training on entering records

    A short session and a one-page guide for the front desk on what to record, in what words and what never to record.

    Result: Records are entered the same way by every shift.

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

The fields a children's hospital's list needs, and who fills each.

Parent or guardian contact
The adult who agreed to be contacted, with relationship, filled at registration and linked to each child.
Child's age band
Newborn to adolescent, chosen by the desk so the right reminders and guides go out.
Next vaccination due
A date from the doctors' schedule, used by the desk to build the due-list.
Referring doctor
Entered at booking for the note back and the referral register.
Reminder consent
Yes or no, with the date and channel the parent agreed to.

Who it is for

This is written for these children's hospitals.

  • Standalone children's hospitals with paediatric emergency
  • Women and children hospitals that also run maternity
  • Paediatric multispeciality hospitals with surgery and subspecialties
  • Hospitals with a NICU and PICU taking referrals from nursing homes
  • Neighbourhood children's hospitals with a strong OPD and vaccination clinic
  • Hospitals with developmental paediatrics and child therapy units
  • Children's wings inside general or multispeciality hospitals
  • Charitable children's hospitals serving referral cases

Before you decide

When this may not be the right fit.

  • The hospital system already holds all visits and no one will update a second list; use that.
  • You want the CRM to hold diagnoses; they stay in the hospital record.
  • Registration staff are not trained to enter the records, so entries would be missing.

Before you decide

Agree the work. Know how to judge it.

CRM for children's hospitals: 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 children's hospitals. Anything missing is noted in the written scope, with who will supply it.

A list of who may see which records
Write down who at the hospital should see family contact details, who should see visit reasons, and who should see nothing at all. We set the access to match. The list also records who may export records, since a spreadsheet downloaded to a personal laptop leaves the hospital's control. Without a clear list, we give the narrowest access and widen it only when you decide, which may slow the desk for a short while at the start.
The hospital's data and privacy policy
Bring the policy or consent form the hospital uses today for patient information. The CRM must follow it, and we will not store anything the policy does not allow. If the hospital's own advisers have already approved a consent form, we use its exact words in the consent field. If none exists, we advise you to have your own counsel write one first, and we hold off on storing any health detail until it is in place.
A sample of today's enquiry paper or sheet
Show us the register, the slip or the sheet where the desk notes an enquiry now. We copy the structure that works and drop what does not. A photograph of one page is enough, with the names hidden, because we are copying the habit and not the data. Without a sample, the fields are our guesses, and the desk may find them awkward and go back to the notebook within a few days of the launch.
A decision on which tool to use
Tell us whether the hospital already pays for a CRM, a spreadsheet or the billing system's own module, and who signed for it. We fit the structure to what exists first. If the choice is a spreadsheet, we set it up with locked columns and a single owner, so that it does not become several versions. If nothing exists, we suggest a simple tool and you decide, since the hospital must own the data and the login.
A named person to keep the records tidy
Someone in administration must check on working days that new records are complete, duplicates are merged and consent fields are filled. The person need not be technical, only careful, and a half-hour on working days is enough. Without that person, the system fills with half records within a season, and reminders go to families who never agreed to them, which is the exact harm the consent field exists to prevent.

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

    Map how an enquiry travels now

    We follow a real enquiry through the hospital, from the first call or message at the desk, to the doctor, to the billing counter and back to a follow-up. We note which paper, register or phone holds each fact along the way. You walk us through one case from your own records, with the names hidden, so that we see the real route.

  2. 2

    Define a family and a child record

    We agree on how one family with three children is held, with the parent as the main record and each child linked under it, and the reason for each visit noted. You decide which fields the hospital is willing to hold in a CRM and which stay only in the hospital system, because clinical detail has no place in a sales tool.

  3. 3

    Set stages for emergency and planned care

    Emergency, OPD, vaccination and surgery enquiries move through different stages, so we set a short list of stages for each, using the words your desk already uses. We also agree who moves a record from one stage to the next, so that the desk and the nurses do not both change it. You approve the stage names, and the desk tries them on live enquiries before they are fixed, because a stage nobody understands will be skipped within a few weeks.

  4. 4

    Add consent fields to every record

    Every family record carries a field for whether the parent agreed to reminders, in which language and by which channel, with the date and the person who recorded it. Families who decline reminders are marked clearly, and the desk can still record their visits and enquiries without any message being sent. You tell us who in the hospital may change that field, and no reminder goes to a record without it, whatever the doctor or the desk would like to send.

  5. 5

    Start the referral register inside the system

    The family paediatricians and nursing homes who refer children get their own records, linked to the enquiries they sent. You name who keeps it. We also record the date of each referral, so that the register shows a pattern across the year and not just a total. We show that person how to log a referral from a phone call, and how the register shows which doctors have stopped sending children, so that someone can ask why.

  6. 6

    Train the desk and read first results

    We train the desk and the nurses on entering a record, one role at a time, and later review the records against the call counts recorded before the work began. A short printed sheet beside each desk lists the fields in the order the call follows, and the nurse in charge corrects it after the first few days. You see how many enquiries are now captured, where fields are left blank, which stages are crowded and what to simplify so that the habit holds.

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.

Which CRM should a children's hospital use?
One the front desk will actually open every day. Some hospitals use their existing hospital software with an added module, others use a simple tool such as a spreadsheet or a commonly used CRM. We choose after seeing your workflow and data rules.
Is it safe to store children's health details in a CRM?
Keep clinical details in the hospital system and store only what the desk needs for contact and reminders. Health data carries legal duties, so agree the fields and access with your own adviser before anything is stored.
Who should see the records?
Only staff who need them for their job. Set access by role, so the front desk sees contact and consent, the vaccination clinic sees schedules, and the administrator sees counts and sources without reading individual families.
How should a family with three children be recorded?
One family contact linked to three child records, each with its own age band and due dates. The parent receives one message about the child who is due, not three. The desk sees the link on one screen.
Does the CRM replace the hospital information system?
No. The hospital information system holds clinical and billing records and stays the source for them. The CRM holds the relationship around the visit: who enquired, which service they wanted, who referred them, whether they agreed to reminders and what the next contact is. Where the hospital later moves to a larger system, the structure we set up can be exported, because the fields and stages are written down. Clinical notes, test results and diagnoses do not belong in it, and we keep the two systems separate by design so that a mistake in one does not spill into the other.
What happens when a staff member who kept the notes leaves?
The notes stay, because they live in the hospital's record and not in a person's phone or notebook. We write a one-page guide on how a new person picks up an open enquiry, and the access of the departing member is removed by the person you name. A copy of the stage names and field meanings stays in the shared folder, so a new person is not dependent on someone's memory. This is the reason we ask that every follow-up note be written in the record itself and never in a private chat or on a loose slip.
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.