A missing inquiry does not always mean the form itself is broken.

Use a test you are authorized to make, with clearly marked fictional details and no sensitive information. Avoid repeated submissions that could trigger automations, bookings or charges. Note the page address, date, time, browser and the steps taken. If the form could trigger a consequential action, arrange an appropriate test environment first.

Does the button respond? Are required-field messages understandable? Can the form be completed with a keyboard? Does it remain usable on the relevant device? Record the exact error or confirmation. If nothing happens, a browser-side validation or script problem is one possible cause, but the appearance alone does not prove it.

Some form systems keep submissions in a dashboard; others do not. Check the actual configuration. A saved record can show that information reached that part of the system even if a notification is missing. If there is no record, do not assume the visitor never submitted: inspect the relevant processing result or logs with appropriate access.

Confirm the intended recipient and check filtering or spam folders. Review the form provider’s delivery evidence where available. For WordPress developers, the wp_mail documentation explicitly distinguishes a successful processing result from the recipient actually receiving an email. The useful question is where this particular message stopped, not whether a button said “success.”

An inquiry can arrive correctly and still be missed because it reaches an unattended inbox, is assigned to the wrong person or never enters the expected workflow. Identify the owner and the expected next action. Keep this separate from judging lead quality: first establish whether the inquiry reached the right place.

Avoid installing several plugins or changing unrelated settings at once. Reproduce the issue, make the agreed change and repeat the test. Compare invalid input, a valid submission and any important follow-up step. If a system reports an uncertain result, reconcile it before retrying so you do not create duplicate records or notifications.

Share the page URL, platform, exact symptoms, when the issue began and whether anything recently changed. Include redacted screenshots and the test timestamp. Keep credentials and real customer details out of the message. This gives support a reproducible starting point rather than a vague report that “leads are down.”

Official guidance checked 2026-10-26.