All marketing guides / Lead follow-up process

A lead follow-up process defines what happens after someone asks about your business: where the request goes, who owns it, how you respond and when it is closed. Build that process before adding automation. Otherwise, software can repeat a confusing message or leave an inquiry sitting in several inboxes.

This guide walks through a simple workflow for a small service business. It includes a record template, an acknowledgment example and a test checklist. Timing and messages should fit your actual availability and the customer’s request. The examples are suggestions to adapt, not evidence of a particular conversion rate.

1. Trace where each inquiry arrives

List the ways people contact you. These may include a website form, calls, social messages, email or an advertising lead form. Then identify the actual destination of each request. A notification email is not necessarily the only stored copy, and a dashboard entry does not prove that a person saw it.

For each route, answer four questions: where is the request recorded, who receives a notification, who checks that destination and what happens when the first person is unavailable? If the answers are unclear, fix the routing before writing a sequence of follow-up messages.

Use approved tests to confirm delivery. Check the saved record and recipient inbox rather than relying on a confirmation screen alone. Our website lead checklist covers problems that can occur before an inquiry reaches this stage.

Keep access to inquiry records limited to the people who need it. Use your actual business tools and account ownership rather than placing customer information in a shared document that nobody maintains.

2. Give the lead follow-up process a clear owner

Assign one person or role to move each new request forward. Other people can contribute, but the record needs a responsible owner. A request that everyone can see is still easy for everyone to assume somebody else has answered.

Define coverage for evenings, closed days and absences. You do not need to claim round-the-clock availability if you cannot provide it. Tell people when they can reasonably expect a reply, and use that expectation in your internal task list.

If an inquiry needs a specialist, hand it over with its context: what the person asked, what has already been said and what action is due next. Avoid asking a prospect to repeat the same information because the business changed owners halfway through the conversation.

3. Keep one usable inquiry record

A simple record can work before a full CRM is necessary. The important part is that it reflects the latest conversation and makes the next action visible. An owner should be able to open the record and understand what happens next without searching several inboxes.

Store only information your team needs for the request. Keep permission and channel preferences with the record when relevant. If the person asks you to stop contacting them, record that clearly and end the sequence.

4. Acknowledge the request honestly

An acknowledgment can confirm that the business received the message and explain what happens next. It should not pretend that a person has reviewed the request if it was sent automatically.

Here is an adaptable example:

Thanks for contacting us about your website. We received your request. Our team reviews new inquiries during our listed business hours and will reply by the time shown below. If you have a page you want us to look at, you can reply with its public link. Please do not send passwords or sensitive account details.

Replace the timing with a commitment you can meet. Include the business identity and a working reply address. Check how the message looks on a phone and confirm that replies reach a monitored destination.

Keep the acknowledgment separate from the useful human response. A prospect may need an answer about scope, suitability or scheduling rather than another message saying that someone will be in touch.

5. Build a useful reply into your lead follow-up process

Refer to the person’s request and ask the smallest number of questions needed to move it forward. If they asked about a particular service, answer what you can before asking them to book a general sales call.

A useful reply can include a short restatement of the need, one clarification and a concrete next step. For a fictional website inquiry, that might mean asking which action visitors should take and offering to review the current public page before discussing a larger project.

Avoid sending a long questionnaire that repeats the original form. A few well-chosen questions are easier to answer and can show whether the business is able to help. If the request is outside your scope, explain that promptly rather than leaving the record open indefinitely.

Use plain language about availability, deliverables and the next conversation. The brand messaging checklist can help keep your website offer and follow-up explanation consistent.

6. Define stages and stopping conditions

Choose stages that tell your team what action is due. “New,” “Waiting for us,” “Waiting for customer,” “Conversation scheduled” and “Closed” may be enough for an early workflow. Add more detail only when it supports a real handoff or reporting need.

Set a reasonable follow-up approach for unanswered requests. The number and spacing of messages should reflect the original request, your service cycle and the person’s preferences. There is no universal sequence that suits every business.

Each follow-up should offer something useful: answer a question, clarify the next step or ask whether the person still needs help. Stop when the person declines, asks you to stop or reaches the agreed closure point. An old inquiry does not automatically belong in an ongoing newsletter or promotional campaign.

7. Automate the repeatable steps

Once the manual lead follow-up process works, identify steps that software can handle consistently. Suitable candidates may include saving a form entry, notifying the owner, creating a task or sending a clear receipt acknowledgment.

Keep judgment-dependent steps with a person. A system should not promise a price, confirm an appointment or claim that a service is suitable unless it has reliable information and an approved rule for doing so. Make an escalation path visible when a request cannot be handled automatically.

Before turning on a workflow, test these cases:

1. A complete, valid inquiry creates one record and reaches the correct owner.
2. An incomplete or failed submission does not start a success sequence.
3. Two notifications about the same inquiry do not create two customer conversations.
4. A customer reply pauses or redirects an unanswered-request reminder when appropriate.
5. A stop request prevents later automated messages.
6. An unavailable owner triggers the agreed backup route.

Use clearly labeled test records and remove them from business reporting. Do not treat a successful email send as proof that the customer read it or that the inquiry became a sale.

8. Measure the lead follow-up process

Record a few signals you can act on: unassigned inquiries, overdue actions, valid conversations and closed outcomes. Review the reasons requests stalled. Some may be unsuitable requests; others may reveal a broken notification, an unclear offer or a slow handoff.

If analytics is configured, Google provides recommended events for stages such as generating, qualifying and converting a lead in its lead-generation event documentation. These events need appropriate implementation; choosing an event name does not create a working CRM connection.

Keep customer names, emails, phone numbers and message contents out of Google Analytics. Google’s guidance on personally identifiable information explains this restriction. Use nonpersonal labels for permitted measurement, and keep the inquiry itself in your business’s customer system.

A short weekly review

Review the lead follow-up process with the people who use it. Ask which requests had no owner, which next actions were missed and which messages repeatedly required clarification. Fix one recurring problem before adding another automation.

The result should be a workflow somebody can explain and maintain: a known destination, a responsible owner, a useful reply and a clear next action. That foundation also helps you judge whether more acquisition activity is worthwhile; compare the options in our SEO versus Google Ads guide.

MOFO offers CRM, lead management and marketing automation support. Contact MOFO to discuss your inquiry routes and handoffs, or return to the marketing guides.