The form is the beginning of customer service, not a technical addition to the footer. The contact user devotes time and transmits data, so he needs a clear goal, a sense of security and information about the next step. The form should only collect the data needed to answer, keep the values entered after the error and act on the phone and keyboard. Its effectiveness should be assessed not only by sending, but also by the quality of contacts and problems occurring along the way.
Fields, labels and expectations
Each field should be justified. The earlier the decision stage, the less information the user is ready to provide. The label must remain visible when writing is started, and the example value cannot replace it. Optional fields are worth marking, and appropriate data types make it easier to use a phone keyboard.
Before the form you need to explain its purpose, the expected response time and what happens after sending. Another form fits a quick question, another one for the valuation of the complex project. The preservation of the context of the subpage allows you to limit the questions and better convey the request to the right person.
Errors, accessibility and privacy
The validation should indicate a specific problem at the field and in the summary, do not delete the entered data and not be based solely on color. The form must operate by keyboard, have logical order and visible focus. After sending, the user needs unambiguous confirmation, and the e-mail message can summarise the notification.
Texts on data and possible consents require a match to the actual process by the person responsible for this area. The form should clearly distinguish the handling of the query from additional voluntary actions. Spam protection cannot create obstacles to man; it is worth combining server mechanisms, frequency limitation and discrete trap fields.
Measurement and handling after sending
Analysts can measure start-up, errors and send, respecting privacy. A large number of start-ups without ending may indicate an area requiring checking; they do not themselves explain the reason for resignation. The test must be performed in different browsers and for incorrect scenarios, including loss of connection and double click.
The notification must reach the responsible person or CRM safely. Monitoring should detect shipping problems, and the procedure will determine the response time. Even an ideal form will not help if messages go to spam or no one owns the next step.
Contact form test
- Each field has a visible label and a legitimate purpose.
- The form explains the response time and the next step.
- Errors are specific and do not delete data.
- Keyboard and phone support is working properly.
- Consents and information about the data are understandable.
- Spam protection doesn't block people.
- Shipping, delivery and service time are monitored.
Explain which files are needed
The attachment may help you to pass a briefing, example or document, but it should not be mandatory without justification. Before selecting a file, specify the accepted types and size limit. You should not know these conditions only after long waiting for the shipment.
It is also worth explaining what kind of material the company expects. Short instructions limit the transfer of files that do not help to answer your request.
Keep control of your choice
The person filling the form should see the names of the selected files and be able to delete them before sending them. If one attachment does not meet the conditions, the message should indicate this item. The amendment should not unnecessarily delete the description of the whole case.
Check selecting a file from your phone and using the keyboard. Drag to the field may be an addition, but not the only method.
Design security on the system side
OWASP recommends, among other things, limiting the types and size of files allowed, verifying the content and controlling the storage and access site. The name or the declared file type itself is not sufficient. Details are described in detail. Safe File Acceptance Guide.
The scope of the security should correspond to the implementation. Files from the notifications should not accidentally go to the public library of the site's materials.
Pick up a message with an attachment
The test should confirm that the right person can open the material and the user receives a real confirmation. Also check the limit overrun and the connection interrupted.
We write about the stages of a more comprehensive query in multi-step form guideAttachments are useful when they help in conversation and have the entire service process worked out.
The most common questions
How many fields should the form have?
Only as much as you need at a given stage. Simple contact may require three fields, and the qualification of a complex project with several additional questions.
Is CAPTCHA Necessary?
Not always. It is worth first to use less burdensome mechanisms and implement additional security proportionally to the problem.
Should the form send a confirmation?
This confirmation is helpful if it does not reveal sensitive data and clearly describes a further step.
Summary
A good form combines simplicity, availability, privacy and reliable submission of the application. The quality of the whole process also depends on what the company does after clicking “send”.
