Automate Sales Follow-Ups
You finish a good call on Thursday. The prospect says send over a proposal, and you do, on Friday. Then the weekend happens, then a Monday full of other clients, then a week where you tell yourself you will check in "when things calm down." Three weeks later you remember, write a slightly embarrassed email, and get no answer. The deal did not die because of price or fit. It died because nobody was asking.
Follow-up is the least glamorous part of selling and one of the most valuable. It is also very easy to automate badly, in a way that makes you look like the sort of company that sends a stranger six emails in six days. This article is about doing it well, whether you are a solo consultant with a notes app and a calendar or a small sales team with a shared CRM.
What automation should and should not do
The goal is not to send more messages. The goal is to make sure no real conversation goes quiet by accident, and to take the memory burden off your head. A good system does three things. It notices when a follow-up is due, it drafts or sends a message that fits the situation, and it stops the moment the situation changes.
A bad system does the opposite. It sends a sequence on a timer regardless of what the prospect did, and it keeps going after they replied, booked a meeting, or said no. That is how automation damages relationships, and it is why the stop rules matter more than the sending rules.
Triggers, the events that start a follow-up
A trigger is an event in your data that starts a timer or a task. Pick triggers that reflect real buying signals, not just the passage of time. Good ones include these.
- A proposal or quote was sent and not yet answered.
- A discovery call happened and no next step was booked.
- A prospect opened your proposal link several times, if your tool records that, which is a mild signal and should never be treated as certainty.
- A form was submitted on your website.
- A deal has sat in one stage longer than its normal length.
- A past client's contract or project ended 90 days ago.
Each trigger should map to one specific follow-up with one specific purpose. "Proposal sent, no reply after 3 business days" is a clear rule. "Lead is warm" is not, because nobody can say what warm means or when it ends.
Business days, time zones and sending windows
Count business days, not calendar days, and skip holidays your recipient observes. If you serve clients in Puerto Rico and the mainland, remember that Atlantic Standard Time does not change with daylight saving, so the gap between you and Eastern Time shifts twice a year. Schedule sends for mid morning in the recipient's time zone. A message that lands at twenty to seven on a Sunday evening reads as pressure.
Stop rules, the part that protects you
Every sequence needs explicit stop conditions. Write them before you write any message. The list I use has six items.
- A reply of any kind. Even "not now" stops the sequence, and a human decides what happens next.
- A meeting booked. The next contact is the meeting itself.
- A status change. If the deal moves to won, lost or on hold, all pending follow-ups for it are cancelled.
- An unsubscribe or a "stop" request. This is permanent for that channel and must be honored immediately.
- A bounce. A hard bounce means the address is bad, and continuing only harms your sender reputation.
- A cap. No sequence runs longer than a fixed number of touches. For most one to one B2B selling, three to five touches over three to four weeks is plenty.
Reply detection is harder than it looks
Stopping on a reply sounds trivial and is where many setups fail. If your follow-ups go through a tool that sits outside your mailbox, the tool needs to see replies, and it needs to recognize them correctly. Three problems show up repeatedly.
- Replies from a different address. The prospect answers from a personal address or a colleague replies. A rule that matches on exact sender misses it. Match on the email thread and the company domain, and let a person confirm uncertain cases.
- Out of office and auto replies. These are replies in a technical sense but not in a human one. Most tools can detect the standard auto-reply headers. An out of office message should pause the sequence until the stated return date, not end it.
- Replies outside the email channel. A prospect texts you, calls, or answers in a meeting. Nothing in the mailbox changes. The fix is a simple habit. When you talk to someone, log it in the CRM, and make the log entry cancel the pending sequence.
If you take only one thing from this section, test your stop rules by replying to your own sequence from a second address before you let it near a real prospect.
Tone, or how not to sound like a robot
A follow-up should read like a note from a person who remembers the conversation. Two features separate those from the other kind.
First, it refers to something specific that was said. "You mentioned the audit is in March, so I kept the timeline in the proposal tight" is a sentence a template cannot fake unless you give it the variable. Capture one real detail from every call in a field, and merge it into the follow-up. If the field is empty, the system should not send. It should create a task for you.
Second, it makes the next step easy and small. "Would a 20 minute call Thursday or Friday work to go through the numbers" is easier to answer than "let me know your thoughts."
Here is a shape that works for a proposal follow-up, with no gimmicks.
- Touch one, three business days after sending. A short note that restates the one decision they need to make and offers help with any question.
- Touch two, seven business days after. Something useful and different, such as a one page answer to the question they raised on the call, or a relevant example of how a similar project was scoped.
- Touch three, fifteen business days after. A plain, polite close. "I will assume the timing is not right and will stop reaching out, but I am glad to pick this up whenever it makes sense."
That last message often gets the most replies, because it takes the pressure off. It also gives you a clean way to end the sequence.
Automated drafting versus automated sending
You can automate in degrees. At the lowest level, the system creates a task and a draft, and you press send. At a middle level, it sends only low risk messages, such as a meeting reminder, automatically. At the highest level, it sends the whole sequence. For solo consultants and small teams, I recommend the lowest level for anything that mentions price, scope or a relationship, and the middle level for logistics. Human attention is cheap at your volume, and a wrong message to an important prospect is expensive.
If you use a language model to help draft, treat it as an assistant that writes a first pass from your notes. Review every message, keep it from inventing facts about the prospect, and never let it send unsupervised.
Consent and anti-spam rules, in general terms
The rules differ by country, state and channel, and they change. What follows is general information and not legal advice. If you sell across jurisdictions or into regulated industries, ask a lawyer.
In general terms.
- Email to businesses in the United States is governed by the CAN-SPAM Act, which does not require prior consent for commercial email but does require a truthful sender and subject line, a valid physical postal address, and a working opt-out that you honor promptly.
- Email to people in the European Union or the United Kingdom is more restrictive, and often requires consent or a clearly documented legitimate interest. If your prospects are there, check the rules before you automate.
- Text messages and automated calls in the United States fall under much stricter rules, and consent generally has to be obtained in advance and recorded. Do not add prospects to automated texting without it.
- Canada has its own strict anti-spam law that generally requires consent.
Practical habits that hold up everywhere are these. Record where and when each contact gave you their address and what they agreed to. Put a plain opt-out in every automated message. Keep a suppression list that every tool checks before sending. And do not buy lists of strangers to feed a sequence. Beyond the legal risk, it ruins your domain's reputation, and messages start landing in spam for everyone, including your existing clients.
For deliverability, make sure your sending domain has SPF and DKIM configured. SPF is a published list of servers allowed to send mail for your domain, and DKIM is a cryptographic signature that proves a message was not altered in transit. If these are missing, mailbox providers treat your messages with suspicion no matter how good the text is.
A worked example (illustrative)
Take a hypothetical solo consultant who sends about 8 proposals a month. Suppose historically 3 of those 8 turn into projects, and the consultant believes about half of the lost ones went quiet rather than said no.
The consultant sets up one sequence with the proposal trigger and the three touches above, stop rules for reply, meeting, status change and unsubscribe, and a drafting step so each message is reviewed. Suppose over the next quarter, 24 proposals go out. These numbers are invented to show the arithmetic.
- If the sequence revives 2 of the 12 deals that would have gone silent, that is 2 extra conversations.
- If 1 of those 2 closes, that is one additional project in a quarter.
- If an average project is worth $6,000, the sequence added $6,000 against roughly an afternoon of setup and a few minutes a week of review.
The point is not the figure. It is that you can state the hypothesis, measure it, and decide whether to keep going.
Measuring what works
Measure outcomes, not activity. Emails sent is a vanity number. These are more useful.
| Measure | How to calculate it | What it tells you |
|---|---|---|
| Reply rate per touch | Replies after a touch divided by recipients of that touch | Which messages earn a response |
| Meeting rate | Meetings booked from the sequence divided by sequence starts | Whether follow-up creates conversations |
| Time to first response | Days from send to first reply | Whether your timing is right |
| Unsubscribe and complaint rate | Opt-outs and spam reports divided by sends | Whether you are annoying people |
| Revived deals | Deals that were stalled, then moved forward | The actual business effect |
Change one thing at a time. If you alter the timing and the wording together, you will not know which helped. With a small volume, you will not get statistical certainty, and that is fine. Look at the trend over a quarter, read the actual replies, and trust your judgment over a decimal point.
What can go wrong
- Duplicates. The same prospect enters two sequences and gets double messages. Use one active sequence per contact.
- Stale data. The contact changed jobs, and you keep writing to a departed employee. Review bounces and update records.
- Wrong personalization. A merge field fails and the message says "Hi ,". Add a check that blocks sending when a required field is empty.
- Silent failure. The integration breaks and nothing is sent for three weeks. Add an alert when no messages have gone out in a set period.
- Over-automation. The system sends to a client who is upset about an invoice. Give yourself a one click pause for any account.
What you can do on Monday morning
- Write down your stop rules before anything else.
- Choose one trigger, probably proposal sent with no reply.
- Write three short messages, each with a clear purpose.
- Set it up in the tool you already pay for, whether that is your CRM, your email platform or even calendar tasks, in draft and review mode.
- Log the outcomes for a quarter and review them.
You do not need a new platform to begin. If you want a second pair of eyes on the setup, such as the SPF and DKIM records, the reply detection or how the CRM and mailbox talk to each other, Ozcorp InfraOps can help, and we are happy to talk it through whether or not it becomes a project.
Discuss your infrastructure requirements
Review the current service offer or schedule a conversation about the scope you need.
Stay in touch
Follow Ozcorp
Leave your details for occasional notes about new articles and Ozcorp updates.