Stop losing enquiries: a simple follow-up system before you buy a CRM

Someone asks for a quote. You answer between jobs, promise to check your schedule, and forget to reply. A new app only helps if it makes that unfinished promise visible.

Start with one list and one reminder routine. A spreadsheet can work for an owner who handles their own enquiries. A CRM, short for customer relationship management software, becomes useful when you need shared ownership, connected email history, or automatic reminders that your current process cannot reliably provide.

Give every enquiry a next action

Use the Leads tab in the downloadable workbook. It includes fictional examples and blank rows you can replace with your own records. The supplied tab assumes one owner handles the list. If sharing it, add an Owner column and make responsibility for each next reply explicit. Keep these fields:

Field	What to enter
Lead ID	A stable reference, such as L001. Keep it when you sort the sheet.
Name and contact	Enough information to reply. Avoid collecting details you do not need.
Source	Website form, phone, referral, Google, or another source you can recognize.
Request	A short description of the customer’s actual job.
Stage	New, Contacted, Quoted, Won, Lost, or Waiting.
Owner, for a shared list	Add who is responsible for the next reply. In the supplied solo-owner template, that is you.
Last contact	When you last spoke or sent a useful reply.
Next action	A verb: call to confirm measurements, send the revised quote, or check the preferred date.
Due date	When you will do that action.
Quote and currency	Optional. Keep CAD and USD separate.
Result or reason	What happened, without guessing why a customer declined.

“Follow up” is too vague. “Call Sam on Tuesday to confirm whether the weekend appointment works” is actionable. If you are waiting for the customer, set a reasonable check-in date or explicitly close the enquiry. Waiting without a date is where requests disappear.

Make the reminder real

A coloured overdue cell does not notify you while you are working elsewhere. Put a recurring reminder in the calendar you already check: review enquiries at the beginning of the working day. Add separate calendar reminders for time-sensitive promises.

At each review:

1. Add yesterday’s phone, message, and form enquiries.
2. Filter to open enquiries whose next action is due.
3. Complete the action, record the contact date, and set the next action immediately.
4. Review New enquiries before leaving the list.
5. Mark completed or declined work Won or Lost. Keep the useful result, not an endless open task.

Choose a review time you can maintain. If daily reviews repeatedly fail, change the reminder method or use a tool with task notifications. Moving the same neglected list into a different app will not solve the problem.

If you use Google Sheets, custom conditional formatting can highlight overdue rows. With stage in E and due date in H, as in the supplied template, apply this formula to the data rows:

=AND($A7<>"",ISNUMBER($H7),$H7<TODAY(),$E7<>"Won",$E7<>"Lost")

Recheck those column letters and the first data row if you change the layout. Highlighting remains a visual prompt; the calendar reminder is what brings you back to the sheet. Use clear dates, such as 2026-10-04, and record the agreed time zone for an appointment spanning time zones.

Reply with a useful next step

For a new enquiry:

Thanks for asking about [job]. To confirm whether I can help, could you send [specific detail]? I will get back to you by [realistic date].

For an agreed quote follow-up:

Hi [name], checking whether you have any questions about quote [reference]. If the timing or scope has changed, let me know and I can confirm the next step.

Do not repeatedly message someone who has declined or asked you to stop. A requested reply and an ongoing promotional campaign are different things. In Canada, a requested response can qualify for a CASL exemption; that does not authorize an indefinite newsletter. In the United States, CAN-SPAM treats narrowly defined transactional messages differently from commercial messages, based on their content and primary purpose. A pre-sale quote is not automatically an already agreed transaction. Use the newsletter guide’s separately labelled Canada and US sections before building a marketing list from these records. See Canada’s requested-response exemption and the FTC email guide.

When more than one person answers

Give each open conversation a named assignee and a state such as Unassigned, Assigned, Waiting, or Resolved. The sales stage in the spreadsheet is separate: an enquiry can be Quoted while its next reply is still unassigned. Claim it before answering and leave the next action and date visible to the team.

Use this small routine:

• Review the unassigned queue and overdue actions at the chosen daily time.
• Keep received messages and sent replies visible in the shared workflow; forwarding copies to several personal inboxes is not a reliable shared history.
• Record who is covering holidays and absences, then hand over open promises explicitly.
• Resolve a conversation only when its next step is completed or deliberately closed.
• Remove departed people’s access and sessions, transfer open work, and retain required history under your retention rules.

Test a fictional enquiry with two people: assign it, reply, have the second person find that reply, hand it over, and resolve it. Permissions, notifications, and sent-history settings can fail even when both users can receive mail. A claimed assignee reduces confusion; do not assume the chosen tool automatically prevents simultaneous replies.

Your existing mailbox tools may already support the job through Google Groups Collaborative Inbox or Microsoft 365 delegation. Trial a new shared-inbox service only when the actual tests fail or the existing interface is unsuitable.

Keep the list private and recoverable

Share the file only with people who need it. Use a business-controlled account, enable account security, and avoid public link sharing. Do not put card numbers, passwords, identity documents, or sensitive client histories in a general lead tracker.

Tell people why you collect their details and how to contact you about them. Write a retention routine for old leads instead of keeping every note forever; retain records you still need for a valid purpose or a legal obligation. Keep only enough suppression information to avoid re-adding someone who declined marketing. A customer’s marketing opt-out is not an instruction to erase a legally required invoice.

A tracker template does not determine compliance in either country. Healthcare, financial, children’s, or other sensitive records need a workflow suited to the applicable obligations. A provider’s privacy badge does not settle your obligations or establish that its data stays in Canada or the United States.

Export a sample before the list becomes important. Open the exported file and check names, dates, notes, and contact details. Calendar reminders and attached files may need their own backup; a contact CSV does not automatically contain them.

Pay for a CRM when it removes a real failure

Consider a CRM when two people need to know who owns the next reply, you cannot reliably find conversation history, or missed reminders cost work despite a functioning review routine. Test those tasks during the trial. For example, HubSpot documents individual task reminders; check the current plan and reminder settings before depending on them.

Before upgrading, create a test enquiry, assign it, receive the reminder, close it, and export it. Include the learning and migration time in your decision. There is no universal contact count at which a paid CRM becomes necessary.

You are finished when: a new enquiry reaches the list, has a specific owner and next action, triggers your chosen reminder, and can be found in an export.