Imagine a parent submitting a school enquiry and receiving an immediate thank-you message. Three days later, nobody has called. The page worked, but the organisation did not complete the handover.
This is a hypothetical example of a common process gap: a form sends information somewhere, but no named person is responsible for the response. Before rebuilding the website, trace what happens after submission and make that work visible to the team.
Where enquiries usually get lost
- Form submissions go to a general email inbox that nobody checks daily.
- WhatsApp enquiries land on one staff member's personal phone. When that person is on leave, the messages wait.
- Nobody is clearly responsible for replying, so everyone assumes someone else has done it.
- There is no reminder when a follow-up is due.
- Nobody records what happened in the end, so management cannot tell whether the website is producing results.
Buying new software will not fix any of these on its own. Start by understanding how the work actually flows.
Map one enquiry from start to finish
Pick your most valuable type of enquiry: an admission, a membership application, a request for a quote, or a patient booking. Then write down, step by step, what happens to it:
- Where does it arrive? Website form, WhatsApp, phone call, walk-in?
- Who sees it first, and how quickly?
- Who replies, and within what time?
- What is the next step: a visit, a quotation, a payment, an appointment?
- Where is the final outcome recorded: enrolled, joined, bought, or lost?
Mark every point where the enquiry could sit without anyone acting on it. Those are the leaks to fix first.
Give every enquiry an owner and a deadline
Agree a few simple rules and write them down. For example: every website or WhatsApp enquiry gets a first reply within two working hours; the admissions officer owns admission enquiries and the bursar owns fee questions; if the owner is away, a named backup takes over.
Use a shared tool rather than personal phones and inboxes. A WhatsApp Business number shared by the team and a simple tracker in Google Sheets can work well for a small team. You can upgrade later, once the routine is working. Our guide on building a reliable WhatsApp reply routine covers this step in detail.
Test the journey before you buy anything
Ask a friend to send enquiries through the website, WhatsApp and phone, and time the responses. You will quickly see where things break.
If you are considering a CRM or a custom system, give suppliers your real scenarios, such as "a parent enquires on Saturday evening" or "a company asks for a quote for 20 staff", and ask them to demonstrate each one. Then let the staff who will use the system try it before you sign.
What managers should see every week
Four numbers are enough to start: new enquiries received, enquiries with no owner, follow-ups that are overdue, and enquiries that became a sale, admission or booking.
Illustrative example: an admissions office receives 80 enquiries in a month, replies to 64 of them within two hours (80%) and gets 20 completed applications (25% of enquiries). Now the school knows exactly where to improve: the 16 slow replies, and the full journey from first response to application. The totals alone do not show which applicants received a fast reply.
Collect only the information you need
A first enquiry rarely needs an ID copy, a full student record or a medical history. Ask for a name, a contact and what the person needs. Collect more only when the process actually requires it.
Decide who can see enquiry records, how long you keep them and how you back them up. The ODPC guidance on consent is a useful starting point. Health facilities should also read our hospital marketing guide.
When a connected system is worth building
A spreadsheet stops being enough when several teams handle the same enquiry, the volume becomes too high to track by hand, or management needs automatic reminders and reports. At that point a CRM, portal or connected system may justify the investment. Compare the cost with the expected time saved, the risks reduced and the value of improving follow-up. The process it supports still needs to be clear.
Try this today: send an enquiry through your own website and see how long it takes for someone to reply. That one test will tell you more than any software demonstration.
Zero Impulse designs websites and the digital systems behind them, from enquiry tracking to reporting dashboards. Tell us where your enquiries go after the form and we will help you map the journey.




