Reply-To defined.
Reply-To is the email header that sets where replies go when that differs from the sender, so on a form notification hitting reply writes straight to the person who filled in the form.
How Reply-To works
Every email carries a From header naming its sender, and mail clients reply to that address by default. Reply-To overrides the default: when it's present, hitting reply addresses the new message there instead. The From address still identifies who actually sent the mail; Reply-To just names who the conversation belongs with.
Form notifications are the textbook case. The notification has to be sent from an address the service is authorized to send as. Sending "from" your visitor's address would fail SPF and DMARC checks, since the service doesn't own that domain, and land the message in spam. So the reliable pattern splits the two headers: From is the authenticated sending address, Reply-To is the visitor. You read the submission in your inbox, hit reply, and you're writing to the person who filled in the form, deliverability intact. FormWire sets this up on every notification, with Reply-To defaulting to the submitter's email field.
From and Reply-To, split cleanly.
From, authenticated
The sending address the service actually controls, so SPF and DMARC pass and the notification reaches your inbox instead of spam.
Reply-To, the human
Set to your visitor's address, so answering a lead is one click, the reply goes to them, not back at the service.
Delivery, verified
Notifications go only to recipients you've verified, so the form can never be pointed at an inbox that isn't yours.
Related questions
Because that's spoofing, and modern mail servers are built to catch it. SPF and DMARC verify that the sending server is authorized for the From domain, a form service sending as gmail.com fails both, and the notification lands in spam or vanishes. Reply-To delivers the same one-click reply without forging a sender.
What drives email deliverability →The submitter's email field, by default. Collect an email in the form and every notification arrives reply-ready. The Reply-To behavior is set in your form's settings.
Then there's nothing to default the reply target to, and replying to the notification won't reach the visitor. If you want to answer submissions by email, an email field in the form is the prerequisite.
Send an autoresponder back to submitters →No, your reply is a normal email from your own address. The service only shaped the notification's headers; the conversation that follows is directly between you and the submitter.
Want to see it working?
Read the docsAnswer every lead with one click.
Free tier forever. No credit card required.