How to Build a Podcast Guest-Booking Pipeline

How to Build a Guest-Booking Pipeline

A podcast guest pipeline should make editorial fit, outreach permission, scheduling, consent, preparation, recording readiness, release review, and follow-up visible. Its purpose is to create better conversations with less rush, not to maximize the number of people contacted.

flowchart LR
    A["Candidate"] --> B["Qualified"]
    B --> C["Invited"]
    C --> D["Interested"]
    D --> E["Scheduled"]
    E --> F["Recording ready"]
    F --> G["Recorded"]
    G --> H["Release review"]
    H --> I["Published and followed up"]
    B --> J["Hold or decline"]
    C --> J
    D --> J

Start with editorial fit

Define the audience, the episode promise, and why this person is positioned to help deliver it.

Record a relevance thesis in one sentence. "The guest is famous" is not a thesis. "The guest operated the system this episode is trying to explain and can describe its tradeoffs" is stronger.

Verify identity, current role, work, and the source that established the fit. A conference biography or social profile may be outdated. Use a company page, personal site, recent publication, professional record, or direct confirmation when possible.

Rank candidates by relevance, evidence, perspective, and audience value. Reach can matter to distribution, but it should not outrank the quality of the conversation.

Separate qualification from contact authority

Finding a public email address does not mean repeated outreach is welcome. A profile can establish identity without authorizing recording, publication, newsletter enrollment, or future marketing.

Record the public contact route, the reason it appears appropriate, any introducer, and any do-not-contact state. Use the channel the person or their organization designates for requests.

If an invitation promotes a commercial show, service, or website, review whether commercial email rules apply. The Federal Trade Commission's CAN-SPAM compliance guide says the law covers commercial email based on the message's primary purpose and does not create a business-to-business exception.

This page is not legal advice. Outreach rules differ by jurisdiction, channel, content, consent, and organizational policy.

Make the invitation specific and bounded

The first message should identify the host, show, audience, proposed topic, reason for inviting this guest, expected duration, recording format, likely publication surfaces, and a simple way to accept or decline.

Do not pretend to know the person. Do not manufacture urgency. Do not hide a sales pitch inside an interview request.

Riverside's guest preparation guide suggests organizing potential guests, researching the show's niche, contacting people through appropriate channels, and explaining the format. Its booking templates are examples, not proof that one message fits every audience or jurisdiction.

The invitation should be easy to ignore. A respectful pipeline does not punish silence.

Set the follow-up rule before sending

Choose the maximum number of follow-ups, the minimum time between them, and the conditions that end outreach.

A decline, opt-out, do-not-contact request, channel restriction, wrong-person reply, or clear lack of fit should close the sequence. Preserve the suppression state so another teammate or agent does not restart it.

Do not use open tracking, enrichment, or personal data merely because a tool makes it available. Define what is necessary, how long it will be retained, and who can access it.

Build enough lead time

Use a twelve-week view even if the show publishes weekly.

The first weeks can hold qualified candidates and invitations. The middle weeks can hold accepted guests, scheduling, and research. The final weeks should contain recording-ready and recorded episodes.

The exact numbers depend on acceptance rate, guest complexity, team capacity, and release cadence. Do not treat a target pipeline size as a universal benchmark.

Maintain a qualified backup. A backup is not someone pressured to record at the last minute. It is a guest or solo topic that has already passed its own readiness gates.

Define every state by evidence

"Interested" should mean the guest or representative responded positively. "Scheduled" should include a confirmed time, time zone, participants, and route. "Recording ready" should include the brief, consent state, technical instructions, accessibility needs, topic research, and recovery plan.

"Recorded" should not mean publishable. The episode still needs audio review, fact checking, privacy review, assets, title, description, transcript, links, and the agreed release process.

The [[Guest Booking Pipeline Schema]] contains the full record. Keep its minimum fields in the system of record rather than hiding decisions in email threads.

Treat consent as more than a calendar event

Before recording, confirm the guest understands the format, whether the conversation is live or edited, where it may appear, and how clips, images, transcripts, and promotional excerpts may be used.

The SPJ Code of Ethics distinguishes legal access from ethical justification and asks publishers to consider harm, privacy, and the permanence of publication. It is voluntary ethical guidance, not a substitute for law or a guest release.

For recording law and jurisdiction differences, consult the Reporters Committee recording guide and qualified counsel when needed.

Close every outcome

After recording, send the expected release window and a contact route for factual corrections. After publication, send the canonical page and thank the guest without making promotion a condition of the relationship.

Record whether the relationship should be revisited, held, or closed. Remove personal data that no longer serves a defined purpose.

E024 shows why one-week-at-a-time booking made an early show fragile. E069 extends the idea into a deliberate guest strategy. E112 demonstrates the additional evidence and preparation required when a guest topic touches property risk, safety, and consequential claims.

Continue to [[How to Prepare and Host a Better Podcast Interview]] after a guest accepts. Use [[How to Build a Sustainable Podcast Production System]] to connect the booking board to recording, review, release, and recovery.

This guide was developed with AI assistance from the preserved E024 transcript, current FTC, SPJ, Reporters Committee, and Riverside guidance, and the linked pipeline schema. Dalton Anderson remains the author. It is not legal advice, permission to contact any person, or a universal outreach policy. Editorial, outreach, privacy, legal, source, accessibility, production, and founder review are required before publication or use. Publication is not authorized.