How many times should I follow up with a Department Head (replied then went silent)?

Send it the same day. Thanks that arrive a week later feel like a task. Give it a week unless they named a date. Then write on that date, not the day after you got impatient. After that, send a breakup note and archive it. A department head who wants it will answer a clean close more often than a

How soon should I send a thank-you after a meeting?

Same day, ideally within a few hours. Waiting until the next morning is fine if the meeting ran late. Waiting until Friday for a Monday meeting makes it look like a chore. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

Why do prospects reply once and then disappear?

Often they needed to check with someone, a fire started, or your last ask was bigger than they meant to take on. A good follow-up shrinks the next step and references what they already said so they don't have to reload context.

Is it okay to send this thank you on LinkedIn instead of email?

Yes if this department head is actually active there and the thread isn't about long attachments. Keep the LinkedIn version even shorter. Don't paste the full email. One context line and one question is plenty. Name the stall they care about, offer one small next step, and stop before the thread feels like a sequence.

What should I never say in a Construction thank you?

Don't pretend you've run a job if you haven't. They'll test you. Going over their head in the same thread. Don't forward the whole thread with 'friendly bump' and nothing else. Those three mistakes show up constantly in Construction inboxes and they all read as "this was templated."

Construction · Department Head · Replied Then Silent

Thank You for Construction Department Head: Replied Then Si…

A thank-you email names the specific thing someone did and, when it's natural, points to one next step without turning gratitude into a pitch. For Construction teams, the version that works for replied then went silent has to respect Don't send long emails during pour days. Write to the department head like they already have a full calendar and a

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

We write templates the way we wrote emails on quota: short, specific, and easy to forward. When we cite research below, it is because the number changes how a buyer reads your note, not to pad the page.

Sources: HubSpot sales email benchmarks; Gong follow-up research

Why does this thank you work for a Construction Department Head?

Separate thanks from selling. If you must include a next step, keep it optional.
Speaks to bid follow-up that dies, subs who go dark, and paperwork that lags the jobsite instead of a generic "value prop."
Fits how a department head actually reads: Give enough context that they can forward the email upward.
Quote their last sentence and answer it. People reply to their own unfinished thought.
Name the exact help they gave so it doesn't sound templated.

When should I send this to a Construction Department Head?

Send it the same day. Thanks that arrive a week later feel like a task. Give it a week unless they named a date. Then write on that date, not the day after you got impatient. For this combo, treat "5-7 days, or the date they named" as the default, then adjust around decisions bunch around bid dates and pay apps, not your sequence. If you're emailing a department head, Give enough context that they can forward the email upward.

What this Department Head actually cares about

A department head in Construction is protecting their team's load and their standing with leadership. They sit between strategy and the people doing the work. They need cover to say yes and a way to not look reckless. The hook that earns a look is a department KPI, a staffing bind, or a tool the team already hates. The ask should stay at this size: a working review they can invite a deputy to. Delete trigger: Going over their head in the same thread. a department KPI, a staffing bind, or a tool the team already hates

How Construction changes the note

Construction buyers are PMs, estimators, and owners who live in change orders and weather. Don't send long emails during pour days. Be concrete about schedule and docs. Fluffy 'partnership' language wastes a PM's time. A credible proof point in this vertical sounds like: shortened bid-follow-up cycles from 11 days to 4 for a regional GC. Watch the language. Words that land here include bid, RFI, retainage, punch list, GC, change order. Decisions bunch around bid dates and pay apps, not your sequence. Words that work: bid, RFI, retainage, punch list, GC, change order. Decisions bunch around bid dates and pay apps, not your sequence.

How should I customize this template before I send it?

Replace the pain line with a subcontractor who submitted a bid and then waited in silence for two weeks.
Keep the tone respectful of internal politics without being coy.
Handwritten notes still stand out for in-person meetings.
Time it for 5-7 days, or the date they named. Give it a week unless they named a date. Then write on that date, not the day after you got impatient.
Don't pretend you've run a job if you haven't. They'll test you.

What mistakes should I avoid with this replied then silent note?

A generic 'thanks for your time' is forgettable.
Don't forward the whole thread with 'friendly bump' and nothing else.
Don't pretend you've run a job if you haven't. They'll test you.
Going over their head in the same thread.

How does this replied then silent scenario compare?

Dimension	For this template
Best send window	5-7 days, or the date they named
Ideal length	Give enough context that they can forward the email upward.
Primary ask	a working review they can invite a deputy to
Industry metric to cite	win rate on bids, RFI cycle time, and retainage aging
Tone	Respectful of internal politics without being coy.
Unlike no response	They already spent social energy. Treat them like a conversation, not a lead.
Unlike after proposal	You may not have a document on the table yet. Don't invent a buying process.

What should I copy and send?

Copy-ready template

Subject

Thank you for [specific thing]

Body

Hi [First Name],

Just a note to say thank you for [intro / time / review].

I'm writing because a bid due date, a failed inspection, or a GC switching software. If it's useful, I can share the [notes / one-pager / intro] we mentioned so you have it in writing.

Quote their last sentence and answer it. People reply to their own unfinished thought.

Hope the rest of your week is quieter than the start.

Best,
[Your Name]
[Your Title]
[Your Company]

Questions people ask before they hit send

Name the situation and the business object, not your excitement. Something like "Thank you for [specific thing]" outperforms "Just checking in" because a department head can decide from the preview text whether it's worth opening. Keep it under 50 characters when you can.

Related templates

Want a custom draft instead? Try the email generator.