The final touch that closes the loop, makes silence easy, and keeps the door open for a better moment.
Write the breakup email for the content-hiring sequence. Four touches, no reply.
Three sentences: closing the file, a one-line reminder of the review bottleneck that prompted the outreach, and an offer to revisit once the new hires are ramped. CRM note records all four touches and sets a review date for ninety days out.
A breakup email template should close the loop, not manufacture urgency. This one writes a short final touch that states you are stopping, makes not replying completely acceptable, and leaves a genuine opening for later — which is also, incidentally, what tends to generate replies.
The last message in a sequence. It acknowledges that the timing did not work, releases the recipient from any obligation to respond, and states what would make it worth reconnecting later. Two or three sentences.
Say you are closing the file, name the specific thing you thought was relevant, and offer one door back in. No guilt, no false deadline, no "I will assume you are not interested" phrased as a reproach.
Because the urgency is transparently invented — there is no deadline, and the recipient knows it. Manufactured scarcity in a breakup email converts curiosity into irritation and costs you the option of a warm re-approach in six months.
After your planned touches are exhausted, typically two to three weeks after the first. Send it as a fresh short message rather than appended to a long unanswered thread.
The agent reads the earlier touches so the final message does not repeat them, and writes the re-entry conditions into your CRM as a note so a future rep knows what was already tried. It exports to your sequencer as the closing step of the cadence.
It reads the earlier touches so the final message adds something rather than repeating.
Name the change that would make this account worth contacting again.
Two or three sentences, no urgency devices, one clear door back in.
The CRM note records what was tried, so a future attempt starts warmer.
No manufactured urgency, which protects the future re-approach
Reads the earlier touches so the close is not a repeat
Names a specific re-entry trigger instead of "keep in touch"
Logs what was tried for whoever picks the account up later
State that you are closing the file, name the specific reason you thought it was relevant, and offer one door back in. Keep it to two or three sentences and avoid any implication that they owe you a reply.
Often the highest reply rate of the sequence, because releasing the obligation removes the reason to keep ignoring it. That is a side effect of a clean close, not a reason to fake one.
Avoid it. It reads as a mild reproach and puts the recipient on the back foot. "Closing the file on this — happy to revisit if X changes" achieves the same thing without the edge.
Yes, and that is precisely why the tone matters. A clean close plus a logged re-entry trigger makes the next attempt a continuation rather than a cold start.