Quick answer
A form label, submission field, notification template, and CRM mapping can be separate settings. When adding or renaming a field, verify the whole path so the new value is actually delivered and stored where expected.
Before you start
Identify the form plugin or page-builder module, form ID, embedding page, recipients, storage location, and connected automations. Export or record the existing form configuration and use staging for a structural change.
Steps
- Open the exact form rather than creating another similarly named copy. Add the approved field with a visible label, appropriate input type, and a clear required/optional setting.
- Update notification merge tags, confirmation copy, and any CRM/webhook mapping to use the real field identifier. Keep the From address on an authorized sending domain; use visitor email as Reply-To where supported.
- Review privacy copy and data minimization. Do not collect sensitive information that the business does not need or is not prepared to protect.
- Submit a clearly labeled test using non-sensitive data. Check required-field errors, phone layout, keyboard use, stored entry, authorized recipient delivery, and downstream mapping.
Verify the result
The same expected value should appear in the visitor confirmation, stored submission, notification, and integration where applicable. Record the form ID and tested page URL.
Troubleshooting and recovery
A success message does not prove that mail or a webhook arrived. Inspect the plugin's sanitized delivery evidence and preserve the original mapping so the change can be reverted selectively.
Related help
- Make website form notifications use an authorized mail path
- Review form labels, instructions, and error messages
- Plan what happens after a website inquiry form is submitted
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
