Email subject and preheader: promise what the message contains

8 min read

A good email subject line announces useful information that is faithful to the content. The preheader, that is to say the overview text offered next to the subject in certain messaging services, completes it instead of repeating it. Write both based on the expected action and what the recipient will actually find after opening. Then check their display in the relevant email clients. The objective is not to provoke openness at all costs, but to give an understandable reason to read a message whose promise is kept.

Things to remember before looking for a catchy formula

Google requires that the subject, headers, and visible name accurately represent the sender and content.^[19] A misleading object can therefore contradict good sending practices, even if it seems attractive. Start by writing the proposition of the message in everyday language; style effects come after this check.

Build the email subject and preheader duo

First write an internal sentence: “this message helps this person accomplish this action.” If you can't complete the sentence, the subject line may obscure scattered content. Then choose the information that deserves to be visible in the inbox: a confirmed appointment, targeted advice or an offer with its essential conditions.

The object carries the main promise. The preheader provides clarification: audience concerned, document included, next step or useful condition. It must not become a second, unrelated object. Reread the duo as a short sentence, then separately: some interfaces do not display the preheader or only show part of it.

The 4SYSTEM email journey guide allows us to place this work in the complete campaign. The subject line does not correct a message without a purpose, a questionable selection of recipients, or a destination that does not live up to the promise.

Choose information that should survive truncation

There is not an identical visible length for all boxes, devices and settings. Rather than aiming for a universal number of characters, place words early that help understand the topic. A recipient who only sees the beginning should be able to distinguish between an invoice, advice and a promotion.

Avoid preambles that consume this space: internal campaign name, irrelevant edition number or repetition of the sender. If the brand is already clearly in the sending field, consider whether it should be repeated in the subject line. Keep it when it brings a real distinction, not out of habit.

Dates, conditions and restrictions must remain true. If an offer depends on a specific range, do not write a subject that suggests that it concerns the entire store. The preheader can provide the main condition, but it must also be found in the body. Truncation is not an excuse for omitting a decisive reservation.

Write concrete promises without artificial urgency

Prefer wording that your team can verify. “The guide to choosing your filter” announces a resource. “Your order is ready for pickup” announces a state that actually needs to be reached. “Last chance” requires a real deadline and a consistent commercial rule.

The false prefixes “Re” or “TR” must not lead to the appearance of an existing conversation; Google lists them among the deceptive practices to avoid when they do not correspond to the message.^[19] Likewise, a sender named as a known person must not conceal a commercial campaign.

Personalization is only useful if its data is reliable. Prepare a version without a first name and test the missing fields. Sensitive information or a business relationship detailed in the subject may be visible on a locked screen. Choose what is actually worth displaying before opening and leave the appropriate details in the content.

Make the preheader a precision, not a waste of the model

Your tool may offer a preview text field, but check the message received. Without appropriate settings, the email client may repeat a sentence from the beginning, a technical text or an online consultation instruction. A correct preheader in the editor is therefore not enough.

Write a short clarification that adds information missing from the object. For an advice newsletter, it can announce the problem being addressed. For a requested reminder, she can specify what to prepare. Avoid “click here to learn more,” which says nothing about the content.

Do not place important conditions only in an invisible display tip. The proposal must remain understandable in the actual message, including without images. The W3C recommends text alternatives adapted to the information or function of the images.^[22] This reference helps design the content; it does not guarantee rendering to all email clients.

Writing workshop with fictional examples

The following formulations are illustrative. They do not describe a client campaign or a measured result. They show how a vague promise can become controllable.

For each duo, ask someone outside the editorial team to say what they expect to receive. Compare their response to the content. If the interpretation is broader than the actual offering, correct the text rather than relying on the reader to then find the restriction.

Test the display and the route after opening

Send the final version to test boxes tailored to your audience. Review the sender name, subject, preview, and start of the message on phone and computer. Also test a version with an empty personalization field and a version whose images do not load.

Open the main action from the received message. The title of the landing page should confirm the promise. If the subject advertises a free document, the reader should not discover an unannounced obligation to purchase. If authentication is required, explain it before losing the context of the message.

Log problematic displays and their conditions. A single capture does not represent all boxes. Prioritize ambiguous meanings, missing elements and inconsistent destinations. A minor visual difference does not carry the same weight as an invisible restriction.

Evaluate text without overinterpreting openings

Apple explains that Mail Privacy Protection prevents the sender from seeing whether the message has been opened and that this protection does not extend to links or attachments.^[41] The opening rate therefore does not constitute a direct and exhaustive reading of the recipients' attention.

If you compare variants, write in advance the question and the observed result: consultation of the resource, expected response or useful action. Keep content and scope consistent. Examine errors and unsubscribes as well as available clicks. A click may itself require qualification depending on your measurement system.

Don’t choose a plan just because it attracts more displayed opens. A sensational promise can lead to disappointment. Without sufficient and comparable data, prefer editorial validation and comprehension tests rather than a classification of formulations presented as statistical proof.

Frequently asked questions

Can we use a question in the subject?

Yes, if it corresponds to an actual question addressed in the message. Avoid a question that creates unanswered concern or suggests a fictitious personal incident. The preheader can specify the help offered. Then test what the reader understands, not just the supposed effect of the punctuation.

Do I need to personalize all objects?

No. Personalization must provide a useful benchmark and be based on reliable data. Always prepare replacement text when the field is missing. Also check what the object reveals on a split or locked screen. An accurate first name does not compensate for a vague promise or a poorly targeted message.

Does a preheader necessarily improve the results?

It may clarify the message when displayed, but no gain is guaranteed. Its usefulness depends on the content, the recipients and the rendering. First assess the duo’s understanding and destination loyalty. A displayed increase in opening is not enough to demonstrate a lasting commercial improvement.

Next step: validate a complete promise

Take a message to send and write its object-preheader duo, then the first sentence of its destination. These elements must tell the same thing. To frame your models and their connection to the site, consult the 4SYSTEM services without expecting an automatic performance gain from a formula.

Sources

• Consignes pour les expéditeurs de messages - Aide Gmail (accessed 2026-10-08)
• Images Tutorial | Web Accessibility Initiative (WAI) | W3C (accessed 2026-10-08)
• Use Mail Privacy Protection on iPhone - Apple Support (accessed 2026-10-08)