Nobody searches for a follow up email template because they cannot write a sentence. They search because a proposal went out eleven days ago, there has been no reply, and the choice on the screen is between sounding desperate and doing nothing. Then the same situation repeats with four other clients, at four different stages, and the real question turns out to be which ones are even due a follow up today.
That is the part the template libraries skip. A well written follow up sent three weeks late is worse than an average one sent on the right day, and a follow up nobody remembered to send has no wording at all. What follows is the timing, the structure that gets replies, the wording to avoid, and the mechanism that makes it happen without relying on anyone's memory.
The failure is usually timing, not wording
Follow ups go wrong in three ways, and only one of them is about the writing.
The first is that they never get sent. A proposal goes out, the sender intends to check in next week, next week contains something urgent, and by the time the gap is noticed it is three weeks wide and the message now needs an apology built into it. This accounts for most lost follow ups, and no amount of template quality touches it.
The second is that they get sent too many times to the same person. Without a record of what was sent when, two people from the same supplier can both chase the same contact, or one person can send a third nudge believing it is the first. That is the failure that actually damages the relationship, more than any phrasing.
The third is the wording, and it is the smallest of the three. Most follow ups that read badly are badly structured rather than badly written: they restate the entire previous message, apologise at length, and end without a single clear question. That is fixable in four lines.
The order to fix these in is the order they are listed. A team with a reliable next action date against every open conversation is in better shape than a team with excellent wording and no system, because the first team's messages arrive on time.
When to send it
Cadence depends on what was sent and what the client committed to. The useful rule is that the interval matches the size of the ask.
| What preceded it | First follow up | Then | Notes |
|---|---|---|---|
| Quote or proposal sent | 3 to 4 working days | Weekly, up to three times | Enough time to have circulated it internally, not enough to have forgotten it |
| Meeting or call held | Same day or next morning | Once more after a week | The summary itself is the follow up, and it is the highest value one |
| Client promised a decision by a date | The working day after that date | Every few days | Reference their own date, not the calendar |
| Invoice sent, payment overdue | The day after the due date | Weekly, then escalate | Separate from relationship follow ups, and it runs to its own schedule |
| Cold outreach, no prior contact | 4 to 5 working days | Twice more, spaced wider | Then stop for a quarter |
| Waiting on information to continue work | 2 working days | Every 2 days, and say what is blocked | Delay has a visible cost here, so name it |
Two refinements matter more than the exact intervals. Widen the gaps as the sequence goes on, since a third nudge at the same interval as the first reads as pressure while a wider one reads as persistence. And when the client named a date themselves, use it. A message that opens by referring to the date they set is not a chase, it is a follow up on their own plan, and it reads completely differently.
Avoid Monday morning and late Friday. Neither is a superstition about open rates, it is that both land in a pile the recipient is triaging rather than reading.
Same thread or a new email
Reply in the original thread when the client has some reason to remember it: they replied at some point, or they asked for the document, or it is under two weeks old. The thread carries the attachment and the history, so the recipient does not have to search for anything.
Start a new email when the thread has grown long, when the previous messages were sent to a different person, or when the subject line no longer describes what is being asked. A twelve message thread titled with the original enquiry is hard to act on, and a fresh subject that names the current decision is easier to forward internally, which is often what actually needs to happen.
When starting a new one, reference the previous message explicitly and attach the document again rather than referring to an earlier attachment. Asking somebody to scroll is a small cost that reliably produces a delay.
What goes in the message
Four elements, in this order, and nothing else.
The reference. One line naming what was sent and when. Not a summary of it, and not an apology for following up. "Following up on the proposal sent on 3 March" is the whole line.
The new information, if there is any. A follow up that adds something is not a nudge. A relevant example, a deadline that has since become relevant, a change in availability, an answer to a question raised earlier. This is the single biggest difference between a follow up that gets a reply and one that does not.
One question. Exactly one, and it should be answerable in a word or a sentence. "Is the decision still expected this month" is answerable. "Let me know your thoughts" is not a question and produces no reply because there is nothing to type.
An easy exit. A sentence that makes "not now" a reply rather than a silence. Most non responses are not rejections, they are the absence of a comfortable way to say the timing is wrong. Supplying that way converts silence into information.
Here is the shape, at length.
Subject: Proposal for the March intake
Following up on the proposal sent on 3 March.
One thing has changed since then: the March delivery slot is now the last one before the summer, so the timing may matter more than it did.
Is a decision still expected this month, or has it moved? Either answer is useful for planning.
If it has been shelved for now, that is a fine answer too.
That is under a hundred words and it contains all four elements. Length is not a virtue in a follow up, but neither is being cryptic. The failure mode of very short nudges, "just bumping this", is that they add nothing and place the whole burden of the exchange on the recipient.
Wording that reliably backfires
A short list, each one common and each one avoidable.
"Just checking in" and "just circling back" signal that the message contains nothing new, which is usually accurate and never helpful. If the message truly has nothing new, add something or wait.
"Apologies for chasing" apologises for doing the job. It also draws attention to the number of previous attempts, which is the thing not to highlight.
Any variant of "as per the previous email" reads as an accusation regardless of intent. Reference the date instead.
"Let me know if you have any questions" is a closing line that asks for nothing. It is the most common last sentence in unsuccessful follow ups because it feels polite while removing the only question in the message.
False urgency, meaning a deadline invented to force a reply, works once. When the deadline passes without consequence, every future deadline is discounted, including the real ones.
Finally, be careful with the word "again". It quietly counts the attempts for the reader.
When to stop
Every follow up sequence needs an end, decided before it starts. Three attempts on a warm conversation and three on cold outreach is a common shape, and what matters is less the number than that it is fixed in advance rather than decided by mood.
The final message in a sequence is the one worth writing carefully, because it often gets the reply the previous three did not. It works by removing the obligation.
Subject: Closing this off
Three messages have gone unanswered since 12 May, so this will be the last one on this.
If the project is on hold or has gone elsewhere, no reply is needed at all.
If it comes back later, the quote from May will still stand until the end of July, and picking it up again is easy.
No pressure, no guilt, a clear statement of what happens next, and a door left open. Then actually stop. A fourth message after announcing the third was the last undoes the credibility of everything sent before it.
Stopping is not the same as forgetting. Set the conversation to a dormant state with a date to revisit, typically a quarter out, so it leaves the working list without leaving the record.
Making it a system instead of a memory
Everything above depends on one thing: knowing today which conversations are due a follow up. That is a records problem, and it needs four fields.
A next action date on every open conversation. Not a mental note and not a calendar reminder that names no context. The date lives with the conversation, and the working view is a list of what is due today.
One named owner. Two people chasing the same client is the most damaging failure in this whole area, and it happens whenever a conversation belongs to a shared mailbox rather than to a person.
The history of what was sent, visible to the team. If the previous three messages live in one person's sent folder, nobody else can pick the conversation up, and the person who can is on leave the week the client replies. A follow up written without knowing what the last one said is how a sequence turns into a pile.
A status that distinguishes waiting on the client from waiting on the team. These are opposite situations that look identical in an inbox. Only one of them needs a follow up, and the other needs the work finishing.
These four fields are what turn a template library into a process. Enquiries, applications and quote requests all need the same structure, which is set out in use cases, and how owners, statuses, history and saved wording sit against each individual response is described in features.
One caution about tooling. Open and click tracking is genuinely useful for deciding whether a message reached the right person, and it is a poor basis for the wording of the next one. A message opened four times might mean interest, or it might mean the recipient searching for something else. Use it to inform timing, never to write a sentence like "noticed the proposal was opened", which reads as surveillance.
What to change first
Put a next action date and one named owner on every open client conversation, then work from a list of what is due today rather than from memory. That single change fixes the most common follow up failure, which is the message that never got sent. If those conversations currently live in a shared mailbox where neither the owner nor the history is visible, that is the thing to replace, and the Halict demo shows what it looks like with both attached to the response itself.
Q1. How long should you wait before following up with a client?
Three to four working days after a quote or proposal, the same day or next morning after a meeting, the working day after any date the client named themselves, and two working days when work is blocked waiting on information. Widen the gaps as the sequence goes on, since a third nudge at the original interval reads as pressure.
Q2. How many times is it acceptable to follow up?
Three attempts is a common limit for both warm conversations and cold outreach, and the important part is deciding the number before starting rather than by mood. Make the last message say it is the last, state what happens next, and then stop, because a fourth message after announcing the third was final removes the credibility of everything before it.
Q3. Should a follow up go in the same email thread or a new one?
Same thread when the client has reason to remember it, meaning they replied at some point or it is under two weeks old, because the attachment and the history travel with it. Start a new email when the thread has grown long, the recipient has changed, or the subject line no longer describes the decision being asked for.
Q4. What should a follow up email actually say?
Four things in order: one line naming what was sent and when, anything new that has changed since, exactly one question answerable in a sentence, and a line that makes "not now" an easy reply. Leave out apologies for following up and leave out "let me know if you have any questions", which asks for nothing.
Q5. Why do clients ignore follow up emails?
Most silences are not rejections. They are the absence of a comfortable way to say the timing is wrong, or a message that contained no question to answer, or a decision still sitting with somebody who was never on the thread. Supplying an easy exit and asking one specific question converts a good share of those silences into usable answers.
Q6. How do you keep track of which clients need following up?
Four fields against each conversation: a next action date, one named owner, the history of what was already sent visible to the whole team, and a status that separates waiting on the client from waiting on the team. Then work from a list of what is due today. A shared mailbox supplies none of the four, which is why follow ups get missed and duplicated there.