Configure the Reply-To field
Configure the Reply-To email field in Qubeforms so replies reach the form submitter. Match HTML field names and test notification emails and autoresponders.
1. Choose the visitor email field
Open Settings → Delivery & spam → Reply-To field. Enter the field name containing the visitor’s email address, not an email address, label, or HTML ID. The default is email. The field must contain one valid email string at the top level of the submitted data; arrays and nested paths are not supported for this setting.
2. Match the name in your form
For this fragment, set Reply-To field to contact_email and save delivery settings. The setting and submitted name are case-sensitive. Keep the name simple: it must start with a letter or underscore and may contain letters, numbers, underscores, dots, or hyphens, up to 191 characters. Underscores work consistently across HTML and JSON.
<label for="reply-email">Your email (required)</label>
<input
id="reply-email"
name="contact_email"
type="email"
autocomplete="email"
required
>3. Distinguish replies from recipients
Verified recipients receive notification emails. Reply-To directs a human reply to the submitted visitor address; it does not change the sending domain or automatically add the visitor as a recipient. If the chosen field is missing or invalid, Qubeforms omits the visitor Reply-To header. Inspect the actual reply destination before sending if a submission lacks a usable email.
4. Review dependent features when renaming
Enabled autoresponders also use this field to choose the submitter destination and require a valid address, an eligible plan, and available sending capacity. Advanced spam email-domain rules use the configured visitor email too. When renaming the field, update your website, Reply-To setting, relevant template tokens, and routing conditions together. Old submissions retain their original field names.
5. Test the resulting email
Send a new test using a mailbox you control. Confirm the stored field, open the notification, and start a reply to check the destination. If autoresponders are enabled, verify that message separately. If replies point to the wrong place, compare the saved setting with the actual payload, including letter case and nesting.
Public form keys can appear in browser code. Read keys, management credentials, and webhook signing secrets must stay on the server.