Best Practices for Journalist Outreach in an OmniCampaign

Use this checklist after journalist outreach has been added to a PodPitch OmniCampaign. For the start-to-finish workflow, see How Journalist Outreach Works in an OmniCampaign.

Build a complete profile

Include verified background, expertise, achievements, current facts, approved links, and topics the profile can discuss accurately. Remove expired offers and claims that cannot be supported.

Use a timely news hook

A news hook should explain what changed, why it matters now, and who is affected. Keep it specific and supported by the profile or linked source material.

Refresh or pause the journalist channel when the hook expires.

Validate targeting

Use only the journalist controls shown in the current OmniCampaign. These can differ from podcast and newsletter controls.

Review a sample of recommended journalists and confirm:

• recent coverage matches the story;
• the journalist and outlet are active;
• the beat, publication, language, and geography fit;
• any traffic or audience range is appropriate; and
• the same contact is not being pitched repeatedly across overlapping campaigns.

Targeting fields are signals, not guarantees. Remove irrelevant recommendations before sending.

Review the pitch as a journalist

Confirm the subject, news hook, claims, statistics, links, sender, first- or third-person perspective, and signature.

Keep the message concise and useful. Do not send a podcast guest pitch unchanged to a journalist.

Start carefully

Use Manual Mode while testing a new story angle. Enable Smart Mode only after the profile, targets, and generated pitches have been reviewed.

After a material profile, hook, or targeting change, rewrite eligible pending pitches and review examples before resuming.

Manage replies in context

Read the entire thread and confirm the correct profile, story, and publication before responding. Journalist replies arrive in the connected mailbox and, where supported, PodPitch reply tools.

Updated on: 25/08/2026