Build a Follow-up Sequence You Can Repeat

01

Start here after your audit

Use this for people who have already asked your business about a service and have not yet replied. Check the original request, contact preference, and last conversation before including anyone. An open service inquiry is different from permission to enroll someone in ongoing promotional messages.

02

The problem

Ad hoc follow-up depends on memory and individual judgment. Promising leads can disappear while other people receive repetitive messages with no new value.

03

Why it matters

A repeatable sequence protects consistency without requiring aggressive automation. Each touch should help the person decide, answer a likely concern, or make the next step easier.

04

Common mistakes

More messages are not automatically better follow-up.

• Repeating the same Just checking in message
• Using one sequence for every lead type
• Continuing after a clear no or unsubscribe
• Automating before the team agrees on ownership
• Failing to record the next action and outcome

05

Design the manual sequence

Begin with a short sequence the team can run consistently.

• Choose which lead types belong in the sequence
• Give each touch one purpose and one clear next step
• Set timing based on buying context rather than a generic cadence
• Assign the owner and record each outcome
• Stop after a clear no, opt-out, invalid contact, or the documented final touch

06

Example scenario

Illustrative example · Not a client case study

A home-remodeling inquiry receives a useful first reply, a second message that answers a common scheduling question, and a final invitation to choose a consultation time. The owner stops the sequence after a reply, opt-out, invalid address, or the documented final touch.

07

Review before automating

Run the sequence manually long enough to learn which questions, objections, and timing patterns recur. Automate only stable steps, and keep replies routed to a person.

08

Adapt a short sequence to the inquiry

The following messages illustrate a routine estimate request. They are editorial templates, not a tested conversion formula. Replace each bracketed detail with accurate information, use the customer's chosen reply channel, and choose timing that fits their requested schedule rather than adopting a universal cadence.

• First response — help them proceed: 'Thanks for asking about [service]. We can help with [confirmed scope]. To work out the next step, could you confirm [one necessary detail]?'
• Second touch — remove a real obstacle: 'For your [service] request, [answer to a relevant scheduling or scope question]. Would [the actual next step] be useful?' Avoid inventing availability or scarcity.
• Final touch — close the loop: 'I will close this open inquiry for now so we do not keep following up. If you still need help with [service], you can reply here.' Use this only if replies will still reach someone.
• Before every message, read the record. If the person already replied or booked by phone, cancel the pending sequence and continue the real conversation.

09

Put stopping rules next to the schedule

For each lead, record the owner, last contact, purpose of the next contact, due time, and stop condition. A spreadsheet or task list can prove these rules before automation.

• Reply received: stop the scheduled sequence and assign the conversation to a person.
• Booked, declined, or asked not to be contacted: cancel pending touches and update the record immediately.
• Invalid contact or delivery failure: pause; investigate the permitted contact route without repeatedly sending to the same failing address.
• Final touch reached: close the sequence. Record 'no response' rather than assuming a sale was lost to a competitor.
• Duplicate inquiry: merge the work in the appropriate system so two owners do not run competing sequences.

10

Evaluate the sequence before making it longer

Review all inquiries that entered the sequence during a defined period, once enough time has passed for that group to complete the planned schedule. Include inquiries that exited early because of a reply, booking, stop request, or failed delivery; do not count only those sent the final touch. Count replies, useful conversations, bookings, no responses, stop requests, and failed deliveries separately. Ten extra messages with no additional useful conversations may simply be more work. Read examples of replies to learn which details helped people decide. Automate only when the manual process is reliable, replies and opt-outs stop queued sends, and there is a visible failure queue. If the team cannot keep the record current, fix ownership before increasing the number of touches.