Three messages can be one enquiry

Sam sends a form, then emails about the same shelving job. Alex replies; Jo starts a quote. Give them one enquiry to work from, so neither assumes the other is following up.
Sam, Alex and Northline Home Services are fictional examples.
Make the stage mean something
- NewRequest received
- In conversationUseful reply sent
- Offer sentQuote shared
- ConfirmedConditions met
- ClosedReason recorded
When do you need a separate record?
One person can have several jobs; one job can produce several messages. Create a separate enquiry for a genuinely different request. Check the context before merging: a shared email address alone does not prove two records belong together.
Make the next step impossible to miss

Start with the free lead tracker
A CSV with the working fields and one fictional example. Open it in your spreadsheet tool, then replace the example.
Download the lead trackerOther fields and customer-data handling
Keep an enquiry ID, received date, contact route, request, source, stage, last useful contact and links to the quote or booking. Preserve the received date when another message arrives.
Use one controlled shared copy, accessible only to people who need it. A CSV does not provide permissions or an audit trail.
The ICO’s data minimisation guidance supports keeping information appropriate to the purpose. Record the job requirement, not unrelated personal details.
Closing a task is not a deletion rule. The ICO’s retention guidance does not set one period for every record. Set justified review points, consider applicable obligations and remove or anonymise data no longer needed. The guidance is marked under review; check it when setting your policy.
Make your follow-up easy to answer

Ask for the next piece of information the job needs. Explain what happens after the customer answers.
Adapt these examples. Check for replies and bookings before sending; respect requests to stop.
Enquiry follow-up or promotional message?
The ICO explains that purpose and content matter; adding promotion can change how a service message is treated. These are writing examples, not a determination of the rules for your message.
When the plan changes, reset the next step
Choose a situation. The aim is a visible action someone has accepted.
Two messages, one job
- Do first
- Check they concern the same request. Keep both messages under one enquiry.
- Record
- Keep the original date; name one owner.
- Done when
- Both colleagues see the same next action.
A reply arrives before a reminder
- Do first
- Pause the reminder and read the reply.
- Record
- Replace the stale task with a useful action and deadline.
- Done when
- No “we have not heard from you” message is queued.
The owner is away
- Do first
- Ask the covering colleague to accept the task.
- Record
- Record the cover owner and original customer promise.
- Done when
- Someone has accepted responsibility, not just received a notification.
The quote or booking changes
- Do first
- Check the current quote and booking before promising a slot.
- Record
- Link the accepted version; cancel outdated tasks.
- Done when
- Sales and delivery see the same confirmed plan.
The customer says “not now” or “stop”
- Do first
- Stop the active follow-up sequence.
- Record
- Record the reason and any specifically agreed later contact.
- Done when
- No unwanted sales reminder remains active.
Test the failure as well as the fix
Rehearse with fictional records. Include a failed notification and an owner who never accepts cover. Name the person who will resolve each failure; a log entry alone does not complete the task.
A booking needs an accepted handover

Sam accepts the quote. Before delivery takes over, check these five things:
- Agreed scope
- Confirmed date and location
- Accepted quote version
- Open questions, with owners
- Named person accepting the job
Link to one current booking record. Keep unresolved questions visible after handover.
Count the jobs, not the messages
A fictional week, at one review date
Each square is one enquiry. Three ticks are confirmed bookings.
The example also has 15 messages and five quotes. These are different counts, not extra enquiries.
Keep the denominator clear. Three bookings from five quotes is 60%; three from 15 messages is 20%. Those percentages answer different questions.
Make the comparison fair
Use the same group of enquiries and a stated review date. Compare groups that have had equal time to develop. Keep open enquiries separate from confirmed losses.
Also review overdue actions, unanswered requests and time to a useful response. State working or calendar hours. These fictional figures illustrate a method; they are not customer results or benchmarks.
Start small. Learn from one working week.

- Day 1 · MapTrace five enquiries. Find where ownership or the next step became unclear.
- Days 2–4 · TryUse the tracker. Rehearse a duplicate, an absent owner and a changed booking.
- Days 5–7 · ReviewRead unresolved records. Remove an unused field and agree the routine.
When is it time for a CRM?
Consider a CRM when duplicate conversations, simultaneous editing or missed handovers keep creating work. There is no universal enquiry-count threshold.
Ask a supplier to show capture, cover, a stopped reminder and a changed booking. Check the exception as well as the normal path.
Explore lead management software, CRM with booking or what to automate first.
Your daily lead follow-up checklist
Use this at opening or before the team signs off. The checkboxes stay in this tab only; they reset when you reload the page.
0 of 7 checks complete
Questions small teams ask
How should a small business track leads without a CRM?
Use one controlled tracker with an enquiry ID, request, owner, stage, last useful contact and dated next action. Keep one shared working copy rather than separate staff spreadsheets. The downloadable template gives you a starting structure; it does not provide access controls or an audit trail. Review unassigned and overdue work each day.
How often should I follow up with a lead?
Agree the next contact where possible and make each message useful: request a missing measurement, confirm availability or clarify a decision. There is no universal number of messages or waiting period. Record the agreed date, pause reminders when a reply arrives and honour requests to stop. Decide how unresolved enquiries will be reviewed and closed.
What if one customer contacts us through several channels?
Check whether the messages concern the same job before merging them. Link the conversation to one enquiry, preserve its original received date and assign one owner. A shared phone number or email address is not enough to prove identity. Keep genuinely different jobs separate so a new request does not disappear into an older booking.
What should be on a daily lead follow-up checklist?
Review unowned enquiries, unread replies, promises due today and overdue next actions. Check cover for absent colleagues and confirm that changed bookings reached the delivery team. Finish by recording closure reasons and stopping reminders that no longer apply. Count distinct enquiries, not messages, when reviewing how many requests became bookings.
When is it time to move from a spreadsheet to a CRM?
Consider a CRM when simultaneous editing, fragmented history or missed handovers keep causing work. Test a real workflow before choosing: capture an enquiry, change its owner, receive a reply, stop a reminder and hand over a confirmed booking. Check export access and permissions as well as the normal demonstration. A particular lead count alone is not a reliable trigger.
Sources and context
Published by HexaTech. The people, scenarios, illustrations and numbers are teaching examples, not reported customer results.
References and what changed
Checked 18 October 2026. The ICO principles guidance is marked under review. Confirm product capabilities in a demonstration.
This revision adds four original illustrations, shortens the reading path and moves supporting explanations into optional notes.
