A contact form that goes nowhere is one of the quietest ways a service business loses leads, because nobody sees the failure. The visitor fills it out, sees a message or nothing at all, and moves on. You can find most of these failures with seven checks: submit a real test, confirm where it lands, and see what the visitor sees.
Here is the uncomfortable part. If your form is broken, you will not get an error message. You will get silence, and silence looks exactly like a slow week.
Websites change. A developer moves hosting, a plugin updates, an email address gets closed, a spam filter tightens. Any of those can break a form that worked the day the site launched. Nobody tells you. The form still looks fine, and the submit button still clicks.
Run these checks from a phone, not your office computer. Many of your visitors will meet the form on a phone, and that is where problems tend to show up first.
The seven checks
| Check | How to test it | What a failure looks like |
| 1. The submission arrives | Fill out the form with a real test entry using an email address you do not normally use. Wait ten minutes. | Nothing arrives, or it arrives hours later. |
| 2. It lands in a monitored inbox | Find which address receives notifications, then confirm someone reads that inbox daily. Check the spam folder too. | Notifications go to a retired address, a former employee, or spam. |
| 3. The visitor gets a confirmation | Read what appears on screen after submitting, and check whether an email or text follows. | The page refreshes with no message, or the visitor is left guessing. |
| 4. It works on a phone | Submit from an actual phone on cellular data, not Wi-Fi. | Fields overlap, the button is hidden by the keyboard, or the page jumps. |
| 5. It asks for only what you need | Count the required fields. Ask if you could call back with just a name, a number and a short description. | Ten fields, several required, and a visitor who gives up halfway. |
| 6. Spam protection does not block real people | Submit as a stranger would, from a fresh browser and a different device. | A puzzle that will not load, or a legitimate submission rejected as spam. |
| 7. Someone owns the response | Ask who replies, and how quickly. Time it from the test submission. | Everyone assumes someone else has it, and the reply happens days later or never. |
Notes on each check
1 and 2: Arrival and destination
These two catch the worst failures. A form can submit successfully on the website's side and still deliver to nowhere, because the notification address is wrong or the sending service is blocked. Test by actually submitting, not by looking at the settings page.
Then follow the trail. Which email address receives the notification? Do you own it? If the answer is "the person who built the site," you have a risk. Change it to an address you control, and consider adding a second recipient so one person on vacation does not stall everything.
3: The confirmation
The visitor should know two things: it worked, and what happens next. "Thanks, we got your message and will reply by end of the next business day" does both. A blank refresh does neither, and a visitor who is unsure may submit three more times or call a competitor.
4: Phone behavior
Load the page on your own phone and try to complete it one-handed with a thumb. If it takes effort for you, it takes more effort for a stranger standing in their driveway looking at a dripping ceiling.
5: Field count
Every extra required field is a reason to leave. For a contractor, name, phone, address or zip, and a short description of the job is usually enough to start. For a real estate agent, name, phone or email, and what they are looking for. You can ask more once you are talking. Each field should earn its place.
6: Spam protection
Spam filters exist for good reason, but overly strict ones reject real people. Test them, and check the spam or junk folder of your form's notification inbox from time to time. A legitimate lead sitting in junk is a lead you never saw.
7: Ownership and speed
This is the check most sites fail, even when the technology works perfectly. A form is a promise that someone will respond. If nobody is assigned, the form works and the business still drops the lead. This connects to the wider issue I describe in The Follow-Through Problem: the lead arrives and nothing in the business acts on it.
Extra checks for real estate agents
If you are a Texas real estate agent, your site and form also sit inside advertising rules. TREC has requirements for how a license holder's name, brokerage and license information appear in advertising, and your form page should follow them. Check the current rules and confirm with your broker, because I cannot give legal or compliance advice.
Texting and calling leads also brings consent questions under the TCPA. If your form collects a phone number and you plan to text or call it, make sure the form language and your process match what your counsel and brokerage require. Avoid promises about closed prices or property values in form confirmation messages and follow-up. Reach out if you want a second set of eyes on how your forms and consent language hold up.
How often to repeat this
Run all seven checks after any change to the site, and run checks 1 and 2 once a month even if nothing changed. Put a reminder on your calendar. It takes five minutes, and it is the cheapest insurance a website has.
When the form is not the real problem
Sometimes the form works and the site around it is the issue: slow pages, unclear services, no service area. If you are weighing a rebuild, reach out and we will walk through the ranges and what a tested-end-to-end build looks like for your trade.
What to do this week
- Submit your own form from your phone, on cellular data, and time when it arrives.
- Confirm who receives the notification and that the inbox is watched daily.
- Rewrite the confirmation message to say what happens next and when.
- Cut required fields down to what you need for a first call.
- Name one person who owns form replies and set a response time.
- Set a monthly reminder to test again.