How to Automate Lead Follow-Up Without Sounding Automated
TL;DR: do not automate sending, automate the blank page. A rep writing follow-ups by hand manages about 20 a day; reviewing and approving drafts they manage 80 with the same personalisation. Build: three to four days. The approval step is not a safety net you remove later, it is the thing that makes the output good. The bottleneck in follow-up is not judgment, it is typing and the reluctance to…
Automating the process of following up on leads can be done without compromising the personal touch. The key is to automate the draft stage, rather than the entire email sending process. This approach allows human reps to review and approve the drafts before they are sent, maintaining a personal connection with the recipient. The approval step is crucial, as it ensures the quality of the output and prevents the email from sounding automated.
The bottleneck in lead follow-up is not judgment, but rather the time and reluctance to start typing. Reps are well aware of the need to follow up, but they often skip it because writing the follow-up can be challenging, especially after three attempts. When a lead shows genuine interest, they tend to go cold due to the difficulty in crafting a follow-up and the presence of more urgent tasks.
To solve this issue, a CRM can be configured to pull relevant context from the deal, such as company information, contact details, last interaction, amount, stage, and the number of days without activity. A model can then generate a concise follow-up that references the specific points discussed during the last interaction and proposes a concrete next step with a deadline.
This draft is sent to the rep, who can review, edit, and approve it before it is sent from their own email address. This process saves time, as it takes only ten seconds to generate a draft instead of ten minutes, and the rep still has the opportunity to read and personalize the email before it is sent.
The approval step is essential, as it provides a sense of ownership and ensures that the follow-up sounds genuine. This step also helps prevent the email from being perceived as bulk sending, which can have legal implications. When drafting the follow-up, there are specific guidelines to follow. The draft should be limited to four sentences, reference a specific aspect of the last interaction, propose one concrete next step with a time, and avoid generic phrases like "circling back" or "touching base." If there is no new information to add, it is best to output nothing at all.
The optimal threshold for initiating follow-ups varies depending on the stage of the deal. For instance, a deal that went quiet after a proposal may require a shorter follow-up interval compared to a deal at the initial contact stage. The key is to track real activity, such as emails, calls, or notes, rather than simply monitoring record updates.
The implementation of this system requires minimal technical resources, including a CRM with API access (such as HubSpot, Pipedrive, or Salesforce), an automation platform like Make or n8n, a model API key, and a mailbox connection via OAuth. Compliance with legal requirements, such as having an unsubscribe mechanism and a suppression list, is also necessary. These measures ensure that the follow-up process remains within the bounds of applicable laws and regulations.
The results of implementing this system can be significant. In a case study, the B2B system generated 60-80 drafts per week. The reply rate improved from around 12% with manual follow-up to approximately 28% with consistent drafted follow-ups. Additionally, deals that would have stalled for two or three weeks started receiving responses within five days.
The primary factor behind this improvement is consistency, as the follow-ups that were previously missing now occur. This consistent follow-up approach is likely to outperform systems that rely on sporadic, manually-written follow-ups.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.