6 cold email subject line examples—and the messages behind them
A useful cold email subject line accurately describes the message that follows. Start with a relevant reason to write, then choose words that help the recipient understand that reason. Curiosity is not a substitute for accuracy.
Use a real observation, a specific resource or an honest question. Avoid invented referrals, fake reply prefixes and unsupported claims of proven performance.
Six examples with clear conditions
These are complete illustrative messages, not winning variants from a customer experiment. Adapt the situation and offer to evidence you can verify. Add your accurate sender identity and the appropriate opt-out mechanism to the message you actually send.
01 / A relevant resource
Subject: Dock scheduling worksheet Your public operations role includes dock scheduling across sites. We have a one-page worksheet for mapping that workflow. Would a copy be useful?
When it fits: Use when the role listing and resource both exist.
02 / A specific problem to explore
Subject: Manual CRM cleanup We help operations teams review duplicate-record workflows. Is CRM cleanup owned by your team, or should I ask someone else?
When it fits: Do not claim their CRM contains duplicates without evidence.
03 / An accurate referral
Subject: Introduction from Jordan Jordan suggested I contact you about warehouse appointment scheduling. Would it be useful if I sent the planning worksheet we discussed?
When it fits: Only use the referrer’s name when the referral actually happened.
04 / A useful comparison
Subject: Scheduling options for multiple sites We put together a comparison worksheet for teams reviewing scheduling across locations. It covers ownership, exceptions and reporting. Would you like a copy?
When it fits: Use only if you can supply the promised comparison.
05 / A direct role question
Subject: Who owns partner onboarding? I’m trying to reach the person responsible for partner onboarding. Does that sit with your team? If so, I can explain why I’m asking in a short reply.
When it fits: Use when the role genuinely needs clarification, not as fake personalization.
06 / A requested follow-up
Subject: The worksheet you requested Here is the worksheet you asked for. The example row shows how to document the current process before comparing options. Which section is most relevant to your team?
When it fits: Use after a real request; it is not an initial cold-email opener.
Download the testing worksheet (.csv)How should you test subject lines?
Change the subject while keeping the audience criteria, body, sending conditions and observation window comparable. Assign eligible recipients randomly where practical. Do not send both variants to the same person and then treat those observations as independent.
Write the question before you send: “Does the resource-led subject produce more relevant human replies than the role-question subject for this audience?” Record the actual subjects and count unique delivered recipients, human repliers and positive repliers for each variant.
| Test element | Keep a record of |
|---|---|
| Audience | Selection criteria, exclusions and assignment method. |
| Message | Exact subject and body for each variant. |
| Sending context | Provider, time window and any configuration differences. |
| Outcome | Unique delivered recipients, human replies and positive replies. |
| Interpretation | Sample size, uncertainty and any differences beyond the subject. |
The worksheet contains one completed planning example and blank result fields. It deliberately contains no invented lift. For the distinction between tracked opens and conversation outcomes, read email open rates vs reply rates.
Review the subject and body together
- Can the recipient understand why this message is relevant to their role?
- Does the body deliver the resource or explanation promised by the subject?
- Is every named referral, observation and previous interaction real?
- Could the subject be mistaken for an existing conversation or an internal instruction?
- Does the next-step request match what you can actually provide?
Google’s sender guidance says subjects and headers should accurately represent the content and warns against using reply or forward prefixes unless the message is a real reply or forward. Do not add “Re:” to a first message to imply a conversation that never happened.
Review the complete draft with the cold email grader, then use the cold email launch checklist to check the list, sending setup and response workflow. A subject-line review is one part of launch quality, not a delivery guarantee.
Is there one best subject-line length?
A short subject can be clear or vague; a longer one can be specific or overloaded. Check how it reads on mobile, keep the central meaning early and test within the audience you serve. This guide does not claim a universally optimal character count.
Should I put the person’s name in every subject?
Only when it improves the meaning. A name token does not establish relevance. A specific, truthful resource or business question is often a better starting point for the message.
Put the workflow into practice
Bring your audience, offer and current process. We can review where the campaign needs a clearer decision or a stronger operating setup.
Apply to work with ReplyLead →