How soon after the click should I follow up?

Two business days is the default. Same-day notes feel anxious, especially in a close week. If they clicked during SKO or a QBR, wait until that week ends. Faster follow-ups rarely raise replies. They just stack your name in a forecast inbox that is already loud.

What stall should I guess when a sales VP clicks and vanishes?

Unused seats, a sandbox that never launched, or CS sitting on activation numbers. Pick one. Three guesses look like a blog. A wrong guess still beats a vague bump, because they'll correct you, especially around SKO and a quiet click. Don't guess they went cold on you as a person. That's your anxiety, not their quarter.

Is a sandbox login a better ask than a meeting?

Usually yes, if the sandbox already exists. A calendar hold is still prep plus a slot, and their week is a grid of pipeline reviews. Async is live slot only if they asked for a walkthrough, especially around SKO and a quiet click. Meeting-default follow-ups are how this inbox learned to ignore vendors, especially around SKO and a quiet click.

How do I close the thread without sounding hurt?

Offer to hold until SKO or quarter planning and name the date. If they still don't answer, stop. Sales VPs talk. Your reputation with that person matters a logo on a slide, especially around SKO and a quiet click. Adult hold language often gets the late reply that a guilt trip never will, especially around SKO and a quiet click.

Can I mention billing or a true-up in this follow-up?

Only if the click was on pricing or a seat calculator. Then one line about true-up versus unused seats is fair. Don't open a collections vibe on a curiosity click, especially around SKO and a quiet click. Billing belongs in the ask as a number they already own, not as a threat. Warm and specific still beats clever.

Last updated 2026-09-02 · Reviewed by Sales Email Template editors

SaaS · Sales VP · Clicked But No Reply

Follow-Up Email When a SaaS Sales VP Clicked and Didn't Reply

A follow-up email to a SaaS sales VP who clicked and didn't reply is a short, kind note that names one stall and asks a cheaper question. Don't restack the pitch. They already peeked. Guess unused seats, a frozen sandbox, or a CS queue they didn't want to babysit, then offer a hold they can take in one word.

Copy-ready template

Subject

Unused AE seats at [Company Name], or hold?

Body

Hi [First Name],

I'll keep this gentle. Someone on your side opened the seat note, then the thread went quiet, which in SaaS sales orgs often means the sandbox never launched or CS is still sitting on activation numbers.

Want a one-page map of unused seats versus AE headcount, or should I hold until after [SKO / Quarter Close]? A later or hold is plenty.

[Your Name]
[Your Title]

Why this follow-up works

The subject is a number they already defend in forecast, not a product category.
You guess a real stall (sandbox or CS queue) instead of celebrating the click.
The ask is a page, so they can forward it without booking you.
Hold language makes a no cheaper than ghosting through quarter close.
Warmth without a recap of email one keeps you from sounding like a sequence.

When should I send this to a SaaS Sales VP?

Give the click two business days unless they opened it during a SKO week, in which case wait until that circus ends. Same-hour bumps read as pixel theater. If they stay silent twice, close with a hold until quarter planning or the next SKO, and mean it. Weekly drips through a close week get your domain a filter. Avoid Monday 8:00 forecast huddles and Friday dump hours. A 10:00 Tuesday note is more likely to get a four-word later. That's a win. Take it. If RevOps parked new vendors until after the billing cutover, believe it and leave a reopen date. Do not stack a third pitch into a clicked thread. Archive energy is warmer than another feature list, and it often earns the late reply a sequence never gets.

What this Sales VP actually cares about

This person is already late on a forecast, a ramp complaint, and a CS ticket about who owns activation. They open mail between standups and a deal desk ping. The first two lines have to name seats or a sandbox, not a vision for selling. They decide in seconds whether you add work or remove it, especially around SKO and a quiet click. Don't CC the CRO to apply heat. Don't mock last quarter's trial in a sentence they'd have to defend in Slack. Their credibility with AEs is the real product. Protect it. Then stop. A hold until after SKO is a gift in this seat, and they will remember who offered it without a guilt trip. If your note would look naive in a QBR packet, rewrite it before you hit send.

How SaaS changes the note

SaaS sales VPs live inside unused seats and a CS queue that never quite matches the forecast they just promised. A click that doesn't become a reply is usually not a snub. It is a sandbox that legal has not opened, an activation report CS said would land Friday, or a billing true-up they do not want to explain to finance while AEs are already in the field. Your follow-up has to sound like you have sat in a pipeline review: which seats are dark, who owns onboarding, whether the trial workspace even has sample data. Do not talk enablement as if they have not bought three tools that demoed well and then sat idle. Quiet after a click often means they forwarded the tab to RevOps and did not want to babysit a vendor thread on top of a yellow week. Shrink the work. A one-page seat map they can drop in Slack is a gift. A 30-minute tour is homework. If you cannot name the stall in one sentence, wait until you can. Seat waste and time-to-first-value survive a skeptical buyer. Feature lists do not. Tools that looked sharp in a sandbox and died in week-three activation trained this inbox to flinch. Write as if that already happened, and stay kind about it.

Customization tips

Put the real SKO, QBR, or quarter-close date in the placeholder.
If they clicked pricing, talk seats. If they clicked a sandbox invite, talk activation.
Don't mention the tracking pixel. They already assume you saw it.
Name the AE team or region they run, not your win-rate philosophy.
Send Tuesday or Wednesday morning in their timezone, never Monday forecast hour.

Common mistakes

Announcing that you saw them click, like a camera in the ceiling.
Restacking the original pitch and calling it a bump.
Sending a 30-minute Calendly as the entire follow-up.
Pitching a full sales methodology while their sandbox is still empty.

How this scenario compares

Dimension	For this template
Best send window	Two business days after the click, not during SKO
Ideal length	Under 90 words, one question
Primary ask	A one-page unused-seat map they can refuse
Unlike a no-response bump	You have a signal. Use it to name seats, not to invent interest.
Unlike a CTO follow-up	Talk activation and seats, not identity or pager load

Questions people ask before they hit send

No. They already assume the pixel fired. Name the topic they likely opened, like seats or the sandbox, and ask a cheaper question. Surveillance language trains them to filter you. Curiosity about unused licenses is warmer and still specific. Let them keep a little privacy while you stay useful.

Related templates

Want a custom draft instead? Try the email generator. Word count on this page: 1286.