The practical takeawayTell people which field needs attention, explain the correction, and keep their valid answers in place.
- Identify the field
- Explain the correction
- Preserve the work
“Something went wrong.” The message appears after a visitor has entered their contact information and described a project. They cannot tell whether an inquiry arrived, whether a field needs fixing, or whether pressing the button again will send a duplicate. The wording takes seconds to write and can cost both sides a long conversation. A useful error explains the state of the transaction and gives the visitor a safe next step.
Separate a correction from a service failure
A missing email address is something the visitor can fix. A temporary failure between the website and the CRM is a different situation. A slow response after the server accepted a submission is different again. Work with the developer to identify what the form actually knows at each point. Write the message from those facts.
For a missing email, direct the visitor to the field and say why the address is needed. For a delivery problem, say whether the site retained the inquiry and what happens next. Only promise staff follow-up if the team has a record and a process for handling it. Uncertainty in the backend should trigger a design conversation rather than an invented assurance in the interface.
Put the guidance where the correction happens
Give every field a persistent label. Show its error next to it and connect the message to the input so assistive technology can announce it. On a longer form, provide an error summary that links to the affected fields. A visitor using a phone should not have to scroll past every successful answer looking for a red border.
Use examples when formatting matters. “Enter the month and year as MM/YYYY” is more actionable than “Invalid date.” Prefer accepting reasonable variations when the business process permits them. Ask why a phone number must include punctuation before teaching every customer the internal format. Validation can often normalize a harmless difference when the data is stored.
Keep a mistake from becoming a second task
Preserve valid answers after validation. If a person entered a long description and missed a required checkbox, the description should survive. Be deliberate about sensitive data and payment fields. Some providers intentionally require re-entry and have their own guidance for handling it. Explain the next action without exposing information the form should keep private.
Think about what happens when a person presses the button twice on a slow connection. Indicate that processing is underway and have the receiving system handle duplicate attempts appropriately. A disabled button alone cannot settle what happened on the server. Test the actual outcome in a safe environment and check how many records were created.
Rehearse the experience your visitor sees
On a phone-sized screen, leave two required fields empty and submit. Can you discover both problems, reach each field, and return to a clear submit action? Repeat using only the keyboard. A visible message at the top of the page may never be announced to someone whose focus remains below the form. Test with the assistive technology your organization supports.
Try a valid submission after correcting the fields. Follow it to the confirmation and receiving inbox or CRM. A green success message carries a promise just as much as an error message does. Document what the visitor sees and what staff receive so future changes can be checked against the same transaction.
Give support staff a part in the review
Ask the people answering public inquiries for the last few confusing form reports. Remove personal details and sort the reports by the action visitors took afterward. Did they give up, call a different office, or submit the same information several times? The pattern points toward the part of the message that is missing.
Rewrite one common error and rehearse it with a colleague who has never seen the form. Ask them what happened and what they would do next. If their answer matches the system's actual state, the wording is doing its job. Keep that example in the release checklist so a design refresh does not accidentally reintroduce the original uncertainty.



