Guide · Example table
How can you track potential customer enquiries without losing the next step?
Replying to an enquiry does not finish its follow-up. If ownership and timing of the next step are unclear, the process can remain incomplete. A shared record structure may be enough to begin, rather than complex software. This guide covers new business and sales enquiries, not complaint management or technical support systems.
Make the next step visible instead of repeatedly asking “Who was going to get back to them?” Try the example below with one enquiry from your own work.
Answer three questions for every enquiry.
- 01Who owns this enquiry?
- 02What stage is it at?
- 03When will the next step happen?
Together with the source and last response, these answers prevent the record from becoming only a contact list.
An example tracking table you can copy
The sequence each record follows
- EnquirySource and ID
- OwnerWho has it?
- StatusShared definition
- Next stepWhat happens?
- Follow-up dateWhen?
| Enquiry ID | Source | Owner | Status | Last response | Next step | Follow-up date |
|---|---|---|---|---|---|---|
| EX-001 | Web form | Team A | Awaiting information | Day 1 | Check missing scope information | Day 3 |
| EX-002 | Team B | Meeting to be arranged | Day 2 | Confirm a suitable meeting time | Day 4 | |
| EX-003 | Phone | Team A | Assessment complete | Day 2 | Record the outcome and close | Day 2 |
No downloadable file or working CRM product is offered here; copy the structure into your own table.
Track status through shared definitions, not just notes.
Define what “new”, “awaiting a response”, “awaiting information”, “meeting to be arranged” and “closed” mean to the team. Moving a record forward should make clear who does what. Follow-up frequency and appropriate communication depend on the context; automatically messaging everyone is not a follow-up policy.
When is a table enough, and when does automation help?
If records are maintained consistently and the team shares one view, start with the table. If manual transfers between channels, repeated entry or missed reminders recur, assess the need for a connection or automation. Define ownership and rules first; AI does not resolve record ownership on its own.
Once the basic tracking structure is clear, improvements to repeated handoffs and reminders are easier to plan. PRIZMATION can help you assess that transition.
Respect data boundaries when adapting the example.
Record only necessary information and assess access for the people doing the work. Don't include private customer, patient or sensitive content in general examples or the contact form. In a clinic, this structure can explain administrative enquiry tracking and progress towards an appointment; it is not a substitute for a patient record or medical file. For clinics: Automation for dental clinics.
Let's find the point where follow-up gets lost.
Describe your enquiry sources and current tracking. Let's identify a first step towards a clearer workflow for your team.