Articles / Bad News Email Subject Line: Name What Changed and When

email marketing

Bad News Email Subject Line: Name What Changed and When

Finn ·

A bad news email subject line should identify the affected service, order or request. For an operational change, include the change and date: "Your Pro plan rises to $29/month at your 12 November renewal". For a sensitive personal decision, a neutral subject naming the request can be more appropriate. Put the explanation and next steps in the body.

Three parts, and the six lines they produce

Start with the affected plan, delivery or booking, then add the change and relevant date. If action is required, name it in the subject when space permits. Preview text can add detail, but repeat essential instructions in the body: inbox previews may be hidden or shortened.

These invented examples cover six situations a solo operator might face:

  • A price increase: Your Pro plan rises to $29/month at your 12 November renewal
  • A delivery slipping: Your landing page delivery is delayed until 14 November
  • A feature going away: The Zapier integration stops working on 3 December
  • A job that failed: Your 9 November reports were delayed and have now been sent
  • A cancellation: The 12 November workshop is cancelled, refunds started
  • Work you are turning down: Regarding your Q4 retainer request

Use completed-action wording only after confirming the action: "refunds started" means you have initiated the refunds. The retainer example deliberately leaves the decision for the body. Unlike the prospecting context in Cold Email Subjects Are a Filter, Not a Hook, these messages concern an existing service or request. The subject should reveal the change; the body should explain the reader's options.

Six subject lines that make the news worse

The empty update. "An important update" leaves the topic unclear. Write for Business recommends neutral subjects in some examples, but those subjects still identify the matter being discussed. Keep that specificity: "Update on your November delivery" is useful even when the final date is unknown.

The good news costume. "Exciting changes to your plan" frames the change as welcome before the reader knows its cost. State the increase directly; explain any added features separately in the body.

The document title. "Changes to our terms of service" can describe anything from a minor edit to the loss of a feature. When a specific change affects the reader, name it: "Free API access ends on 15 December".

The apology. "We are sorry" does not identify the problem. Use "Your delivery is delayed until 14 November", then acknowledge the inconvenience and explain the options in the body.

The undated alarm. "URGENT: action required" omits the task and deadline. If payment failed and access will pause, try "Update your payment method before access pauses on 3 October". Use urgency only when the timing warrants it.

The buried noun. "Following our review of the roadmap and your feedback..." delays the news. Put the affected service first so a shortened subject retains some meaning; explain the review in the body.

The subject should reveal the change; the body should explain the reader's options.

One complete email, values included

This fictional example assumes monthly billing in US dollars, renewal on the 12th, and a price change that applies at the next renewal after 1 November. Before adapting it, confirm your billing rules, notice requirements and actual cancellation process.

Subject: Your Pro plan rises to $29/month at your 12 November renewal
Preview text: You can keep your plan or cancel before that renewal.

Hi Marta,

Your Pro plan will rise from US$19 to US$29 a month at your 12 November
renewal. Your current paid month is unchanged.

Transcription costs have increased, so we are raising the subscription
price to continue providing this feature.

To keep your plan at the new price, you do not need to do anything.
To cancel, sign in and choose Settings > Billing > Cancel subscription
before your 12 November renewal. You will retain access until that renewal
and will not be charged US$29. Check for the cancellation confirmation.

Reply to this email if you need help with either option.

Sam

Replace the fictional reason and menu path as well as the names, prices and dates. Then send yourself a test. With the body closed, can you identify the affected plan, new price and renewal date? With it open, can you find both choices and the cancellation instructions? Also check with preview text hidden. The subject cannot carry every condition needed to make a decision.

Check the recipient segment before sending, one of the mistakes solo stores make with marketing automation. Set aside time to answer questions, too. The advice that a scheduled LinkedIn post needs you there when it goes live has a useful application here: plan for the conversation your announcement may start.

Where a neutral subject is the right call

Write for Business illustrates a rejection with "Bid 4459 Everson City Park". That subject identifies the decision without displaying its outcome. Similarly, "Regarding your Q4 retainer request" can introduce a courteous refusal to a specific person.

Use a neutral subject when the outcome is personal or sensitive and no urgent action would be obscured. State the decision clearly in the body. For a difficult conversation with someone you work closely with, consider speaking first and sending written confirmation afterwards.

When the subject line becomes a legal question

Under US CAN-SPAM rules, commercial messages must use subjects that accurately reflect their content. The FTC's CAN-SPAM compliance guide distinguishes these from transactional notices. Adding an upsell can affect the classification, depending on the subject and body. Keep an operational notice focused on the change; an exemption from some CAN-SPAM requirements does not establish compliance with every applicable law.

Where a breach requires notifying affected people under Article 34 GDPR, that communication must explain the breach clearly. The provision does not prescribe a subject line or automatically rule out a neutral opening. A good subject alone does not satisfy the notification requirements.

FAQ

Should the subject line say "bad news"? Usually, a specific subject is more helpful. "Bad news" does not identify the affected order or service. Use the space for that information, or name the request if a neutral subject suits the situation.

Will I lose customers by putting the price rise in the subject? This article does not establish how subject wording affects cancellations. A customer may leave because of the price itself. The reason to state the increase clearly is to let them make an informed choice before renewal, not to promise a particular retention result.

Did this article help?

Get the best articles, carefully selected to save you time.

Read next

Cold email agencies sell three different products under one name: a lead generation retainer where they own the list and the sending, an infrastructure package that rents you domains and warmed mailboxes, and a done with you sprint that sets up your stack and leaves. The pay structure tells you which one you are buying, and the guaranteed meeting count is the one to refuse.

A cold email format is a fixed order of short parts, each with one job: a snippet that earns the open, an opener that proves the email was written for one person, a bridge to your offer, a single ask, an easy out, and a signature with almost nothing in it. The body runs 50 to 125 words. The vocabulary below names each part, so you can write one without a template and diagnose one that gets no reply.

Featured

A pivot is often just the polite word we use with investors when the first company is dead and we have decided to build another one. And that is fine. Not because failure is noble, but because luck needs exposure: every market you enter, every product you ship and every channel you test is one more surface where something unexpected can land.

Build articles

OpenClaw and Hermes Agent are both MIT-licensed AI agents you host yourself, and their own documentation disagrees about where the safety boundary sits. OpenClaw puts it at the gateway: authenticate to it and you are trusted with everything it reaches. Hermes puts it around the command, inside a container. Pick by which of those you can live with.

Reddit is not split into believers and skeptics about vibe coding. Across the eight discussion threads Google ranked for this query in September 2026, the reports that failed and the reports that worked describe the same defect: generated code that runs, looks finished, and does not do what it claims. The check that catches it is to remove what the feature depends on and confirm it breaks.

Projects

Brands

The essentials, by email.

What works, what does not, what I would do differently. Sent when I have something useful to say.