Ask enough to start a useful conversation
Choose fields around the next step your business actually takes. A repair company may need the service, postcode and a short description. A consultant may need the type of project and a contact email. A restaurant enquiry is different again: a private event request needs different details from a table booking.
For each required field, ask what happens if someone cannot answer it yet. If your team can give an initial response without it, consider making it optional. A customer may know the problem they want solved without knowing the technical name, final budget or exact completion date.
- Label the form with its purpose, such as Request a quote.
- Ask for one dependable way to reply.
- Use a short message field for context.
- Explain when specialist enquiries need a different route.
Make every field understandable on a phone
Keep a visible label alongside each input. Placeholder text disappears during typing, so it is a poor substitute for a clear label. Use plain words that match how customers describe their needs, and make required and optional fields easy to distinguish.
Try the form at the width of a real phone. Check that labels remain visible, buttons are easy to reach and the keyboard does not obscure the next action. Someone should be able to move through the fields without hunting for the right control. These checks support usability; they do not by themselves prove the whole website is accessible.
Make mistakes easy to correct
Submit the form with a required field missing and then with an incomplete email address. The error should explain what needs changing and preserve the information already entered. Avoid a generic message that forces the visitor to guess which field failed.
Browser validation helps visitors correct simple mistakes, but the server must also check incoming data. A development review should cover accepted fields, sensible length limits, unwanted submissions and what happens when the receiving service is unavailable.
Follow a test enquiry into the inbox
Send an identifiable test message from the published website. Use ordinary sample information, then check the destination inbox, spam folder and any system that stores the enquiry. Confirm that the subject, message and reply address arrive correctly. Repeat from mobile after a form, email-provider or domain change.
A success screen can confirm that the website accepted a submission without proving the eventual email arrived. Ask your developer how failed deliveries are detected, what the user sees on a failure and how your team can recover a genuine enquiry. Keep test messages clearly marked so they do not appear in sales totals.
- Record the test time and the page used.
- Check that the intended person receives the complete message.
- Try replying and verify the reply goes to the test address.
- Check that failure messages offer a useful next step.
Give each enquiry an owner
Decide who checks new messages and who covers absences. Keep a simple record of received, replied, quoted and won enquiries so an unanswered email does not disappear among other work. The system can be small; what matters is that someone owns the next action.
Tell visitors what happens after they submit, using a response expectation your team can actually meet. Avoid promising an immediate reply if nobody monitors the inbox at that time. A confirmation should explain the next step without treating an enquiry as a confirmed booking or order.
Measure the full journey
Track successful submissions separately from form-button clicks. Then compare genuine enquiries, conversations and paid work. More clicks are not useful if the messages are irrelevant or never reach your team. Record when you change fields or wording so you have a clear basis for reviewing what happened.
Start with one complete test and fix the most concrete failure first. If the form works but enquiries remain weak, review the service information, examples, location coverage and next step around it. The form is one part of a website that needs to explain why someone should contact your business.
Business websites by Finstark · Website improvements and support