Cold Email Subject Lines: Examples, Rules and Spintax

A good cold email subject line tells the recipient what the email concerns and gives them a reason to read it. Keep three rules: match the body, use a detail you can verify, and read the final subject after every personalization field has been filled.

Start with the recipient's task or a real reason for contacting them. A hiring message can mention the open role. A support offer can mention ticket coverage. A referral subject can name the person who actually introduced you. Keep the same subject promise in the first sentence of the email.

Below are 50 subject lines grouped by situation, followed by checks for length, merge fields, spintax and testing. Choose the pattern that fits the message you intend to send, then evaluate its replies on your audience. A subject line alone cannot establish relevance or guarantee inbox placement.

For the message itself, what cold email is covers the opening, offer and request. Keep the subject consistent with those parts.

Subject Line Examples by Situation

Use the exact field names your sending tool stores. Before import, verify that the data supports any event, referral or company detail in the subject. The body should explain why that detail matters to the recipient.

A Trigger Event You Can Verify

A public event can explain why you are writing. Confirm the company's needs in the message. Keep the subject factual. Use the body to ask whether the need exists. For a job listing, confirm it is still open and that the recipient is responsible for it; an outdated event turns personalization into an obvious data error.

A Referral or Mutual Connection

The first three subjects require a real referral. A mutual social connection does not establish an introduction or an endorsement. If you only noticed a shared group, use that factual context and explain your own reason for writing. Do not borrow the connection's credibility by implying permission they never gave.

A Question the Body Answers

Questions should be answerable without a meeting. If the subject asks who owns support, the body should make that routing request easy. If you want to sell a service to that owner, identify yourself and explain the connection. Avoid sending a vague question whose body immediately changes to an unrelated pitch.

A Role, Task or Problem

These subjects can work without a dramatic trigger. Their usefulness comes from a clear connection between the recipient's work and your message. Check the role and responsibility before sending: a company name is accurate personalization, but it does little to help a recipient who never handles the task.

Short Two- or Three-Word Subjects

A short subject makes the topic visible with little space. It also removes context. Pair it with a precise opening sentence so the recipient can immediately connect the subject to their role. “Helpdesk backlog” should lead to a question or offer about the backlog; it should not imply you have inspected internal ticket data.

A Name or Direct Address

A name-only subject leaves the recipient with little information. Treat it as a pattern to test against a topic-led subject. Check that the stored first name is a person's name, with sensible capitalization, and that the preview does not display a raw variable. A name is not permission to imply an existing relationship.

For complete messages to accompany these subjects, use cold email templates and samples. The subject and body need to be reviewed together: changing one often changes what the other should say.

How Long a Cold Email Subject Line Should Be

Use the shortest version that preserves the useful topic. There is no single character count that guarantees a full preview across Gmail, Outlook, desktop clients and phones. Font size, screen width, sender name and the inbox's layout affect what a person sees.

Send the rendered message to accounts you control and inspect it on a phone. Ask whether the visible part makes sense before the end is cut off. Put the useful task or event early. If the subject needs its final words to become accurate, shorten the opening so the useful text appears first.

Check a long company name as well as a short one. A template that looks brief with a sample value can become unwieldy for a lead whose organization has a long legal name. Clean company fields before import and use the name the recipient recognizes, while retaining accurate records in your lead source.

The preview also contains the sender and opening text. Read the combination as the recipient sees it. Repeating the same vague phrase in all three places uses space without adding context. Give the opening sentence the job of explaining the reason for contact.

Personalization Fields and What Breaks Them

Match variable names to the imported column names exactly. Check whether your tool distinguishes firstName from first_name, and company from companyName. Preview the subject against the actual imported contact fields before sending.

Check missing values and junk values before activating. “N/A,” a job title stored as a company, and an all-caps personal name can all be technically nonempty while producing an unusable subject. Read the subject with the recipient data rendered.

A fallback such as {{firstName|there}} only helps if the tool supports that syntax and the resulting line reads naturally. “There, about support” is awkward. For a name-led family, fixing or filtering missing names may be a better operational choice. For a company-led family, a complete topic-only subject can be another version to test.

The merge variable render check skill maps fields, checks the fill rate and renders real leads. Use samples covering the emptiest record, the longest name, a long company and normal records. Include the signature and body in that review because an accurate subject can still lead into a broken email.

After moving a campaign between tools, repeat the check. Import settings, supported variable names, fallback syntax and spintax support can differ. Send from the actual campaign configuration to a mailbox you own and read the delivered subject. Preserve that test with the template version you approved.

Subject Lines to Avoid

Google's sender guidelines say subject lines should accurately represent the message, and prohibit misleading thread markers on messages that are not actual replies or forwards. In the US, the FTC's CAN-SPAM guidance likewise requires subject lines to reflect the content accurately.

All caps and symbols are also a readability decision. Do not treat every word on a “spam words” list as a proven cause of filtering. Inspect the actual message, authentication and observed placement. The cold email copy checker helps review copy risks and mismatched claims before sending.

Spintax Subject Lines for Volume

Spintax lets one template produce several subjects by choosing between alternatives. Keep a few structural families, such as name plus question, topic plus company, or a short question. Give every family a label you can use when counting campaign replies.

A family should represent a clear communication choice. “Support coverage” and “Who owns support coverage?” ask different things of the recipient. Swapping “quick” for “short” is a wording change within the same shape. Keep those levels visible when deciding what a test result means.

Here is the topic-noun pattern from our subject line spintax generator skill:

{{RANDOM|support|helpdesk|IT}} {{RANDOM|coverage|backlog|setup}} at {{companyName|your team}}

The two random blocks produce nine combinations before company personalization: three topic options multiplied by three task options. Some combinations suit a particular offer better than others. Remove options that change the promise or do not fit the body. Inspect the actual renders before deciding the template is ready.

For a sending tool that supports single-brace alternatives, the structural equivalent is:

{support|helpdesk|IT} {coverage|backlog|setup} at {{companyName}}

Verify the sending tool's merge-field syntax separately. A single-brace spintax pattern does not establish which personalization syntax or fallback it supports. Keep an approved version for each tool you use.

Keep Options Strip-Proof

Put spaces in the literal text between blocks. Avoid option values whose first or last character is a space, because a sender may trim them. This keeps word boundaries stable across renderers:

{{RANDOM|quick|short}} question

Also remove empty alternatives. An empty option can leave punctuation without a phrase or join words that should be separated. Prefer a separate, complete shorter subject when the optional phrase changes the grammar.

Every option in a block must fit every option in its neighboring blocks. Read combinations at those boundaries, then render samples with real leads. A parser can establish that braces and pipes are balanced. It cannot establish that the sentence accurately describes your offer.

Use the free spintax validator for the syntax check and sample renders. Pair it with the merge-field check before sending. If there are duplicate options or repeated phrases, the product of option counts can overstate the number of distinct final subjects; inspect and deduplicate the result.

How Many Variations to Prepare

Our generator skill recommends a handful of variants per family at a few hundred daily sends, and thousands of distinct renders per family when the same family is sent thousands of times a day. Use this working recommendation to reduce exact repetition, then check each rendered subject and the campaign's actual replies.

Keep the number of families small enough to interpret. The skill uses three to eight families and supplies sample renders with filled and empty fields. The meaningful unit for a result is the family and audience together. A large render count does not repair an irrelevant list or an inaccurate message.

If you need more variation, introduce complete phrase choices that preserve the same purpose. Do not multiply random synonyms solely to make the count larger. Recheck the least natural combinations and the longest fields. Retain a few sent samples so you can confirm the tool produced the template you approved.

How to Test Subject Lines

Choose the decision before starting: for example, whether a task-led subject produces more qualified replies than a short question on the same audience. Keep the body, offer, sender setup, schedule and audience criteria comparable. Split recipients between the variants, and retain the family label with each assignment.

Use a consistent observation window and denominator. Count human replies and positive replies separately. Exclude automatic replies from the human total; decide how to classify routing replies before comparing variants. Count each recipient once in the chosen metric, including conversations with several replies.

Open tracking can distort the comparison. Google says it cannot verify the accuracy of third-party open-rate reports. Image loading, privacy features and automated activity can all affect a tracker. Read open tracking and deliverability before adding a tracking pixel solely for a subject experiment. Google sender guidelines

If you use reply rate, keep the denominator consistent across families and make bounces visible alongside it. Define whether you use sent or delivered recipients in the report. For positive replies, keep the classification criteria fixed so that a changed definition does not look like a better subject.

Small differences from small samples are a reason to continue collecting comparable evidence. Look for consistency across relevant batches and inspect the actual replies. A subject that gets many “wrong person” replies may be useful for routing, while a subject that gets fewer but more qualified replies may fit a sales objective better.

If all families perform poorly, check the wider campaign before writing more subjects. Confirm that mail is sending, replies arrive, the list fits the offer and the message is readable. Our email open-rate guide covers that broader investigation.

Follow-Up Subject Lines

For a genuine follow-up, your sequencer may keep a message in the existing thread when the follow-up subject is empty. Confirm the behavior in a sent test: thread handling depends on how the tool sets the message headers and on the receiving client.

Keep the earlier subject if the conversation remains about the same topic. Add useful information in the follow-up body, such as the answer to a likely question or a narrower request. A new subject makes more sense when the topic has actually changed and the new message can explain that change.

Never use a fake reply prefix to manufacture the appearance of a thread. A follow-up to your own earlier message is a real continuation; a first message with invented Re: is misleading. The cold email follow-up sequence guide covers the message sequence and when to stop.

Frequently Asked Questions

What's a good subject line for a cold email?

Use a clear topic, a verified event or a question the body addresses. “Support coverage at your company” works as a pattern when the message actually concerns support coverage. Review the rendered version with real recipient data and evaluate replies on the intended audience.

What are some catchy email subject lines?

A recognizable task or timely fact can give the reader a useful reason to open. Try the event, question and role patterns above when they fit the message. Avoid manufactured urgency or a subject whose promise the body cannot support.

Should I use Re: in a cold email subject?

Use a reply marker only for an actual reply. Google says subjects should accurately represent the message and thread. Test the sequencer's normal follow-up behavior when you want to continue an existing conversation.

Is cold emailing dead?

The useful question is whether a relevant recipient has a reason to respond to this message. Subject lines help set that expectation, while the audience, offer, delivery and follow-up determine the rest. Evaluate the channel through qualified replies and outcomes from your own campaign.

How many subject line variations do I need?

Use a small number of measurable families and enough natural variations for your sending volume. Our generator skill recommends a handful at a few hundred daily sends and thousands of distinct renders per family at thousands of daily sends. Verify the renders and keep the family's purpose consistent.

Sources

Checked October 2, 2026:

• Google email sender guidelines: accurate subject lines, genuine reply markers and open-rate measurement limits

• FTC CAN-SPAM compliance guide: truthful subjects for commercial email

• Subject line spintax generator: structural families, render counts and syntax checks

• Merge variable render check: exact field mapping and testing with real lead records

Prepare your mailboxes, run warm-up and measure campaign replies. Review the subject and body together before activating the campaign.