Find the missing handoff
Someone can fill out a form, see a thank-you message, and still leave you with no usable inquiry. A website form has several handoffs. The page sends data to a provider or server. That system records or rejects it. A notification travels to a mailbox. Then a person sees it and replies.
Test one handoff at a time. Do not start by rebuilding the whole website.
Run a controlled test
- Use a clearly marked test message. Include the date and a phrase you can search for. Do not put passwords, customer details, or card information in it.
- Confirm the browser result. Capture the page confirmation and note the exact time. That only confirms the browser-side step.
- Check the provider record. Review the form service or server log for the same test. A provider receipt is stronger evidence than a thank-you page.
- Check every delivery destination. Look in the intended inbox, spam or quarantine area, and any shared mailbox rules.
- Confirm a reply owner. A working form still fails the customer when nobody is watching the inbox.
Use the symptom to narrow the fix
| What happened | Where to look |
|---|---|
| Every test fails before confirmation. | Required fields, browser errors, form configuration, or the endpoint. |
| The provider records a test but email never arrives. | Notification address, email rules, spam or quarantine, and sender setup. |
| Some inquiries arrive and others do not. | Field validation, attachment limits, spam controls, and patterns in the missing messages. |
| Messages arrive but sit unanswered. | Shared inbox access, alerts, coverage, and a named reply owner. |
Why a one-time test is not enough
Providers can quarantine a message, a mailbox rule can change, and an email address can be updated later. Keep a short test record after changes and test again after a form, domain, or email provider changes. If you use Netlify Forms, its submission guidance explains that verified and spam submissions are separate views.
Protect the customer path
Use a visible phone or email route as a backup for a high-value action. Keep the confirmation page clear about what happens next. Never ask visitors to send passwords through a contact form. Keep the test record with the form owner.
The IT support service covers the technical investigation when the path is unclear. If booking is the problem, map the calendar paths with the double-booking guide.
Talk to Little Fight.
Send a website link, an error message, or a few lines about the work. We’ll take a free first look and explain what we can help with.
9am–9pm Eastern. After hours, leave a message.