Podcast guest pitch template for support leaders
A free, copy-paste podcast guest email template for booking support leaders. Subject lines, full email body, follow-up script, FAQ. Written for hosts who actually book guests.
Who this template is for
Heads of Support, Customer Experience, and Customer Success. If you're booking support leaders as podcast guests — for an interview show, narrative show, or panel format — this template is built for the cold first touch when you don't have a warm intro.
Every winning podcast guest email to a head of customer support cites something concrete the guest made in the last 60 days. The template below structures that reference around a 30-minute recording ask in under 160 words.
Episode topic angles that land
Head of Customer Supports ignore "tell us your story" pitches. These angles consistently get replies because they ask for operator detail, not narrative:
- The escalation that changed their team
- How they actually measure CSAT honestly
- Hiring the first ops person
- What they wish product teams understood
The specific reference you need before sending
Often under-recognized by podcast media; ironically, more selective about which shows they engage. The fix is a concrete reference to recent work. Acceptable proof points include a Support Driven contribution; a recent LinkedIn essay; a panel or webinar. If you can't find one of those within the last 60 days, this is the wrong week to pitch this guest — wait until they ship something new.
Subject line options
Three subject lines built for under 55 characters, lowercase, no clickbait: "{{first_name}} — 30 min for {{podcast_name}}?", "Podcast invite re: your {{specific_post}}", and "Quick chat about support ops?". Each is short enough to render fully on mobile and specific enough to clear pattern-matching delete.
The full cold-pitch template
Hi {{first_name}}, I host {{podcast_name}}, {{audience_short}} listen weekly. Your post on {{specific_thing}} surfaced operator reality most "customer-obsessed" content avoids. I'd love to record 30 minutes on the ops side: the escalation that changed your team, how you measure CSAT honestly, what you wish product teams understood. Editorial format, peer-to-peer audience. Past guests: {{name_1}}, {{name_2}}. Audience ~{{listener_number}} per episode. Three windows in the next month? {{your_name}}
The follow-up (send 5–7 days later)
Reply to your own thread, no new subject. Cap at one follow-up — anything more trades reply rate for trust. Suggested body: Hi {{first_name}}, gentle bump. Promise this isn't a vendor pitch. {{your_name}}
Frequently asked questions
What's the best podcast guest email subject line for support leaders?
Short, specific, and human. "{{first_name}} — 30 min for {{podcast_name}}?" works because it references something they actually shipped. Generic "love your work" subject lines from a stranger get archived on sight.
How long should a cold podcast pitch to a head of customer support be?
Under 160 words. support leaders scan in under 8 seconds — anything longer is a delete. The template above is intentionally tight: hook, ask, format, close.
How many follow-ups are okay when pitching support leaders?
One follow-up about 5–7 days after the original is the practical maximum. After that, you're trading reply rate for trust. Add the prospect to a 6-month re-pitch list instead of sending a third email.
How do I find a head of customer support's email address?
Check their personal site (/about, /contact, footer), LinkedIn contact info, and recent newsletter reply-to address. If nothing surfaces, an email finder like Hunter or Apollo plus a verifier like NeverBounce is the standard playbook.