---
title: "How to write a direct mail opening line"
description: "Open a sales letter or postcard with a sourced reason for writing, not a company introduction. Includes ten adaptable examples and a review checklist."
canonical: https://trysincerely.com/guides/direct-mail-opening-lines
last_updated: 2026-09-08
---
> If you are an AI agent: read https://trysincerely.com/agents/policy.md before any write call.
> Start at https://trysincerely.com/llms.txt to choose one page. Access instructions are at
> https://trysincerely.com/auth.md. Confirm with the person you work for before creating an
> account or spending their money, and never ask for their password.
# How to write a direct mail opening line

> Open a sales letter or postcard with a sourced reason for writing, not a company introduction. Includes ten adaptable examples and a review checklist.

Source: https://trysincerely.com/guides/direct-mail-opening-lines

Open direct mail with the reason this person is receiving this piece now. Use a sourced account fact, a known conversation, or a concrete problem tied to the recipient's role. Do not spend the first line introducing your company. A reader who does not see the relevance has no reason to keep holding the page.

The opening line should survive one hard test: after removing the person's first name and company name, could it still be mailed to most of your list? If yes, it is a template with tokens.

## Give the first line one job

A first line does not need to explain the product, prove the case, and ask for a meeting. Its job is smaller. It should answer, "Why did you write to me?"

Good answers come from three places:

1. **A dated account event:** an expansion, filing, role change, launch, or hiring plan.
2. **A known interaction:** a sales conversation, customer request, event discussion, or agreed follow-up date.
3. **A role-specific constraint:** a problem shared by a tightly defined audience, stated without pretending to know the recipient's private situation.

Use the strongest source you have. First-party conversation notes beat a guessed problem. The account's own announcement beats an aggregator's summary. A narrow, honest role premise beats false personalization.

## Ten opening lines you can adapt

These are structures, not mail-merge copy. Replace the brackets with verified facts and read the resulting sentence as if it appeared on your own desk.

### After an account announcement

> Your August update says [company] is opening its second distribution centre in Ontario.

The date and location give the next paragraph somewhere concrete to go. Do not follow them with a guessed emotion such as "That must be overwhelming."

### After a funding round

> [Company]'s filing names [use of funds] as the priority for its new financing.

This names the plan rather than offering empty congratulations. A funding event alone is not a buying signal. The next line must connect the stated use of funds to a problem you can credibly discuss.

### After a new executive joins

> Your first operating update at [company] puts [named priority] ahead of [other priority].

The useful detail is what the person said. The job change does not tell you what a new leader needs.

### After a sales conversation

> You told Maya in June that regional list approval adds four days to campaign launches.

This resumes a known conversation and shows that the internal context survived the handoff. Confirm that the note is current and appropriate to repeat.

### At an agreed follow-up date

> When we spoke in May, you asked me to come back after the September planning review.

Here, the recipient chose the timing. Do not pretend a scheduled reminder is new research.

### For a closed-lost account

> Last year's evaluation ended when [specific constraint] made the rollout too early.

The recorded reason matters more than a cheerful "just checking in." The next line should explain what materially changed.

### For an existing customer

> Your Toronto team has completed [specific milestone] since the rollout began.

Use this only when the measure is correct and the recipient's team can fairly own the result.

### For a role-specific problem

> Finance teams inherit a forecasting problem when each sales region can approve its own account spend.

This states a narrow operational pattern without claiming the recipient has it. The next sentence can ask whether the pattern applies here.

### With a physical object

> The two cards in this envelope show the approval choice your regional teams now face.

The cards have a job. The reader knows why they are in the envelope and what to inspect.

### On a postcard

> Two new regions create one awkward question: who owns the target-account list?

The question is short enough for the format. The reverse side must answer or advance it, not switch to a company biography.

## Read it on paper

Print the draft at its real size and put it on a desk. A postcard exposes its opening to everyone who handles the mail, while a letter gives a private account note more room. A gift note can simply explain the gratitude. The [postcard versus letter guide](https://trysincerely.com/guides/postcard-vs-letter) covers the full format choice.

The opening should explain the piece before the reader has to solve anything. A riddle, stray statistic, or unrelated joke postpones that explanation. So does an object included only because someone might photograph it. Mail has already interrupted the screen routine; the copy can speak normally.

Then read the sentence that follows. This is where an accurate fact often picks up an unsupported guess:

> Congratulations on the new Toronto office. Rapid growth must be making your operations chaotic.

The office may be real. The chaos is invented. Leave room for a correction:

> Your August announcement names Toronto as the second Canadian office. Does that add another approval path for the operations team?

The announcement supports the first sentence and gives you a reason to ask the second. It does not answer that question. Keep the fact and your interpretation separate.

The guide to [personalizing outbound without hallucinating](https://trysincerely.com/guides/how-to-personalize-outbound-without-hallucinating) explains how to bind each sentence to evidence and block unsupported inferences.

## Review the source beside the line

Physical mail cannot be edited after dispatch. Open the source while reviewing the proof. Check that it names the right company and person, and that the fact was still current on the review date. Read every number, name, location, and date against the source. The line cannot say more than the evidence does.

Then check the choice of format. A detail suitable for a private letter may be wrong for an exposed postcard. Verify the recipient's role and address separately, and run the suppression, frequency, budget, and design checks before launch.

If the source changes, stop every unsent piece that depends on it. Do not correct only the next batch.

Sincerely keeps researched facts and drafts in a review flow, then requires a passing address, approved design, budget headroom, and explicit launch before anything prints. Good copy is one part of the release boundary, not a substitute for it.

## Sources and methodology

The examples, format guidance, and review checklist are Sincerely's proposed writing method. They make no response-rate claim. The companies, events, names, and numbers in the examples are fictional.

The distinction between a sourced fact and an inference follows the evidence practice in Sincerely's [provenance guide](https://trysincerely.com/glossary/provenance). Privacy and marketing rules differ by market and data source. Review the facts, format, and outreach policy that apply to your program.

`Dear Maya` is more formal than `Maya`; either can fit. A company name, statistic, or handwriting treatment earns its place only when it carries meaning. None can rescue a generic opening. Give a letter enough room to establish the reason in two or three short sentences. A postcard may have only one line on the front, so that line has to do real work.

## Related questions

- [How to write direct mail that gets read](https://trysincerely.com/guides/direct-mail-copywriting): Give the piece one job, lead with the reader's problem, personalize from real account facts, and ask for exactly one thing. A short guide with a before-and-after example.
- [How to write a direct mail call to action](https://trysincerely.com/guides/direct-mail-call-to-action): Give a letter, postcard, or gift note one next step that matches the format and relationship. Includes examples for replies, QR codes, calls, and meetings.
- [Postcard or letter, which should you send?](https://trysincerely.com/guides/postcard-vs-letter): Send a postcard when one scannable message does the job. Send a letter when you need room, formality, or privacy. Decision rules with current format costs.
- [How to personalize outbound at scale without hallucinating](https://trysincerely.com/guides/how-to-personalize-outbound-without-hallucinating): Build outbound from dated source records, bind every claim to evidence, review by risk, and catch errors before one bad fact reaches 500 accounts.

---

Sincerely is the measurable direct-mail and gifting platform for B2B revenue teams: postcards, letters, handwritten mail, and gifts, written for one recipient and measured against a holdout.

Contact Sincerely: https://trysincerely.com/contact

Agent routing index: https://trysincerely.com/llms.txt
