Stale form settings
A domain, mailbox or staff address may have changed while the old recipient remained in WordPress.
Contact Form 7 says “sent,” but no email arrived?
Do not keep pressing Send. One controlled test can show whether the problem is on the page, inside Contact Form 7, in WordPress mail or after the message leaves the site.
The free check reads the public page. It does not submit the form or prove inbox delivery.The success message means the browser received a successful form response. It does not by itself prove that the notification reached the recipient. Check the configured recipient and sender, then test the WordPress or SMTP mail path with one uniquely labelled message.
CHECK IN ORDER
Follow the message path, one stage at a time.
- 01
Stop repeated submissions
Choose one test message and give it a unique subject or run ID so you can follow it without creating duplicates.
- 02
Read the form response
A validation error, spinner, network error, success message and redirect point to different parts of the problem.
- 03
Review the Contact Form 7 Mail tab
Check the To, From, Subject and additional headers carefully. Use a sender address that belongs to the website domain.
- 04
Trace WordPress to the inbox
Check the SMTP or mail provider log when available, then inspect the intended inbox and its filtering rules.
COMMON CAUSES
What can break without taking the website offline.
JavaScript conflict
The button may appear to work while a front-end error prevents a complete submission response.
Mail transport problem
WordPress can accept the form data even when the next mail step is misconfigured or unavailable.
Recipient-side filtering
The website path may work while one mailbox moves, quarantines or rejects the message after delivery.
WHAT MONITORING PROVES
Four green stages—not a vague “healthy” badge.
- Public page loaded
- Supported form found
- One synthetic submission accepted
- Test message reached the monitoring inbox
This does not prove delivery to the business owner’s real inbox or spam placement. Read the full claim boundary.
SELF-SERVE LAUNCH
Stop remembering to test it manually.
Join without a call. The first guided test will run after the WordPress companion is connected.