Paediatric clinics · CRM
Keep one record per family so every child's next due date is in front of the desk.
A CRM for a paediatric clinic is a family contact record that holds parent details, children's dates of birth, consent to messages and the next due date. GullySales sets it up so the desk can recall children, with clinical notes kept in the clinic's medical records.
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.
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 paediatric clinics
Where it usually goes wrong, and what we would do.
“The unit is the family, not the patient”
A parent calls about one child and the clinic holds records for two. A record that links siblings, both parents and the grandparent who brings the child saves the desk from asking the same questions every visit and makes one reminder cover every child due.
“The CRM is not the medical record”
Diagnoses, prescriptions and examination findings belong in the clinic's own medical records. The CRM holds contact details, dates, consent and the source of the family. Keeping the two apart protects the child and keeps the data easy to manage. Data protection rules apply to both, so check with your own adviser.
“Consent is a field, not an assumption”
A parent who gave a number for the prescription has not agreed to marketing messages. A yes or no, with the date it was given and how, sits on the record and decides who receives a reminder. Without it, the recall list is a risk.
“When the desk changes, the memory should not”
A receptionist leaves and the knowledge of which families like an evening slot leaves too. A record that notes preferred language, usual caregiver and best time to call carries it forward, so a new person at the desk sounds as if they know the family.
What we do
What we deliver for paediatric clinics.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A family record layout
Fields for parents, children, dates of birth, languages, preferred caregiver contact and source, agreed with the doctor and the desk.
Result: One layout the desk can fill in a few minutes at registration.
A consent field and process
A recorded yes or no for reminders, with the date and the way it was given, and a simple way to withdraw.
Result: Every family on the recall list has a recorded yes.
Due-date views
Lists of children whose vaccine, growth check or follow-up is due, and those overdue, built from the dates on the record.
Result: On any morning the desk can open a list of children to call.
An import from the existing register
Moving names and dates from the paper book or old software into the new record, with duplicates and gaps listed for the desk to resolve.
Result: A clean starting list and a note of what could not be matched.
Rules for who sees what
A short sheet saying which roles can view, edit or export family records and how access is removed when a person leaves.
Result: Access matches roles and is reviewed whenever staff change.
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 paediatric clinic needs so each child's next due date sits in front of the desk.
- Family and the children linked to it
- Filled at registration. One parent record with several children means the desk sees every due date at the same call.
- Child's date of birth
- Filled at registration. It sets the vaccine schedule the doctor follows and the reminders the desk sends.
- Next due date and what it is for
- Filled by the doctor's note after each visit. It lets the desk list every child whose vaccine or review is due.
- Consent for messages
- Filled by the desk with the parent's choice of call or WhatsApp. No message is sent to a parent without it.
- Preferred language and contact person
- Filled at registration. A grandparent may bring the child, so note who to call.
Who it is for
This is written for these paediatric clinics.
- Single-doctor paediatric clinics
- Paediatric clinics with an in-house vaccination room
- Clinics run by a paediatrician and a child development specialist
- Newborn and neonatal follow-up clinics
- Paediatric clinics inside a polyclinic
- Clinics with a paediatric allergy or asthma focus
- Adolescent health clinics
- Home visit paediatricians
- Group practices attached to a maternity home
Before you decide
When this may not be the right fit.
- The desk and the doctor each keep a separate diary and will not enter dates in one place, so the system would hold half the schedule.
- You have no way to record a parent's consent for messages, so reminders would reach people who never agreed to them.
Before you decide
Agree the work. Know how to judge it.
CRM for paediatric clinics: 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 paediatric clinics. Anything missing is noted in the written scope, with who will supply it.
- The current register or software export
- The paper book or an export from the clinic software, with parents' names, children's dates of birth and phone numbers. Without it there is nothing to import.
- The doctor's rule on clinical notes
- A decision that diagnoses and notes stay in the medical record. Only the doctor decides. If undecided, the CRM holds contact details only. A line in the clinic's own policy file settles this for staff who join later.
- A consent line approved by the doctor
- The sentence the desk says when it asks for permission to remind. The doctor and the clinic's adviser approve it. Without it, reminders do not go out.
- A list of who may see the record
- Names of staff and their roles. If everyone shares one login, we need to know, because it changes the rules we can set.
- A retention decision for old records
- How long a child's contact record is kept after the last visit. Check with your own adviser. If undecided, nothing is deleted and the question stays open.
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
Look at the existing register with the desk
We see how the register or software works now: where the parent's phone number sits, whether siblings are linked, how a due date is noted. The receptionist shows us. You tell us what the desk would like it to do that it cannot. What exists afterwards is a list of what must be kept. We also note whether siblings are entered once or twice, since a duplicate family record is a frequent reason a reminder reaches the wrong person.
- 2
Settle what the record is not
The CRM is not the medical record. We agree in writing with the doctor that the contact record holds names, phone numbers, due dates and consent, and no diagnosis or clinical note. You decide where clinical notes continue to live.
- 3
Design the family record layout
The unit is the family. One record holds the parents, each child with a date of birth, the next due date and how the family wishes to be reached. We draw it on paper first. The receptionist tries it with three real families.
- 4
Add the consent field and its process
Consent to receive reminders is a field, and it is asked at registration. We write the line the desk uses and decide with the doctor what happens when it is not given. Reminders go only to families who agreed. A parent who declines reminders is marked so, and the desk does not ask again at the next visit unless the parent raises it.
- 5
Set the rules for who sees what
The receptionist sees contacts and due dates; the doctor sees whatever the doctor chooses. We write the rules down. You decide who can export the list, since it holds families' details.
- 6
Import the register and compare
The existing register is imported, duplicates are merged and a sample is checked by the desk against the paper. After a period of use we compare against the starting list: are the due dates current, and are consents recorded? You decide what to change, and whether the layout needs another field now that the desk has used it with real families.
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.
Do we need to buy new software?
Can the CRM store diagnoses?
What if parents ask us to delete their details?
How long should we keep a child's contact record?
What if a parent asks us to delete their details?
Can staff see a child's vaccine history in the CRM?
How much does it cost?
How long is the contract?
Who will actually do the work?
What do you need from us?
More for paediatric clinics
Related work to consider.
Closest to this: leads and follow-up
Also for paediatric clinics
Or start from the overview: sales and marketing for paediatric clinics.
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.