General hospitals · CRM
Keep one record of every enquiry, from the first call to the follow-up visit.
A CRM for a general hospital is a simple register of enquiries, referrals and patients due a follow-up, kept where the whole front desk can see it. GullySales sets up the fields, the stages and the habit of entering a call, without storing clinical records in 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.
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 general hospitals
Where it usually goes wrong, and what we would do.
“Calls and messages are written on paper or nowhere”
An enquiry for a surgery comes on the phone at one desk and by WhatsApp at another. Neither is written in a shared place, so a family that called twice is treated as new both times.
“The hospital system records admissions but not enquiries”
Billing software notes who was admitted. It does not record the family that asked about a hernia surgery and never came back. Without that, nobody can see how many enquiries are lost or why.
“Patient data needs care”
A CRM holds names and phone numbers, and health details raise privacy duties. Keep the CRM to contact details and the reason for the enquiry, and keep clinical notes in the hospital's own medical record system.
“A notebook beats a system the ward staff skip”
A system with thirty fields will be skipped by a busy night nurse. The set-up has to be short enough to fill in during a call, with the few fields the administrator actually reads.
What we do
What we deliver for general hospitals.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A short enquiry form
A few fields: name, phone, reason for the enquiry, source, who took the call and the next step.
Result: An enquiry takes under a minute to enter.
Stages that match your hospital
Stages such as new enquiry, called back, OPD booked, admitted and follow-up due, named in the desk's own words.
Result: Each enquiry sits at a stage the desk recognises.
Source and referrer fields
A field for how the patient heard of you and who referred them, feeding the admission source record.
Result: The administrator can read enquiries by source.
Access and privacy rules
A note on who may see which fields, how phone numbers are stored and what is kept out of the CRM.
Result: Clinical details stay in the medical record.
A tool chosen for your desk
A suggestion from tools in ordinary use in India, a shared sheet or a simple CRM, based on how many people enter data.
Result: A tool the front desk will actually open.
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 for an enquiry record that a desk will actually fill.
- Caller name, number and the concern
- The desk enters it in a minute. It replaces the paper note that gets lost at shift change.
- Source and referrer
- Doctor, chemist, lab, camp or Maps. It shows which source fills the wards and who deserves a thank-you.
- Stage
- Enquired, visited, admitted, discharged or follow-up due. The coordinator updates it, and it shows where families fall away.
- Scheme or insurance named
- A short field showing what the family asked about. The administrator reads it to see which approvals matter most.
- Reason for not returning
- A single word entered after a follow-up call. It tells the hospital whether cost, distance or care was the barrier.
Who it is for
This is written for these general hospitals.
- Taluk and small-town private general hospitals
- Hospitals run by one or two doctors with an in-house casualty
- Charitable trust and mission general hospitals
- Hospitals empanelled under state and central health schemes
- Industrial-area hospitals serving factory workers and ESI beneficiaries
- Neighbourhood hospitals in city wards with a ground-floor pharmacy and lab
- Hospitals with a small maternity and paediatric unit
- General hospitals expanding from a clinic into inpatient beds
Before you decide
When this may not be the right fit.
- The tool would hold reports and clinical notes that the hospital system already stores.
- Nobody at the desk has agreed to enter calls.
- You plan to buy software before a notebook-style record has been tried.
Before you decide
Agree the work. Know how to judge it.
CRM for general 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 general hospitals. Anything missing is noted in the written scope, with who will supply it.
- The sheets and notebooks the desk uses now
- We cannot design a register until we see current practice. Send each sheet or notebook page with patient details covered. Without them, the first form is a guess. A notebook with crossed-out entries and half-written phone numbers tells us as much as a clean sheet.
- A named owner of the register
- One person should keep it accurate. Name them. Without an owner, it falls out of date within a few weeks, and the family who was promised a call finds nobody has the number. The owner is also the person who tells us when the desk finds a field useless.
- Devices and logins at the desk
- The register must run on the phones and computers the desk has. List what is available. Where the desk has no device that suits, we begin on paper and a sheet. A desk that works on a shared computer with one login is told so that we can set rules that fit it.
- A privacy rule from the administrator
- The hospital decides who sees contact details and who may export them. Give us a short note. Without one, we keep the register to name, phone and reason for call. We also ask whether the register may be opened on a personal phone, because that decides where the data can be exported to.
- A decision on who enters data
- Busy hours leave no time for entry. Tell us who will enter and when. Without that, entries are made in batches and the follow-up dates lose value.
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
See where enquiries are written now
We look at the desk register, the phone notebook and the WhatsApp chats where families first reach you. You tell us what the desk already keeps current. What exists afterwards is a list of what must move into one register and what can stay where it is. We also note which chats are on staff phones and not on the hospital number, since those enquiries are the easiest to lose.
- 2
Shape stages around a family's path
With the desk, we set stages in the hospital's own words: enquiry, appointment, visit, review due, did not return. You cut any stage the desk will not update. The list that remains is short enough to keep up during a busy OPD. A stage for a patient who asked not to be contacted is included from the start.
- 3
Design the enquiry form for the desk
We write a form with the name, the phone, the reason for call and the source, and nothing about the illness beyond what the desk needs. A doctor reads it. The form can be filled in as the caller speaks.
- 4
Load the existing sheets and clean duplicates
We bring your present sheets into the register and merge duplicate families with your help. We keep only what the desk needs. Anything about diagnosis or reports stays in the hospital's own patient record. Families who appear under two phone numbers are merged only when the desk confirms they are the same.
- 5
Set access and privacy rules with the administrator
You decide who may see which part. We write a one-page rule: who can open the register, who can export it, who removes access when someone leaves. The rule is read by each user. The rule also says what is done with a phone that is lost, since the register may be open on it.
- 6
Read the register against admissions
After the desk has used the register, we compare enquiries, appointments and returns with the starting figures. You tell us what the desk finds hard. We simplify the form before anyone relies on the numbers.
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 paid CRM software?
Can we keep patient reports in the CRM?
Who should enter the data?
What if the desk finds data entry a burden?
Can we store patient reports and diagnoses in the register?
How do we treat a patient who asks to be taken off the register?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for general hospitals
Related work to consider.
Closest to this: leads and follow-up
Also for general hospitals
Or start from the overview: sales and marketing for general hospitals.
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.