First, separate missing enquiries from lost sales
This guide is for businesses that need a visitor to request a quote, book a conversation or ask about a service. It also applies to an online shop's trade or bespoke-order enquiries. A shop losing completed purchases needs a checkout check instead.
If messages already arrive but quotes go quiet, you have a different problem. Check fit, price, response and the next agreed action. Our guide to keeping sales follow-up organised covers that stage. More form submissions will not repair an unanswered inbox.
Start by sending a test enquiry from your own phone. If it fails, fix that before rewriting the page. If it works, follow the visitor's route from the advert, search result or social post to the page and form.
Check whether the right people reach the right page
A busy advice article can attract readers who have no intention of buying. An advert for urgent repairs can send people to a homepage that only talks about planned installations. Neither tells you that your form is the problem.
Use the reports you already have, if available, to look at the page people first land on, where they came from and whether they use a phone or computer. Separate service pages from general articles. Exclude your own tests and obvious spam where your existing tools allow it. If you do not have these reports, begin with the pages linked from your adverts, business listings and social profiles; you do not need to install tracking to test them.
Check the promise on both sides of the click. A visitor choosing “Book an evening appointment” should find evening availability and a booking route, not a generic list of services. If you serve one area, say so before the visitor starts the form. For a wider reach, explain delivery or remote-service arrangements.
Answer the questions that stop someone asking
Near the main enquiry button, explain what you offer, who it suits and what happens after contact. Add genuine examples of your work or relevant customer feedback only where you have permission and can support it. A stock photograph is not evidence of a completed job.
For example, a fitted-furniture business could replace “Solutions for your home. Contact us” with “Made-to-measure wardrobes fitted across Essex. Send your room dimensions and postcode to ask about a design visit.” This is illustrative wording, not a claim about a real business.
Help visitors judge the commitment. If prices vary, explain the main cost drivers and what you need to prepare a quote. If a minimum order or consultation fee applies, make it clear. Do not promise “free” or an instant response unless that is how you operate.
- Use a button that describes the action, such as “Ask for a quote” or “Check appointment availability”.
- Explain whether the next step is a call, an email, a booking or a purchase.
- Put relevant eligibility, location or order restrictions before the form, not in a rejection afterwards.
- Give a response time you can keep, including working days where needed.
A second way to contact you can help someone who cannot use the form. Offer only channels you monitor. Adding a chat box that nobody answers creates another dead end.
Ask only what you need for a useful first reply
Keep each question for a reason. A name, one usable contact method and a short description may be enough for an initial enquiry. A postcode can be essential for local work; a full postal address often can wait. Requiring a budget may help filter bespoke projects, but can stop someone who needs your advice before setting one.
Try this question for every required field: “What would we do differently in our first reply if we knew the answer?” Remove it, make it optional or ask later if there is no useful answer. Do not shorten a form so far that every submission needs the same avoidable follow-up.
Keep labels visible after someone starts typing. Mark optional fields clearly, explain unusual requests and show errors beside the field that needs attention. Do not make someone retype everything after one mistake. W3C's accessible forms guidance covers labels, instructions, validation and user notifications; GOV.UK's form-structure guidance explains why each question needs a purpose.
Run a complete mobile form test
Use a real phone if you can, not just a narrow desktop window. Tell the person monitoring enquiries that a test is coming. Use your own contact details and a clearly labelled test message, never a customer's information.
- Open the actual landing page from its normal link. Check that the offer and enquiry button are readable without zooming, and that banners do not cover the button.
- Open the form. Tap each field and check that the keyboard does not hide the question, help text or next control. Try the phone and email fields, dropdowns and any date picker.
- Leave a required field empty and enter a mistyped email address. Check that the error is understandable, focus can reach it and valid answers remain in place.
- Correct the errors and submit once. Check that any consent or anti-spam step can be completed. Note whether the page confirms receipt instead of simply clearing the form.
- Check the receiving inbox and any saved submission record. Confirm that the full message and contact details arrived, and that replying reaches the address you supplied.
- Check any promised acknowledgement. It should explain the next step and a realistic response time. Record the result and remove the test record when you no longer need it.
Repeat after a form, plugin, email-routing or website change. If a fault affects one browser, test that browser again after the repair. An urgent delivery failure needs action now, not a month of observation.
If the message does not arrive, trace where it stopped
On a narrow screen, scroll the table sideways to read each column.
| What you see | What to check next |
|---|---|
| The send button does nothing, or keeps spinning | Check required fields, anti-spam challenges and error messages. Give your website maintainer the page, time, browser and steps, without putting personal details in a public screenshot. |
| A success message appears, but there is no saved submission | Ask the maintainer whether submissions are meant to be stored and whether the server accepted the request. A success message alone is not proof of delivery. |
| A submission is saved, but no notification arrives | Check the destination address, spam or quarantine folder, mailbox capacity and forwarding rules. Ask the email or website provider to inspect delivery logs and sender authentication. |
| The notification arrives, but a reply fails | Check the submitted address and the form's reply-to setting. Send another test and reply to it rather than assuming the notification setup is correct. |
Do not turn off spam protection permanently to make a test pass. Ask for a fix that keeps legitimate enquiries usable. While a form is broken, display a monitored alternative contact route and explain it clearly.
Measure useful enquiries, not just button clicks
Keep a small record of the page changed, date, reason and result. Use existing reports and the enquiries you receive; avoid collecting extra personal information just for this check.
- Compare visits to the relevant enquiry page with completed submissions over the same period, where your existing reports support that comparison.
- Distinguish an enquiry-button click, a form attempt, a successful submission and a delivered message. They are different events, and you may not have evidence for all of them.
- Count genuine enquiries that fit your offer separately from tests, spam and requests you cannot serve.
- Check calls and other monitored contact routes too. Someone who phones instead has not necessarily abandoned the enquiry.
There is no single conversion-rate target that proves every business page works. Compare like with like: the same type of page, similar traffic sources and the same counting method. If an advert changes at the same time as the form, you cannot confidently credit the form for the result.
Low traffic makes percentages jump around. Keep the actual counts beside any rate and avoid declaring a winner from a handful of visits. Fix clear faults immediately; judge a wording change once you have enough relevant visits and genuine enquiries to see a useful pattern, rather than waiting an arbitrary number of days.
When a new tool is worth considering
Keep your existing form if it sends reliably, works on phones and asks the right questions. Clearer wording, fewer required fields and reliable delivery may be the whole fix.
A form builder such as Jotform is worth comparing when different answers genuinely need different follow-up questions or your current form cannot handle the information you need. Check submission limits, accessibility, storage, notifications and what happens to your data if you leave.
A landing-page tool such as Unbounce may help when you run distinct advertising campaigns and need separate pages without repeatedly rebuilding your main site. Skip it if the existing page can do that job. Neither purchase creates demand for an unclear or unsuitable offer.
These are links to our research-based guides, not evidence that we have tested your website or these products hands-on. Current provider links are direct and untracked; no commission is earned.
Questions to answer before making another change
Should I remove the form and use email instead?
A monitored email address can provide a useful alternative, especially during a fault. It does not automatically solve unclear services or irrelevant traffic. Keep the route that customers can use and your team can reliably answer.
What if a shorter form brings worse enquiries?
Restore the one question that would have identified the mismatch, or explain the restriction before the form. Judge whether the enquiries are useful, not simply whether there are more of them.
What should I ask my web designer?
Ask them to demonstrate a submission on mobile, show where it is stored or delivered, test error recovery and identify who receives failures. Give them a concrete fault or unanswered buyer question instead of “make the website convert better”.
What should I do today?
Send and trace one mobile test enquiry. Repair any failure, then ask someone unfamiliar with the page to explain what you offer and what happens after they press the button. Change the first unclear answer. Record what you changed and check the next real enquiries before adding software.
Sources and further help
This guide draws on published form-design guidance, reviewed on 19 September 2026. The business examples are illustrative, not customer results.