Define what counts as the same show

Podcast names can vary across websites, directories, and internal spreadsheets. One record may include a subtitle while another uses an abbreviation. If your duplicate check only compares exact titles, the team can mistakenly treat the same show as several opportunities.

Use the official website, host identity, and other verified show details to connect records. Preserve useful alternate names so researchers can find the existing entry. Do not merge records solely because titles resemble each other; different shows can share common words.

Separate a stored prospect from permission to pitch

A show can remain in the research database while being unavailable for fresh outreach. It may already be a host relationship, have an active conversation, or carry an instruction against further pitches. Make that operational state visible before anyone starts writing.

Assign one owner for an active host conversation. New guest ideas should go through that owner, who can decide whether to add them to an existing thread or save them for an appropriate later discussion. This prevents several teammates from independently introducing themselves to the same person.

Track guest-level status as well as show-level status. A host may have declined one guest while remaining open to a different, relevant person. Conversely, a show-level stop request applies across the roster. Your records need enough detail to tell those situations apart.

Build the check into the actual workflow

Before sending, search for the show, official website, host contact, and the proposed guest’s previous outreach. Check existing relationships and active tasks. A duplicate-prevention rule that appears only in training material is easy to miss when the team is moving quickly.

When you discover a duplicate, fix the underlying records and tell the relevant owner. Preserve the conversation history rather than deleting context to make the database look cleaner. If conflicting messages already reached the host, coordinate one clear response instead of letting each sender explain separately.

Review recurring duplicate causes during team check-ins and fix the search or handoff step that allowed the conflict to happen.

  • Maintain one recognizable show identity with verified alternate names.
  • Flag relationships, active outreach, and stop instructions visibly.
  • Assign one owner for each active host conversation.
  • Track each guest’s outcome without losing show-wide restrictions.
  • Run the duplicate check immediately before sending and log the action.