The Follow-Through: The Part That Happens After

Nobody wants a customer sitting there twiddling their thumbs, wondering whether anything is happening. That is the entire goal of follow-through, and stated that plainly it sounds like it should be easy.

The rules that produce it are simple enough: when this happens, send that. No department, no platform.

What is not simple is working out what the rules should be. That part is interviews. Who owns this kind of enquiry, and who covers when they are away. Who else needs to know it came in. What does the person expect to receive, and how soon before silence starts costing you. What happens on your side once it lands. Ask those questions of a team and you often find the business does not yet have one agreed answer, which is useful to discover and is not a five minute conversation.

So the interesting question is not whether you want follow-through. It is why something whose mechanics are this straightforward so often does not exist.

Three parts, and only one of them is simple

The concept is simple. The rest is not, and it is worth being straight about that rather than making it sound like an afternoon's work.

Designing the journey. What are the few moments that matter for your business, what should the person receive at each one, and what does it say. This needs someone who knows the business, and it is also where automation can work against you. The trap here is not automation itself, it is one generic reply doing duty for everything. A site with a single thank you for your submission message is sending the same words to a newsletter signup and to someone who spent twenty minutes writing out a detailed brief, and the second person can tell. Ours says we are taking a look at your project enquiry now, which is every bit as automated and reads as though somebody noticed what arrived. That means a different acknowledgement per entry point, which is the same conversion journey work the form itself needed.

Building it. This is the part that gets underestimated. If you are in Mailchimp or HubSpot, some of what you need may sit behind a higher tier. Connecting two tools that were never built to talk usually means something like Zapier, which is another subscription and another place for things to break. These setups are easy to get into and awkward to change later, which is a cost that arrives long after the decision. For someone without development experience, a follow-up sequence is an afternoon on a good day and most of a week on a bad one.

It is also genuinely hard to feel confident about, and that is not a beginner's problem. Email fires days later, into somebody else's inbox, and nothing tells you when one did not. We run our own automations against a test inbox and walk through them as a customer before they go anywhere near a real one, because otherwise you are setting up triggers and hoping. If it takes that much care from people who do it for a living, it is not reasonable to expect it as a side task from someone at the front desk.

Watching it. The tools will tell you what went out and who opened it. Visibility is not the constraint. The constraint is that looking is a task, and it is a task that pulls someone out of the tools they actually live in. They have to remember to go somewhere they otherwise never go, log into two or three separate services, and confirm each one is still firing. Then, if anyone wants an actual view of how follow-up is performing, someone has to pull those separate reports into one place, which is a project of its own.

Add that up and it stops being a chore that got added to somebody's plate. It becomes a real job, absorbed by a person who already has one. That is usually the point where it quietly stops happening, and follow-up systems do not fail loudly. They just stop being looked at, and nobody notices until a customer mentions they never heard back.

The fear is reasonable, and it is aimed slightly off

When this goes badly, it is usually because it landed on the wrong person. Someone gets handed a tool and told to automate the follow-ups, on top of the job they already had. It half works, nobody fully trusts it, and it gets quietly abandoned.

Owning a system you cannot maintain is genuinely worse than not having one, because now there is a thing that might be dropping customers and you cannot tell. But the problem was never the automation. It was being left alone with it, without the time or the grounding to design it, build it properly, or keep an eye on it.

That is what a partner is for. Someone maps the moments with you, writes the messages once, wires the rules up, and tests them by going through as a customer to confirm each one fires. Then someone keeps watching, because that part does not end. When it is working it is boring, which is the highest compliment a follow-up system can be paid, and it means everyone who reaches you gets the treatment you already know you would want without anyone having to remember to give it.

---

The Digital Office series. Five jobs a website has to do, named after the parts of a building they resemble.

• Anchor: The rooms your website has
• The sign: how people find you at all
• The lobby: your homepage is a first impression
• The consultation: are we a fit?
• The receptionist: what happens after someone fills in your form
• The follow-through: the part that happens after