A working form needs more than visible fields. Decide where submissions go, whether they are stored, how visitors know they succeeded, and how you recover a message that email delivery misses.
Decide what you need to collect
For a basic enquiry, a name, reply address and message can be enough. File uploads, payments, conditional fields and multi-step applications create different requirements. Collect only the information necessary for the task.
WordPress core does not provide a general contact-form builder for arbitrary enquiry workflows. Your theme, host or another plugin may already supply one. Check that before adding a second form system.
Two documented approaches
| Option | Documented approach | Main decision |
|---|---|---|
| Contact Form 7 | Form and mail configuration with its own form-tag system | Are you comfortable managing the form configuration and delivery? |
| WPForms Lite | Visual drag-and-drop builder for basic forms | Does Lite contain the fields, storage and integrations your workflow needs? |
Contact Form 7 is published by Rock Lobster Inc. Its default privacy statement says it does not itself write user personal data to the database, send it to external servers or use cookies. Enabled integrations can change that behavior. Do not assume default email delivery includes a saved submissions archive.
WPForms Lite documents a visual builder and standard fields. Its listing describes Pro features including file uploads, conditional logic and multi-page forms. Check the current feature boundary before designing a workflow around those controls; the product page discusses both editions.
Neither option is a universal winner. A simple enquiry and a regulated application with attachments need different decisions.
Check delivery and storage separately
Configure the notification's recipient and sender using the plugin's documented mail settings. A visible success message is not proof that a message reached the recipient's inbox. Host mail handling, authentication and recipient filtering all matter.
Decide whether submissions need storage in WordPress, a separate system or email only. Check retention and access. For a workflow you cannot afford to lose, document how you discover delivery failures and recover submissions.
Verify a real test submission
- Create the smallest form that meets the requirement.
- Label every field and write error messages a visitor can act on.
- Submit invalid input, then a valid test message, on desktop and mobile.
- Confirm actual receipt and any configured storage. Check the reply address.
- Test keyboard operation and the visible success state.
- Repeat after adding spam protection or integrations.
Do not ask visitors for sensitive documents merely to test the form. Use dummy data on staging and keep production notification recipients intentional.
Consider privacy and migration
Spam controls and marketing integrations can send data to other providers. Explain enabled processing in your own privacy information. A CAPTCHA's presence alone does not settle compliance or accessibility.
If you later switch plugins, form definitions and stored entries may not transfer automatically. Keep an export where supported and plan how old embeds will be replaced.
Official listings were checked on October 7, 2026. This guide reports documented features; it does not claim hands-on delivery or accessibility tests of these plugins.
Sources & verification
Sources checked September 27, 2026. Documented behavior is distinct from hands-on testing.