Elementor Atomic Forms can collect a submission in WordPress while the email action is missing, misaddressed, rejected by mail configuration, or filtered into spam. The stored entry and email delivery path need separate proof.
Use this when Atomic Forms shows leads under submissions but the site owner or customer never receives the expected message.
Quick answer
Elementor Atomic Forms Collects Submissions but Sends No Email should be handled with a narrow evidence-first workflow: capture submission proof, check both actions, validate mail fields, then verify the result before making broader changes.
What to check first
- Record form name, page URL, submission ID, test time, actions after submit, and recipient.
- Confirm both Collect submissions and Email actions are selected when both outcomes are required.
- Check From email, Reply-To, subject, message fields, and any field-token references.
- Match the submission time to WordPress mail logs and the SMTP provider message ID.
- Correct the action or mail setting, submit once, and verify storage and delivery.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Capture submission proof | Record form name, page URL, submission ID, test time, actions after submit, and recipient. | One test creates one stored submission. |
| Check both actions | Confirm both Collect submissions and Email actions are selected when both outcomes are required. | The Email action generates one message for the intended recipient. |
| Validate mail fields | Check From email, Reply-To, subject, message fields, and any field-token references. | The SMTP provider accepts the message and the mailbox receives it. |
| Trace SMTP ID | Match the submission time to WordPress mail logs and the SMTP provider message ID. | Success and failure states remain accurate for visitors. |
Why this usually happens
- Collect submissions and Email are separate actions.
- A From address outside the authenticated domain can fail delivery.
- A field token can point to a renamed or missing input.
- The success state can appear before mailbox delivery is known.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
wp plugin list --fields=name,version,status | grep -Ei 'elementor|mailer|smtp'
wp option get elementor_pro_version
# Match the form submission timestamp to mail logs without exporting lead content.
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Capture submission proof
- Check both actions
- Validate mail fields
- Trace SMTP ID
- Retest once
What to tell the client or owner
Report the form name, submission ID, actions, recipient, From domain, SMTP message ID, and delivery result.
Production verification checklist
- One test creates one stored submission.
- The Email action generates one message for the intended recipient.
- The SMTP provider accepts the message and the mailbox receives it.
- Success and failure states remain accurate for visitors.
Mistakes to avoid
- Do not judge the fix by one browser or the homepage only.
- Do not delete evidence before recording usernames, file paths, timestamps, and response headers.
- Do not add a cache, security, or tracking plugin while the original problem is still unclear.
- Do not leave test users, temporary debug logs, or broad API keys active after verification.
When HandL WP should help
Bring in help when this affects leads, checkout, search visibility, malware risk, paid media reporting, or a client production site. HandL WP can trace the issue through WordPress, hosting, cache, tracking, and Search Console, then verify the workflow after the technical fix.
If this is active on a production site, repair Elementor form email delivery.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references
Set retention for stored form data
When Collect submissions is enabled, use the Atomic Forms submission retention audit to inventory fields, database rows, email copies, CRM destinations, backups, access roles, exports, and deletion tests.