WORKED ARTIFACT SERIESFICTIONAL 14-DAY EXAMPLE

Lead Follow-Up Sequence: A Worked 14-Day Log

What is the best way to follow up with website leads automatically? Begin with a helpful first reply, a limited sequence and clear rules for stopping.

Automation should make follow-up reliable without making prospective customers feel pursued. A new website inquiry is not blanket permission for endless calls or texts. The business needs a record of who replied first, the channels the person authorized, the unanswered question and the circumstances that end outreach. The completed worksheet below follows one unanswered inquiry over fourteen days after the first human reply. It measures the multi-touch sequence, not response speed or whether the lead is qualified.

Keep the measurements separate. The worked response-time audit measures how long people waited for their first human response. This record begins after that point. For the wider operating design, use the lead follow-up automation guide.

1. Define the inquiry and contact boundaries

Fictional business: Cedar Finch Home Services, a residential repair company. Inquiry CF-204: a homeowner asks for a deck-repair estimate through its website on Monday, November 2, 2026 at 10:00 a.m. Pacific time. The coordinator sends a personal reply at 10:24 a.m., acknowledges the problem, asks for two photos and offers a short scoping call. That counts as the Day 0 human reply, not an automated follow-up.

Contact preference: email permission is on the fictional form. SMS permission is not recorded, so this example sends no texts. Phone contact is left out rather than assuming permission or suitable calling hours. Schedule: Days 1 through 14 after the first reply, Pacific time, with no weekend sales outreach. Immediate stop: a reply, booking, explicit decline, opt-out, invalid address or a human owner changing the case state suppresses future scheduled messages.

2. Filled 14-day follow-up log

Each day is represented, including the days when the right action is an internal check rather than another customer-facing message. The illustrative lead never replies within the window. The word “delivered” means only that a fictional message-delivery record succeeded; it does not establish that the homeowner read or liked the message.

Day and date Channel / timing Message goal or review Fictional outcome
Day 1 · Nov 3 Email · 10:30 a.m. Repeat photo request and offer one easy next step Delivered; no reply
Day 2 · Nov 4 Internal queue · 9:00 a.m. Check replies, opt-outs and owner assignment Still open; owner assigned
Day 3 · Nov 5 Email · 11:00 a.m. Offer two possible scoping-call windows Delivered; no booking
Day 4 · Nov 6 Internal review · 4:00 p.m. Check duplicate messages and address status No duplicate or bounce
Day 5 · Nov 7 No send · Saturday Honor the weekend pause Queue held
Day 6 · Nov 8 No send · Sunday Keep the state, not the pressure Queue held
Day 7 · Nov 9 Email · 10:00 a.m. Explain what an estimate needs and invite a reply Delivered; no reply
Day 8 · Nov 10 Internal check · noon Search for booking under another email No booking found
Day 9 · Nov 11 No send · holiday review Review queue without extra contact Still pending
Day 10 · Nov 12 Owner check · 9:30 a.m. Confirm no conversation in a second channel Owner confirms none
Day 11 · Nov 13 Email · 10:15 a.m. Offer a final simple way to proceed or decline Delivered; no reply
Day 12 · Nov 14 No send · Saturday Maintain quiet period No contact
Day 13 · Nov 15 No send · Sunday Prepare the closeout review No contact
Day 14 · Nov 16 Internal closeout · 3:00 p.m. Close scheduled reminders, keep human reply path Closed as no response

There are four outbound follow-up emails, on Days 1, 3, 7 and 11. The other ten rows represent deliberate queue checks or pauses rather than missed contact opportunities. The closeout does not manufacture one more marketing message. “No response” is the only supported final outcome; it is not proof that the customer hired a competitor, abandoned the project or viewed every email.

3. Derive operating rules from the log

Stop the scheduled sequence when a person responds

If CF-204 replies with photos on Day 3, cancel every later reminder and assign the conversation to the coordinator. If the reply says “not interested,” suppress later reminders and record a decline instead. Sending a Day 7 email after either response is a process defect, even when the copy itself sounds friendly.

Respect the channel recorded at intake

No SMS opt-in means no SMS messages in this worked case. A tool supporting a channel does not authorize using it. Record contact preferences at their source, synchronize opt-outs and apply applicable communication requirements. Avoid treating a service inquiry as permission for an unrelated promotional campaign.

Make every exception someone’s responsibility

A bounced email should create a review state, not repeated retries. An appointment booked in another calendar must cancel reminders before the next scheduled send. An owner should examine unusual cases and note why a sequence was paused, changed, escalated or closed. These are state transitions the system should make auditable.

4. Rehearse three alternative outcomes

Test three branches with synthetic records before any production workflow. In the first, a prospect says “Please call Tuesday” after Day 1. Later scheduled reminders stop, and a human reviews the requested callback against allowed contact preferences. In the second, a prospect asks to unsubscribe. The suppression must apply across every connected email or messaging tool, not just inside one automation.

In the third branch, a calendar booking occurs although no reply arrives in the email thread. The booking event cancels the sequence and assigns appointment preparation instead of more sales reminders. Never use customer-facing production numbers for test messages. The separate lead qualification process helps decide whether an inquiry fits the service; sequence completion by itself says nothing about fit.

5. What to measure without inventing revenue

For this single fictional record: four follow-up emails sent, zero replies, zero appointments booked, one orderly closeout and zero unauthorized SMS messages. That does not yield a meaningful campaign conversion rate. A real monthly report needs a cohort of eligible leads, consistent entry dates, the number actually enrolled, replies, appointments, opt-outs, delivery failures and cases stopped by a human or booking event.

Use explicit denominators. Booking rate among enrolled and eligible leads differs from booking rate among every website visitor. The percentage of confirmed booked or declined leads whose future reminders were correctly stopped can reveal operational reliability. Keep the first-response timer separate from follow-up elapsed days. Small samples warrant showing raw counts next to any percentages; do not promise recovered sales from a sequence diagram.

6. Blank 14-day log to use in your operation

Use a row for each calendar day, including no-send days. Record local time, permitted channel, customer value, actual outcome and the next state. Put private lead data in an access-controlled customer system, not a public spreadsheet. The empty table cells below are intentional fields for your own entries.

Day Date / local time Channel or check Message goal Outcome / next state
Day 1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day 14

Before activating a real sequence, identify the owner, confirm permissions, choose quiet periods, verify the suppression logic and manually inspect a few complete test records. Start with fewer helpful messages and extend only when evidence and customer feedback support doing so. If acquisition rather than follow-up is the bottleneck, the Free Business Check can help separate those priorities.

Make follow-up predictable and respectful

StartLab can map lead intake, human ownership, channel rules and the automation handoffs that keep a service business responsive. The goal is a repeatable process, not a guarantee of bookings.

Explore Local Growth AutomationBook a Strategic Session

Share this:

Like this:

Like Loading…