Subject lines an agent should write, and the ones it should leave alone

The subject line is a small field with a disproportionate job: it decides whether the message is opened, how it threads, and how findable the conversation is in six months. Agents get it wrong in two directions, by rewriting subjects they should have kept and by writing lazy ones when they finally do need to compose.

3 August 2026 · 4 min read

Rule one: on a reply, keep it#

The single most common agent mistake with subjects is improving them. A customer writes "help", and the agent replies with "Regarding your recent inquiry about order 4012". Better English, worse outcome.

Three reasons. Clients that group by subject can split the thread, so the customer sees two conversations. The customer searches their inbox for the words they wrote, not yours. And the agent's own later context depends on the thread staying intact, per how email threading works.

The only edit worth making is the standard Re: prefix, which mail clients handle for you when you reply properly rather than composing.

Rule two: when the topic genuinely changes, start a new thread#

The opposite failure is carrying one subject across an unrelated conversation because it was convenient. If the customer's invoice question turns into a support problem, that is a new conversation with a new subject and a line explaining why: "Starting a separate thread for the login issue so it does not get lost under the invoice one."

Say it out loud like that. A thread that splits without explanation reads as disorganisation.

What a good composed subject looks like#

When the agent does write one, the test is whether it is useful in a search results list nine months later. That produces four properties.

Front-loading matters more than length. Mobile clients show roughly the first thirty to forty characters, so the identifying detail belongs at the start rather than after a courteous preamble.

What to leave out#

• Marketing shape. Exclamation marks, emoji, all-caps, and promises. All of it reads as bulk to filters and to people, per do spam filters catch AI-written email.
• Fake urgency. URGENT and ACTION REQUIRED on something that is neither burns trust the first time and gets filtered the third.
• Internal codes nobody knows. A ticket reference is useful to you and meaningless to the recipient. If you need one, put it at the end, not the front.
• Tracking tokens. Threading is what the headers are for, and a token in the subject is both ugly and fragile.
• The recipient's name. John, about your order reads as a mail merge, because it usually is one.

The reference number question#

Order, invoice, and booking numbers are the exception to the no-codes rule, because they are the thing the recipient will search for. Put the number in the subject and never translate or reformat it, since it has to match what is in your systems and what the customer has on their paperwork. That rule applies across languages too, per answering email in the language it arrived in.

Invoice 2291, due 8 July beats both Invoice reminder and Reminder regarding your outstanding invoice number 2291 dated 8 July.

Where this belongs in the prompt#

Two lines, and they are worth the space:

- Replying: never change the subject. The recipient will search for their words.
- Composing: put the identifying detail first, under 50 characters, no marketing shape,
  no emoji, no fake urgency. Include the order or invoice number exactly as it appears
  in our systems. If the topic has changed, start a new thread and say so.

That is the whole policy. The rest of the writing guidance, including tone and length in the body, is in the system prompt for an email agent.

Questions#

Should an AI agent change the subject line when replying?

No. Keep the recipient's subject. Rewriting it can split the thread in clients that group by subject, and it breaks the words the recipient will search for.

How long should a subject line be?

Under about fifty characters, with the identifying detail first, since mobile clients truncate after roughly thirty to forty.

Should the subject include an order or invoice number?

Yes, exactly as it appears in your systems. It is the thing the recipient will search for, and it must match their paperwork.

What about emoji and urgency markers?

Leave them out. They read as bulk to filters and as marketing to people, and fake urgency stops working immediately after the first time.

When should the agent start a new thread?

When the topic genuinely changes. Write a new subject and say in the first line why you moved the conversation, rather than letting one thread carry two subjects.

Should the recipient's name go in the subject?

No. It reads as a mail merge, because in most inboxes it has been one.