Pharmacy colleges · CRM
Keep every student enquiry in one list from first call to fee paid.
A CRM for a pharmacy college is a single record of each enquiry, the programme it was for, who called, what was said and where the family stands. GullySales sets up the fields, stages and reminders so no enquiry lives only in a staff member's phone.
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.
For pharmacy colleges
Where it usually goes wrong, and what we would do.
“Enquiries live in six phones”
The principal's phone, the clerk's register and two consultants each hold part of the list. When the season ends, nobody can say who was contacted twice and who was never called.
“The same student asks for two programmes”
A student may enquire for D.Pharm and B.Pharm in the same week. Without one record, two staff call them with different answers.
“Stages differ by programme”
A D.Pharm enquiry moves from call to visit to fee. A B.Pharm enquiry has counselling and allotment in between. One pipeline for all courses hides where each programme stalls.
“A staff member leaves with the list”
If the person who handled counselling takes the contacts, the college restarts from nothing. The record has to belong to the college.
What we do
What we deliver for pharmacy colleges.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
A field list for admissions
Name, programme, source, parent contact with consent, stage, next action and reason for loss, kept short enough to fill in at the desk.
Result: Every enquiry has the same facts recorded.
Stages for each programme
A pipeline for D.Pharm, B.Pharm, Pharm.D and M.Pharm using the steps your office actually follows.
Result: You see where each programme loses families.
Reminders for the next call
A task attached to each record with a date and an owner, visible to the admissions in-charge.
Result: No enquiry waits because someone forgot.
Import from forms, calls and consultants
Web forms, WhatsApp enquiries and consultant lists brought into one place, with duplicates merged.
Result: The list is complete, not scattered.
Access rules and a data note
Who may see parent contacts, who may export them, and a plain note on how the data is held.
Result: The college controls its own student list.
Season reports for the principal
Enquiries, visits and joined students by programme and source, drawn from the record.
Result: The principal reads the intake from one screen.
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 desk needs to keep a pharmacy enquiry in one list.
- Programme asked about
- The counsellor selects D.Pharm, B.Pharm, Pharm.D or M.Pharm. It routes the enquiry to the right person and counts demand by programme.
- Qualification and subjects
- Entered at the first call from what the student states. It filters out students who cannot apply.
- Student and payer names
- Two fields: who studies and who pays. That keeps a reminder from reaching the wrong person.
- Counselling or entrance status
- Marks waiting, score received or allotted. It matches the reply to where the family stands.
- Campus visit status
- Booked, done, missed or declined. It shows how many visits become seats and where families drop out.
- Reason for not joining
- Chosen from a short list when the family declines. After a season it shows whether fees, distance or approvals decided it.
Who it is for
This is written for these pharmacy colleges.
- B.Pharm colleges attached to a trust or a medical education society
- D.Pharm institutes that mainly serve students from small towns
- Pharm.D programmes linked to a teaching hospital
- M.Pharm departments in pharmaceutics, pharmacology and quality assurance
- Pharmacy colleges inside a multi-faculty university
- Colleges in industrial belts near pharma factories
- Colleges that depend on management-quota admissions
- New pharmacy colleges that have not yet graduated a full batch
Before you decide
When this may not be the right fit.
- You get few enough enquiries to remember each one, so a new list would add typing and nothing else.
- Admissions staff will not enter data after calls, so the records would fill with blanks.
- Nobody has decided who may see student details, so settle access before any record is made.
Before you decide
Agree the work. Know how to judge it.
CRM for pharmacy colleges: 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 pharmacy colleges. Anything missing is noted in the written scope, with who will supply it.
- Every list of enquiries you hold
- We import what exists. Bring lists in whatever form: registers, sheets, consultant lists, phone exports. Duplicates are expected. Lists kept on personal phones are brought in with the owner's agreement. Photographs of handwritten registers are acceptable, because we type them in, and the source of each list is noted so that you can later compare the routes.
- The seat matrix and fee stages
- Stages follow your process, so bring the intake for each programme and the steps from enquiry to fee. Where steps differ for quota seats, mark them. Without this, the stages are drawn from guesses. A one-page note from the admission clerk describing the real order of work is better than a printed policy that nobody follows.
- A person to own the record
- Someone must add fields, remove users and tidy duplicates. Name them. Without an owner the record drifts within a season. The owner also decides when a family who has not answered is moved to lost, so the counts the principal reads are not inflated by cold records.
- A rule for students' documents
- Marks and certificates are kept in the college's own files, not in the CRM. Decide where they are held and who can open them. The CRM holds a note that a document was received. The CRM then links to the file by a reference number only, so a stolen login shows no mark sheets and a clerk who leaves takes no copies.
- Agreement from consultants on sharing lists
- Consultants who bring students may hold their own lists. Ask them what they will share and in what form. If they decline, their students are entered as they arrive. A consultant who wants credit for each student is told how the source label works, since a clear label is what lets the college show who brought whom.
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
Trace one family from the first call to joining
We follow a family from the first call or form to payment of the first fee, with the admission clerk and the counsellor. You tell us who touches each step. The path sets the stages the record must show, and where families vanish. The path is drawn on one sheet and checked with a family that joined, so the stages come from what happened to a real student and not from a template.
- 2
Choose the fields the admission staff will fill
We list the fields: student, parent, phone, programme, qualifying marks, district, source, last call. You strike what staff will skip. Fields about caste, religion or health are not on the list. Each field has a named person who fills it and a use for it later, and a field with neither is dropped before it clutters the first screen.
- 3
Set different stages for each programme
D.Pharm, B.Pharm and M.Pharm families move through different steps, so we build the stages for each with you. You approve the names. A stage means the same thing to every person who uses it. Quota seats, lateral entry into B.Pharm and the counselling route get their own stages where the steps differ, and the sheet marks which stage means a family has paid.
- 4
Load a few real enquiries and try them
We enter a handful of live enquiries from forms, calls and consultants and open them with two admission staff. You say what is missing or wrong. We load the whole list only when the shape is right. Duplicates, missing phone numbers and a district spelt three ways surface at this point, and we mend the rules for entry before they spread across the full list.
- 5
Test reminders for the next call
We set the reminder for the next call on five real cases and see where it lands. You name a stand-in so a reminder does not lie with one absent person. The test shows whether a family will be called on the day promised. We also check what the reminder shows the caller: the family's last question, the programme and the promise made, so the next call continues the last one and does not start over.
- 6
Switch from the registers and set access
We import the older lists from forms, consultants and registers and fix a date after which the old registers stop being the record. You name who sees what. Later we compare the stage counts with the baseline. Until the old registers are closed, the desk keeps writing in both places, and we show you the day the counts match so the registers can be retired with confidence.
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 software?
Who should have access?
Can the CRM message parents automatically?
Where should the college keep students' marks and documents?
Do we need paid software for the admission season?
Who enters the data when the admission office is crowded?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for pharmacy colleges
Related work to consider.
Closest to this: leads and follow-up
Also for pharmacy colleges
Or start from the overview: sales and marketing for pharmacy colleges.
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.