# Email subject

Set the subject line for Form Plume notification emails so your team can scan the inbox and instantly see which form needs attention.

The subject is the first thing your team sees. Make it tell them which form needs attention.

Open **Notifications** and enter the subject you want to use.

```text
New sales inquiry from Form Plume
```

## What to include

A good subject line has two parts: a stable prefix that stays the same on every notification, and something that names the form. The prefix is what your inbox rules match on, so keeping it constant lets you file every submission into the right folder or label without maintaining a separate rule per form. The form name is what your team scans for, so a subject like `New lead: Contact form` tells them what happened and where before they open the message.

Keep the subject to a fixed string. Submitted field values belong in the body, not the header, so if you want the visitor's name or message to appear in the notification, put them in an [email template](/docs/notifications/templates) rather than the subject. That keeps the subject clean for triage and avoids leaking untrusted input into email headers.

## Keep it predictable

A stable subject makes inbox rules, search, and team triage easier.

Avoid placing untrusted visitor input directly into email headers. When you need conditional delivery, use [Email routing](/docs/notifications/routing). When you need submitted values inside the message, use email templates.