1. Submit a test like a real customer
Open the public website on your phone, enter a test name and an email address you control, and submit it. Record the time. Check whether you see a success message or an error. Repeat in another browser or on mobile data if the first attempt fails.
Do not use a real customer's private details in test submissions.
2. Check the destination inbox and spam folder
Search the receiving mailbox for the test name, subject and form provider. Check Spam, Promotions, filters and forwarding rules. If the message appears in Spam, the form may have worked; the remaining issue is notification delivery.
For broader email troubleshooting, read our business email spam guide.
3. Verify the form endpoint and first-use activation
Some hosted form services require verification before they deliver submissions. For example, FormSubmit documents a first submission followed by an email confirmation step. Confirm the recipient address is spelled correctly and the service is activated. Other providers have different setup steps.
On a custom backend, check whether the server route exists and whether the sending provider reports an error.
4. Inspect browser errors and required fields
If nothing happens when you click Send, check required-field validation and open the browser developer tools' Console and Network tabs. Look for failed requests, blocked scripts, wrong endpoint URLs or a JavaScript exception. A page can load successfully even when the submit handler fails.
Make sure the button is actually inside the form and is not permanently disabled after an earlier attempt.
5. Check what the success message really means
A success message may mean only that a provider accepted the request. It does not prove the notification reached the business inbox. Test the entire path: submit → provider acceptance → notification email → staff reads it → customer receives a reply.
If you use a webhook or CRM, verify that it saved the test lead as well.
6. Confirm reply-to behavior and spam controls
Some services support a special reply-to field. If that field is missing or misconfigured, clicking Reply may contact the form provider instead of the customer. For FormSubmit, the documented field is _replyto. Check spam protection too: a hidden honeypot field should stay empty during legitimate submissions.
Never expose private API keys or credentials in public HTML.
7. Set up a backup path for important leads
Place a visible business email or phone number near the form so customers can reach you when it fails. If your provider supports a submission archive or a secure CRM record, use it as a second check. Restrict access to lead data and define a reasonable retention period.
8. Test again after every deployment
Run a small test after changing JavaScript, form services, domain settings or notification addresses. Record the test date and whether the message reached the right inbox. A five-minute test is cheaper than discovering weeks later that quotes never arrived.
Once delivery works, improve response speed with our lead follow-up workflow. If you need help diagnosing the setup, contact BizTechHarbor.
References and further reading
Need a practical website solution?
We help small businesses build clear, mobile-friendly websites and improve their customer inquiry process.
Discuss your project →