Sales Follow-Up Email Timing: Five Buyer Signals and What to Send

A sales follow-up email works when it arrives while the buyer is thinking about the deal and addresses whatever they are stuck on. A fixed cadence (day three, day seven, day fourteen) gets both wrong because it runs on the seller's calendar. The buyer who read everything twice in the first hour and the buyer who never opened it get the same nudge. This guide times each follow-up to what the buyer did with what you sent. It covers five signals, the timing and a short template for each, and the setup that turns a view into a task for the rep.

Why email opens are a weak signal, and what to track instead

Most sales email tracking tries to fix the timing with open tracking: the email carries an invisible image, and the tracker logs an open when that image downloads. The trouble is that a person isn't always the one downloading it. Some mail apps fetch every image as the message arrives, through a privacy proxy, and some corporate mail filters fetch images while checking mail. Both inflate your opens. Mail apps that block images do the opposite and hide real reads. And even a real open only means someone saw the email, not the proposal.

A per-recipient page link gives you a cleaner signal. Publish the proposal as a page and give each person their own tracked URL. A view then means that URL loaded in a browser. A view also tells you things an open can't: scroll depth (how far down they got), time on page, repeat visits, and new unique visitors once the link has been passed on. HTMLvault records all of these for every link, along with geo, device and referrer.

One rule: use the signal to decide, never to quote

Tracking tells you when to write and what to write about. It never goes into the email. Don't write "I saw you spent four minutes on pricing" or "looks like you've opened this a few times," and don't mention where, when or on what device they read.

Quoting the data reads as surveillance, and a buyer who feels watched gets guarded at the moment you want them candid. The data is also often wrong about who did the reading: the four minutes may belong to a colleague the link was forwarded to.

The test: the email must read the same to a buyer who assumes you have no tracking at all. If a sentence only makes sense because you watched them read, delete it and write the useful thing it was pointing at.

Sales follow-up email templates for five buyer signals

Read each signal from the recipient's own link, never from email opens. The same approach works for a follow-up email after a proposal, a demo recap or a pricing page. The timings assume a sales cycle that runs for weeks. Brackets mark what you fill in.

Not opened after two days

If there's still no view two business days after sending, the email is probably buried, or the buyer needs a reason to open it. This is the classic follow-up email after no response, and the one signal where a plain reminder is the right move. Send it on day two or three, and give them a shorter way in.

Hi [name], the short version: [one-sentence outcome] for [price], starting [date]. The full proposal is here: [link]. If someone else is better placed to review it, tell me who and I'll send it to them.

Opened briefly

One view of well under a minute, a shallow scroll, no return visit. Either it didn't hold them or they were on a phone between meetings. Don't resend the link. On the next business day, lead with the one point most specific to them and ask one question.

Hi [name], one part of the proposal applies directly to [their situation]: [one sentence]. Is [their stated priority] still the main thing you're solving this quarter?

Read deeply, then went quiet

They scrolled to the end, spent real time on the page and maybe came back once, then went silent for days. They are thinking it over or building the case internally, and chasing them now interrupts that work. Wait three to four business days after the last visit, then send something that helps them make the case.

Hi [name], at this stage the question that usually comes up is [likely objection]. Here's how we handle it: [two sentences]. I'm happy to put that on one page you can forward.

Came back to pricing

A return visit that reaches the pricing. Page analytics report scroll depth, not which section held attention, so set up the page so this signal is readable. Either put pricing on its own short page linked from the proposal, or put it last, so a return visit read to the bottom is a fair proxy. Either way, the buyer is weighing cost or terms. Write the same day or the next morning, and make the email about options.

Hi [name], a few options on the commercial side in case they help: we can [bill annually / phase the rollout / start with one team]. If a different structure fits how you budget, tell me and I'll update the pricing.

New viewers on their link

One recipient's link shows more unique visitors than the one person you sent it to, often from another city or device. That means it has been forwarded, and finance, IT or the buyer's manager has joined the decision. Within a day, write to your original contact. When they name someone, give that person their own link.

Hi [name], if others on your team are reviewing this, I'm glad to brief them directly or send a version focused on [cost / security / rollout]. Who should be in the next conversation?

Wiring it up: recipient links, a webhook, a CRM task

Signals only help if they reach the rep in time, and checking a dashboard every hour is just a cadence with extra steps. Set it up so each view arrives as a task:

1. One link per stakeholder. Publish the proposal once, then make a tracked link for each person. From Claude or another assistant connected over MCP, create_recipient_links does this in one call. If each person needs their own page, POST /api/v1/links/batch builds up to 100 pages from one template with {{name}} placeholders.
2. A webhook on views. Send the recipient.viewed event (link.viewed for an ordinary link) to Zapier, Clay or your own endpoint. Pro includes up to five webhooks.
3. One task, not six. Create a CRM task on the contact, due today, unless an open follow-up task already exists. That way a buyer rereading the proposal doesn't bury the rep in tasks.
4. A task for silence. A webhook can't fire for a view that never happened. At send time, create a "no view yet" task due in two business days, and close it when the first view arrives.

When a task comes in, the rep opens the link's analytics, works out which signal it is and picks the matching email. The webhooks guide covers the events and setup.

Worked example: one proposal, one week, two emails

A rep sends a proposal on Monday night to an operations director. Pricing sits on its own linked page, and both pages go to her as recipient links. The automation creates a "no view yet" task due Wednesday.

• Wednesday morning: the task is still open, so the rep sends the short version and offers to send it to whoever is better placed to review it.
• Wednesday evening: she reads the proposal to the bottom over eight minutes. The rep waits.
• Thursday: two new unique viewers from a second city appear on her proposal link, and her pricing page gets a return visit.

When signals stack, write one email that answers the most advanced of them. Pricing getting a second look while new readers arrive suggests finance is involved. That also ends the wait the deep read called for. Thursday afternoon's email:

Hi [name], two options on the commercial side in case they're useful: annual billing at [price], or starting with one team at [price]. If it would help whoever is reviewing the numbers, I can send them a one-page summary directly.

The email mentions no visit, no city and no second viewer. On Friday she names her finance lead and asks for annual pricing in writing. The rep gives the finance lead a recipient link and has an AI agent add the annual option with patch_link, which keeps the URL (editing a published page explains how). Each patch's find string must appear exactly once in the stored HTML, which get_link returns. That's why the pricing table has an id and each price is written in only one place. The link she forwarded now shows the new number.

Caveats: where signal-led follow-up goes wrong

• A signal is a likelihood, not a fact. A short view may be a phone in a corridor, and a long one may be a tab left open over lunch. Give more weight to depth and repeat visits than to any single view.
• Machines click too. Some corporate mail filters open links to check them. A view seconds after delivery, with no scroll and almost no time on page, may not be a person.
• Write when the signal changes. The same signal showing up again is not a new reason to email.
• Old prices travel. A forwarded proposal keeps circulating after the quote lapses, so set the link to expire when the quote does. Pro lets you choose anything from an hour to never, and choosing an expiry window walks through the options.

On Thursday afternoon, while someone in the buyer's finance team has the numbers open, the rep's email arrives about the numbers: annual billing, a smaller start, a summary for whoever is checking. It's about what the buyer is weighing, and it arrives while they're weighing it.