Explain what happens after submission
A person who wants to know whether a repair is possible may find “Request a repair estimate” clearer than “Submit.” Near the button, say who will reply and where the reply will go. Give a timeframe only if the team can meet it.
A confirmation message should describe what has happened. If the server accepted the enquiry, say it was received. Confirming that it reached the person responsible takes a separate check.
Require only what's needed for the first reply
Ask the person who handles enquiries to review two recent requests without sharing customer details. What did they need to respond? If the first reply is by email, a phone number is usually unnecessary. If the customer requests a callback, you'll need the number.
Budget works the same way. A customer may not know the figure at this stage. Make it optional, or ask for a range only where it affects which service you can offer. Mark optional fields in words so people don't have to guess.
Try the form on a phone and with a keyboard
Get to the button with the on-screen keyboard open. Check that labels remain visible after typing, you can move between fields and it's clear where to go when something is wrong. A mistake in one field shouldn't clear the ones you've already filled in.
“Enter your work email, for example name@example.com” gives someone a way to fix the error. “Invalid input” makes them hunt for it. Associate the message with its field and check that keyboard and screen-reader users can find it.
Test delivery with the owner's permission
On a public site, you can review the copy, visible fields, focus order and how the form works at different widths. Agree a time and recipient with the owner before sending a test. Use fictional details, mark it as a test and record its reference.
| Step | What you can verify | Evidence to keep |
|---|---|---|
| Form review | You can read the field, reach the button and understand the message | Screenshot or steps to reproduce, with the device noted |
| Approved test submission | The application accepted a specific enquiry and showed a response | Time and reference in the application log |
| Delivery check | The intended recipient or sales team received the same record | Matching test record in the inbox or CRM |
Compare form starts, accepted submissions and delivered enquiries
If analytics is in place, compare how many people started the form, how many submissions the server accepted and how many enquiries reached the team. People can click the button several times, including when there's an error.
Count confirmed server records and exclude duplicates and tests.
Step events and permitted error codes are enough for troubleshooting. Keep field values, phone numbers, email addresses and free text in the system your team uses to handle enquiries. Compare the same periods, pages and devices.
If there isn't much data, start with test results and support reports.
Choose the audit that matches your question
Choose the free audit when you need to understand your own website first. Choose the competitive audit when your next decision depends on comparing your website with relevant alternatives. Both turn supported evidence into practical actions.