20 Subject Lines for a Support Follow-Up Email

Where you need something from the customer, the subject must say so, since this is what determines whether it is opened today.

5–8. Action needed subjects

Quick question to finish your [issue] · Need one thing from you on [reference] · [Issue]: waiting on your reply · One detail and I can close [issue].

All four make the requirement explicit, which is the single highest-impact element in a support subject line.

Being specific about what is needed

Naming the actual thing, such as your order number or a photo of the damage, performs better than a general request for information.

It also allows the customer to reply without opening, which occasionally happens and is a good outcome.

The second chase

Still need [thing] to sort [issue] is honest and specific, and avoids the passive aggression of a gentle reminder.

Chasing more than twice is rarely productive and should be replaced by closing with an easy reopening route.

Update emails should state what changed, since an update with no substance trains customers to ignore the next one.

9–12. Update subjects

Update on [issue]: [what changed] · [Issue] is with our [team] now · Progress on [reference], next update [date] · Still working on [issue] — here's where we are.

Each conveys something in the subject itself rather than requiring the email to be opened to learn whether anything happened.

Updates with no progress

An honest subject saying no news yet on [issue], next update [date] is better received than silence and better than a subject implying progress.

Customers accept slow progress considerably more readily than uncertainty about whether anyone is looking.

Escalation notices

[Issue] escalated to [team] — [name] will contact you tells the customer both that it moved and who now owns it.

Naming a person materially increases confidence that the matter has not been passed into a void.

Closure emails should make reopening obviously possible, since a closed ticket the customer disagrees with produces a complaint otherwise.

13–16. Closure subjects

Closing [issue] — reply here if it's not sorted · [Reference] closed, reopen any time · Wrapping up [issue] unless you need more · [Issue] closed: here's what we did.

The reopening route in the subject prevents the customer feeling the matter was ended unilaterally.

Closing for inactivity

Closing [issue] for now — just reply to pick it up avoids implying the customer did something wrong by not responding.

Framing matters here, since customers frequently went quiet because they were busy rather than satisfied.

Closing something unresolved

Where the matter is closed without a resolution, the subject should say so rather than implying completion.

A misleading closure subject is one of the more reliable ways to generate a complaint.

Survey emails have low open rates and honest specific subjects perform noticeably better than generic requests.

17–20. Feedback subjects

How did we do with [issue]? · One question about your [issue] · Was [issue] actually sorted? · 30 seconds on your recent [issue]?

Referencing the specific issue rather than asking about the support experience generally roughly doubles response.

Being honest about length

Stating one question, and then asking one question, builds the credibility that makes the next request answered too.

Claiming brevity and then presenting a page-long survey does lasting damage to response rates.

When not to send one

Feedback requests after unresolved issues, complaints or sensitive matters produce both poor data and genuine offence.

Suppressing them in these situations is a small configuration decision with a disproportionate effect.

Several patterns reliably reduce open rates and all of them are common in automated support email.

Generic and templated subjects

Ticket update, your support request and case notification could describe any ticket from any company and prompt nothing.

Every subject should contain at least one detail specific to this customer's situation.

Promotional phrasing

Exclamation marks, capitalisation and urgency language make a support email look like marketing and increase the chance of filtering.

Plain phrasing performs better and reaches the inbox more reliably.

Excessive length

Subject lines are truncated on mobile, which is where most are read, so the meaningful content must appear early.

References and identifiers belong at the end for this reason.

Breaking the thread

Changing the subject line mid-conversation splits the thread in the customer's client and frequently creates a duplicate ticket.

Keeping the subject stable across a conversation matters more than optimising each individual message.

No-reply senders

A support email the customer cannot reply to forces them to start again elsewhere, which defeats the purpose of the follow-up.

Replies should land back in the same conversation, which is a configuration decision rather than a technical constraint.

Chatboq threads email follow-ups into the original conversation and inserts the specific issue and reference automatically.

Threading across channels

A follow-up email attaches to the conversation it continues, so a customer replying does not create a separate record for someone else to pick up.

This is what prevents the duplicate handling that produces contradictory answers.

Specifics inserted automatically

The issue description and reference come from the conversation rather than being typed, which is what makes specific subjects practical at volume.

Templates hold the structure and the details fill in, so every subject is specific without additional agent effort.

Measuring what works

Open and response rates by subject type show which patterns work for your customers, which is more reliable than any general advice.

Response rate matters more than opens, since the point of most of these emails is to prompt a reply.

Sending from a person

Emails from a named agent are opened and replied to at noticeably higher rates than those from a generic support address.

Where automation sends the message, naming the person who will handle the reply achieves most of the same effect.