11. The Follow-Up Sequence for Leads Who Haven't Booked

Summary

The inquiry sequence for Ledgerlane

A lead fills in the booking form and never books the call. They get one factual automated reply straight away, then two short nudges on day three and day seven. The sequence stops when they book a call or opt out. It builds on the setup the last chapter walked through: HubSpot's free CRM, the Zapier connection from Tally, the authenticated sending domain and the factual reply.

Testing the CRM first

Submit the form from a private tab using a link with source, medium and campaign all set to test. Submit again with the same email but a different trigger choice. You should see one contact, the trigger property updated, and the factual reply arriving twice, because HubSpot enrolls a contact on every submission. So anyone who submits twice would start the follow-up twice unless the rules prevent it. If no reply arrives, it has to be sent from Zapier instead. Mark the record as a test.

What Ledgerlane may send

Under PECR, a sole trader counts as an individual subscriber, so marketing email needs consent or the ICO's soft opt-in for electronic mail. The soft opt-in needs four things together: details taken directly from the person, interest shown in the service, similar services only, and an opt-out offered at collection and in every message. The Tally form currently has no opt-out line. Whether a price-and-inclusions reply counts as marketing is left unsettled. Treat both nudges as marketing: add a short line and tick box near the submit button before either sends, and nudge only leads who submitted after it. Its wording is the founder's decision.

The three messages and who is excluded

The immediate reply stays factual. Day three restates the price (£180 a month for one van), the four inclusions, the three exclusions, and that penalty appeals are not included. Day seven offers the diagnostic call again and asks about VAT registration. Personalisation uses only van count and the chosen trigger. Drafts are tagged sentence by sentence to the facts register, then checked; a sample day-three email shows the result.

Nobody is sent a nudge if they are suppressed, unsubscribed, have a call-booked date, are a customer, are a test, ticked the box to say no, or submitted before it existed. A double submitter gets the sequence once. Four sample contacts check this: fresh, booked, unsubscribed, test.

Choosing the sending tool

As of November 2026, the free HubSpot plan allows one automated email action, already used by the reply. HubSpot Starter has an unclear advertised price, and branching workflows are listed only for higher tiers. Mailchimp's sync with HubSpot doesn't carry tags, so a booking can't reliably stop a journey.

Exercise: list four sample contacts, state who gets each step and why, then run the double-submission test.


Someone fills in Ledgerlane's booking form and then never books the call. What should happen to them next? Here is the answer this chapter builds. They get one factual automated reply straight away. On day three and day seven they get two short nudges, each written only from the facts register and from the answers the lead gave on the form. The sequence stops the moment they book a call or opt out. Before any of it goes out, you will run the test the last chapter left open, because a sequence built on a CRM you haven't checked will send the wrong email to the wrong person.

This is the first small lifecycle sequence in the course. A lifecycle sequence is a short series of messages tied to where a customer stands. Here that is the inquiry state: they asked, but haven't acted. It builds on the setup the last chapter walked through: HubSpot's free CRM, the Zapier connection from Tally that creates or updates a contact by email address, the authenticated sending domain and the one factual reply. If you haven't built those yet, do that first, because the test below checks every one of them.

The case running through this chapter is an illustration. Say a one-van contractor gets an HMRC penalty letter, finds the offer page and submits the form. They pick one van and choose penalty letter as the reason they got in touch.

Following one inquiry from the form to the last nudge

Start with the test. Take your phone, open the offer page in a private tab using a link with source, medium and campaign all set to test, and submit the form. Use a name like TEST plus today's date, choose one van, and pick penalty letter. Then submit again with the same email address, but this time choose big year-end bill.

Now open the contact in HubSpot. You should see one contact, not two, because HubSpot matches contacts on email address. The trigger property should read big year-end bill, since the second submission updated it. The three campaign properties should all read test. In the inbox you used, the factual reply should have arrived from the Ledgerlane domain with a working unsubscribe link. It should have arrived twice, because HubSpot enrolls a contact again on every form submission.

That double reply tells you something for the sequence. Anyone who submits twice will start the follow-up twice unless you build against it. If the reply never arrived at all, the contact Zapier created didn't trigger HubSpot's form workflow. In that case the reply has to be sent from Zapier instead. Last, mark the record as a test so it never counts and never enters a sequence.

Before writing a word of the nudges, settle what you are allowed to send. Under the UK's Privacy and Electronic Communications Regulations, known as PECR, a sole trader counts as an individual subscriber, the same as any member of the public. Most one-van contractors are sole traders, so marketing email to them needs either their consent or what the Information Commissioner's Office calls the soft opt-in. The soft opt-in needs four things together. First, you got the details directly from the person. Second, they showed interest in your service, and they don't have to buy. A request for more details or a quote can qualify, but browsing or an unrelated question cannot. Third, you market only similar services. Fourth, you offered an opt-out when you collected the details, and you offer one in every message. It must be simple and free, and it can't require an account or a login.

Filling in a form to ask for a diagnostic call fits the second condition. The fourth is where Ledgerlane falls short today. The Tally form has no opt-out line at collection. One more question stays unsettled: whether a reply that carries only price, inclusions and exclusions counts as marketing at all. Nothing settles it here. So treat it carefully. Add a short line to the form near the submit button. It should say that Ledgerlane may send a couple of follow-up emails about the service, and give a tick box to say no. Treat both nudges as marketing: day seven asks for the call again, and day three is there to win it. So add the line before either nudge sends, and send nudges only to leads who submitted after it went up. How the line reads is the founder's decision.

Now the sequence itself, for the one-van contractor with the penalty letter. The immediate reply stays as it is, strictly factual. It gives the price, the four inclusions, the three exclusions, the two-week setup and the one VAT question.

The day-three email restates the chosen van price, which is one hundred and eighty pounds a month for one van. It lists what's included: receipt capture, monthly bank reconciliation, quarterly VAT preparation and tax-ready year-end accounts. It names what isn't included: payroll, invoice chasing and incorporation advice. It says plainly that penalty appeals are not included, and that the letter itself explains how to appeal.

The day-seven email offers the diagnostic call once more and asks whether they are VAT-registered.

Personalisation uses only two facts, the van count and the trigger the lead chose. A lead who picked penalty letter gets an opening that names the letter. A lead who picked big year-end bill gets one that names the bill. Nothing else is guessed. Draft both emails in a new chat in the Ledgerlane Marketing project. A request that works reads like this: "Draft the day-three follow-up for a lead who chose one van and penalty letter but hasn't booked a call. Use only current rows from the facts register. Open with the penalty-letter version. Keep it under a hundred words, plain and friendly. After each sentence, put the register row it comes from in brackets, or write no source."

Here is an illustration of what should come back, tags removed. "You got in touch about a penalty letter, so here is the plan in one place. One van is a hundred and eighty pounds a month. That covers receipt capture, monthly bank reconciliation, quarterly VAT preparation and tax-ready year-end accounts. It doesn't cover payroll, invoice chasing or incorporation advice, and it doesn't cover appealing the penalty. Your letter explains how to do that." Every sentence there traces to a register row. A sentence tagged no source is cut, or goes to the founder as a question. Run the same request for day seven, which offers the call again and asks whether they are VAT-registered. Then check every tag, just as the offer page was checked.

The exclusions matter as much as the emails. Nobody gets a nudge if they are on the suppression list or have unsubscribed. Nobody gets one if they have a call-booked date or a lifecycle stage of customer. Nobody gets one if they are marked as a test, ticked the form's box to say no, or submitted before that box went up. A contact who submitted twice gets the sequence once.

Check this against four illustrative contacts. The fresh penalty-letter inquiry from Monday gets the reply, day three and day seven. A two-van contractor who booked a call on day two got the reply, but gets neither nudge, because a call-booked date stops the sequence. Someone who clicked unsubscribe in the first reply gets nothing further and stays on the suppression list. The test record gets nothing at all. If any one of those four would receive a message it shouldn't, fix the rule before anything sends.

Then choose the tool that sends days three and seven. As of November 2026, HubSpot's free plan costs nothing and allows up to a thousand marketing contacts, two thousand sends a month and one automated email action. That one action is already used by the reply. HubSpot's Starter plan allows one simple workflow per form with up to ten actions. Its advertised price is unclear, so check the plan page before you count on it. Branching workflows, the kind that wait, check whether someone booked and then decide, are listed only for the Professional and Enterprise plans.

So on the free plan, days three and seven go out by hand from a saved queue. Build a filtered list in HubSpot of contacts created three or seven days ago. Exclude any with a call-booked date, customer stage, test flag, unsubscribe or a ticked no-follow-up box. The founder checks that list each morning and sends from saved templates. It takes a few minutes, and because the founder reads the list, someone who booked an hour ago won't get a nudge.

The other route is an email platform's own automation. Mailchimp's free plan doesn't reliably run automated journeys. Essentials starts from thirteen dollars a month with four journey points, and Standard from twenty dollars with two hundred. Mailchimp's HubSpot sync needs HubSpot's Data Hub Starter or higher, and it doesn't sync tags. That means a booking recorded in HubSpot can't be relied on to stop a Mailchimp journey.

Brevo documents an exit based on a contact attribute, so a contact leaves the automation once a field such as call-booked changes. Its HubSpot sync maps properties onto those attributes. But manual syncs run at most once every six hours. An exit can therefore lag, and someone who just booked could still get a nudge. Brevo's free plan lets up to two thousand contacts enter active automations. Check in Brevo's own settings whether attribute exits work on the free plan before relying on them.

For Ledgerlane at its current volume, the free plan with a manual queue is the safer choice. Brevo becomes worth it once the morning check takes longer than the lag risk is worth.

Now try it on your own inquiry form. List four sample contacts: one fresh, one who booked, one who unsubscribed and one test record. For each follow-up step you plan, write down who receives it and why the others are left out. It has worked when every contact has a stated reason, and no booked or opted-out contact receives a nudge.

Then run the double-submission test, and choose between the free plan with a morning queue and Brevo with an attribute exit.

Want a book of your own?

Gnothi wrote and narrated this chapter. Name a subject and it writes you a course, or a story that teaches it, one chapter at a time, delivered to your podcast app.

Get started free