If replying to a WPForms notification opens your own address, inspect its Reply-To header. Keep From as a sender your mail service authorizes. Putting the visitor's email in From may appear to solve routing while creating a delivery problem.
Decide who should receive each reply
A staff notification and a visitor confirmation have opposite reply destinations. Write that down before editing the form.
| Message |
Intended From |
Intended Reply-To |
| Inquiry sent to sales |
Authorized business sender |
Visitor's validated Email field |
| Confirmation sent to visitor |
Authorized business sender |
Monitored support address |
| Internal escalation |
Authorized business sender |
Responsible internal team |
These are example routes, not a requirement to create extra messages. Avoid exposing internal recipients to the visitor through unnecessary CC fields.
Check the selected notification
Open the form's notification settings and locate the branch that produced the actual message. Conditional rules may choose a different notification for a quote request than for a support request.
WPForms' notification setup guide documents Reply-To and its default to From when empty. For a staff copy, choose the Smart Tag for the intended Email field. Do not copy a field number from another form: duplicated or rebuilt forms may have different fields.
If the form contains both billing email and contact email, decide which person should receive a reply. A valid address is not necessarily the right recipient. For an optional email field, define what staff should do when the value is absent rather than silently routing a response elsewhere.
Staff copy: Replies to test visitor. Visitor copy: Replies to support. Headers: Match selected branch. Blank email: Defined fallback. Explanatory checklist, not a customer test result.
Inspect what was delivered
Submit a synthetic inquiry with an address you control. Open the original message details and compare the delivered From, Reply-To and To headers with the intended route. An SMTP plugin, helpdesk gateway or forwarding rule can alter the final message after WPForms creates it.
Use the mailbox's Reply action and inspect the composed recipient without sending. Then send one controlled response to your own test address and confirm arrival. Do not test with a real lead's address or assume the label shown by the mail client reveals the underlying address.
If the original message has the correct Reply-To but the reply composer does not, investigate the receiving client or helpdesk routing. Changing the form again would hide the point where the behavior changed.
Cover the other branches
Repeat with every relevant conditional notification, then a blank optional email where permitted. Confirm that visitor confirmations reply to the business and that staff copies reply to the test visitor.
Keep routing and deliverability separate. If messages land in junk, continue with WPForms notification spam diagnosis. HandL WP can repair form email routing using a redacted header sample and the notification name, without needing a customer mailbox export.
References reviewed October 13, 2026. Examples are explanatory, not customer test results.