Email sequence templates
PR pitch: a researched story and short follow-ups
Match a story to the publication, support it with available evidence, and respect editorial preferences.
Adapt the example to your audience and check every claim before sending. Use the copy button on each message, or download its body as text. Copy the initial subject separately. Merge fields are preserved for your campaign editor.
Use a short pitch tied to the publication’s beat, with evidence available for inspection. Make it easy for an editor to accept the material or decline the enquiry.
The newsroom, sender and demonstration below are fictional. They are not a news announcement, measured study or claim about a real publication’s preferences.
Prepare the story and its evidence
This example assumes the newsroom’s current pitch instructions accept small-business software stories. The sender has a product walkthrough explaining how Gmail campaign follow-ups use sending capacity.
Replace that angle if it does not fit your real evidence. Keep any simulation clearly labeled. Do not offer data, screenshots or interviews you cannot provide.
Only firstName is merged, with there as the fallback. Review every newsroom’s submission preferences manually.
Message 1: offer the story material
Initial subject: Gmail campaign capacity walkthrough
Hi {{firstName | there}},
Your pitch page says you cover software workflows for small businesses.
I am building ColdMerge, a Gmail outreach workspace. I can share a walkthrough showing how a campaign's first messages and follow-ups use the same mailbox's sending capacity.
The example separates product controls from Google's sending limits. It is a labeled demonstration, not a study of customer results.
Would that material fit your coverage?
Thanks,Mubarak
If you prefer no further pitches from me, reply and I will stop.This is draft example copy. Send it only after the described material exists and the first sentence is true for the intended newsroom.
Message 2: clarify the evidence
Hi {{firstName | there}},
One clarification on the walkthrough: it includes the assumptions behind the example and links to the product behavior and Google guidance.
I am not offering an inbox-placement result or a claim that the example represents all senders.
If the topic fits, I can send the material here for you to review.
Mubarak
Reply if you would like me to stop sending pitches.Do not send if a reply, bounce or opt-out has ended the enquiry. Verify the material and source links again before following up.
Message 3: end this pitch
Hi {{firstName | there}},
I will close this pitch after this message.
If the workflow example is useful for a later piece, you can reply here and I can confirm what material is currently available.
Thank you,MubarakDo not treat silence as permission to reuse the pitch indefinitely or announce that the publication is interested.
Check the angle and deliver the actual material
| Template element | What must be true |
|---|---|
| Publication’s beat | Current instructions or reporting supports the proposed topic |
| Story material | The walkthrough exists and the editor can inspect it |
| Claims | Product and Google facts have current sources |
| Scope | A demonstration is labeled, not presented as representative research |
| Access | Any exclusive or embargo terms are explicitly agreed |
| Signature | The named person is authorized and available to answer |
After a request for the material, reply personally:
Hi Alex,
Here is the walkthrough: [insert the actual permitted link].
It includes [the demonstration assumptions] and [the source references]. It illustrates one sending plan; it is not a customer study or an inbox-placement test.
I can answer questions about the product behavior. Let me know if another part of the workflow would be useful to inspect.
MubarakReplace the square-bracket prompts with real material before sending. A request for the walkthrough is an information request, not an agreement to publish. Use the follow-up sequence guide to set delays and understand when later messages stop.
Keep the thread and response meaningful
Follow-ups use the first message’s Gmail thread and mailbox, with no separate subjects. A detected human reply stops the current campaign’s remaining follow-ups. Automatic replies do not. See Follow-up sequences.
If an editor requests material, reply manually and supply exactly what you promised. Record a request to stop as opted out. A request for information is not a commitment to publish.
Complete list research, prepare the promised evidence and assign conversation ownership before launch. Use the campaign launch guide to review audience rules and message previews. The template organizes a pitch; it does not create a newsworthy claim.
Check opt-out controls before launch
ColdMerge’s unsubscribe footer and one-click header start off. Review and enable the appropriate controls before sending. A reply asking to stop does not automatically suppress the address across campaigns: choose Mark as opted out manually. That suppression applies across the Organization. See How unsubscribes work for the configuration and recipient behavior.
No card required to start. Invited testers get the same 14-day free trial, and the plan is $0.99 a month if you subscribe.