Media · Department Head · After Demo
Thank You for Media Department Head: After Demo
A thank-you email for a Media Department Head (after a demo) is a short message that reopens the thread without making them do extra work. 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. In this setting, that means speaking to flights that stall, brand-safety
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 Media Department Head?
- Name the exact help they gave so it doesn't sound templated.
- Speaks to flights that stall, brand-safety scares, and follow-up that reads like leftover kit copy instead of a generic "value prop."
- Fits how a department head actually reads: Give enough context that they can forward the email upward.
- Replay the two moments they leaned in, and the one concern they named.
- Separate thanks from selling. If you must include a next step, keep it optional.
When should I send this to a Media Department Head?
Send it the same day. Thanks that arrive a week later feel like a task. Same day with the recap. A value bump 3 days later if they went quiet. For this combo, treat "Same day, then 3 days if silent" as the default, then adjust around upfronts and flight dates create urgency. random tuesdays don't. 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 Media 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. If your note would embarrass them in a team channel, rewrite it.
How Media changes the note
Media buyers are sales leads and operators selling attention in a market that keeps changing the rules. They can smell leftover media-kit language. Bring delivery math or a sharp audience observation. A credible proof point in this vertical sounds like: rescued two paused IOs by sending a delivery diagnosis instead of another one-pager. Watch the language. Words that land here include IO, flight, brand safety, CPM, makegood, inventory. Words that work: IO, flight, brand safety, CPM, makegood, inventory. A thread that ignores flights that stall, brand-safety scares, and follow-up that reads like leftover kit copy reads like every other vendor bump.
How should I customize this template before I send it?
- Replace the pain line with a publisher whose advertiser follow-up still leads with 'unique storytelling'.
- Keep the tone respectful of internal politics without being coy.
- Skip gifts unless you know their company policy.
- Time it for Same day, then 3 days if silent. Same day with the recap. A value bump 3 days later if they went quiet.
- Don't promise a viral moment. Promise a clean flight.
What mistakes should I avoid with this after demo note?
- A generic 'thanks for your time' is forgettable.
- Don't send a 19-page deck that relitigates features they skipped.
- Don't promise a viral moment. Promise a clean flight.
- Going over their head in the same thread.
How does this after demo scenario compare?
| Dimension | For this template |
|---|---|
| Best send window | Same day, then 3 days if silent |
| 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 | CPM, fill, and campaign delivery against IO |
| Tone | Respectful of internal politics without being coy. |
| Unlike after meeting | They have product context now. Speak to what they saw, not to a generic intro. |
| Unlike after proposal | Pricing may not be on paper yet. Don't jump to 'ready to sign.' |
What should I copy and send?
Copy-ready template
Subject
Grateful for today's [meeting/intro/help]
Body
Hi [First Name], Thanks for [specific action]. It actually unblocked [outcome]. In Media, that usually shows up as flights that stall, brand-safety scares, and follow-up that reads like leftover kit copy. If it's useful, I can share the [notes / one-pager / intro] we mentioned so you have it in writing. Given this is after a demo, ask who else needs to see it, or whether a narrower use case is the better start. Thanks again. I'll keep you posted on [next step]. Best, [Your Name] [Your Title] [Your Company]
Questions people ask before they hit send
Helpful and specific to what they clicked and asked. They can smell leftover media-kit language. Bring delivery math or a sharp audience observation. The department head is guarding their team's load and their standing with leadership, so the ask should stay at "a working review they can invite a deputy to." If you copy a generic template and only swap
Related templates
Want a custom draft instead? Try the email generator.