Stop losing leads: build a follow-up process that never forgets

Find where your leads are slipping away

Every lost lead has a story. Pick one recent enquiry and trace its path from the first message to the final outcome. Write down where it arrived, who noticed it, what they knew about the customer, and what happened next.

Look for the moments when someone had to remember a task or copy information between tools, and start there. A clear handoff for one common enquiry is a better starting point than a complicated workflow nobody owns.

For example, a quote request arrives on Friday afternoon. The confirmation email goes out, but nobody owns the reply. On Monday, two teammates each assume the other has called. The fix starts with assigning one owner and a due time when the request arrives. Sending another automated email would leave the same gap. And the path usually starts earlier, on the page the customer found first — service page SEO covers how those pages earn the visit and frame the enquiry.

Capture what the customer actually needs

An email address tells you where to reply. It does not explain what the person needs. Your intake should give the next teammate enough context to respond without making the customer repeat everything.

For a service business, that might be the requested service, location, preferred timing, and the question the customer asked. For a software business, it might be the workflow they want to improve and the product they are evaluating. Keep required fields limited to information needed for that first useful reply.

• Where the enquiry came from
• What the customer asked for
• Who owns the next action
• When the next action is due

Replace “follow up” with a clear next move

“Follow up” is too vague to be a useful task. “Call to confirm the service area and offer two appointment times” gives the owner a concrete job. Decide what a successful next step looks like for each common enquiry type.

Use a small set of meaningful states: new, in progress, waiting on the customer, booked, and closed. A teammate should be able to understand a record without reading a long message history. Keep the original conversation alongside the status so important details are not lost.

A useful handoff might read: “Website quote request; customer wants installation in November; service area confirmed; Morgan to call on Monday before noon; ask for photos before preparing the estimate.” The teammate can see the request, the missing information, and the next task in one place.

Automate the reminders, keep a person in charge

Automated acknowledgments and internal reminders can support a repeatable process. Write the expected behavior before configuring the tools: what starts the workflow, what message is sent, who is notified, and what stops further follow-up.

A customer reply, a booking, or a team member taking over should have a deliberate effect on the workflow. Test those paths before launch. Include an exception path for incomplete details or a request your business cannot fulfill.

Write a short rule for each outcome: a reply pauses the reminder and alerts the owner; a booking closes the open booking task; an opt-out stops further texts; an unanswered request stays on an assigned task list. If the tool cannot detect an outcome, define how a person will record it. For quotes specifically, SMS follow-up for quote requests covers the messages, timing and stop conditions that turn unanswered quotes into booked work.

Speed is part of that expected behavior: the first reply should arrive while the enquiry is still fresh. Our guide on how fast a business should follow up with a new lead covers what that first response should say, and how to sequence the touches that come after it.

A follow-up process is one part of a wider setup. When the website enquiry, the phone call and the follow-up sequence all feed the same record, nothing depends on one person's memory — the bigger picture is covered in our guide to AI sales automation for local businesses.

Fix one leak every week

At the end of the week, review a few completed enquiries and a few that stalled. Were tasks assigned? Did the response address the actual question? Did the customer get a clear way to move forward?

Fix one recurring problem at a time. The goal isn’t more automated messages. It’s a process your team can explain, repeat, and improve, so more enquiries turn into booked work.

• Count new enquiries with no owner or due date.
• Check a sample of replies against the customer’s original question.
• Find reminders that continued after a reply, booking, or opt-out.
• Choose one correction and name the person responsible for it.