How to create a contact form that collects what is needed and confirms delivery
A form connects an intention to a support process. To work well, it should request enough information, explain how to correct problems and confirm a true result. The team also needs to find the enquiry and know who replies. This guide covers the interface and initial delivery; a CRM connection can be prepared afterwards with its own contract.
By the end, you can:
- Justify every field requested
- Handle errors without losing the person’s work
- Confirm recording, notification and follow-up
Link every field to a decision
List what the team needs to know for the first step. For every field, write the decision depending on it. If nobody uses information at this stage, consider collecting it later. Name, reply channel, service and a brief description may suffice for a simple journey; a technical request may need other data. The set should come from the process, not copying another form.
Distinguish required from optional and explain formats that may raise questions. Do not force a phone number when the journey can be completed by email unless there is a specific need. Avoid requesting complete documents when a reference is enough. For attachments, state types, limits and purpose before file selection, and define who receives them and how long they are needed.
| Illustrative field | Decision supported | Rule |
|---|---|---|
| Service | Route the enquiry | Required, understandable options |
| Reply to the person | Required in this example | |
| Phone | Call if requested | Optional |
| Message | Understand the context | Instructions on what to describe |
| Attachment | Assess a detail | Only when needed and with explicit limits |
Keep instructions close to the field
Use visible labels associated with fields. An example inside a field can help but disappears when typing and does not replace the name. Choose suitable types, such as email, and autofill suggestions matching the requested data. An appropriate mobile keyboard reduces effort without removing the need for server validation.
Group related information and place instructions before they are needed. For a message field, you can explain “State the service and the situation you want to resolve”. For an attachment, show limits before the selector. If the form is long, consider logical stages with a final review; do not split three simple fields merely to create a progress animation.
Fictitious example: request a maintenance assessment
Fictitious company Ponto Norte receives maintenance enquiries. The example form contains service, location, email and message, with an optional phone number. A test request could use service “Preventive maintenance”, location “Test area” and message “We would like to assess two pieces of equipment; we will provide models at a later stage”. The reply address would be an inbox controlled by the team for testing, without using a customer’s data.
The button says “Send assessment request”. After a confirmed record, the message says the request was received and the team will analyse the information. It does not promise an already-booked visit or an undefined deadline. The test keeps a reference and confirms content at the destination. This example shows the interface contract; final design may vary while preserving the same decisions.
- Explain
Say what is requested and why.
- Validate
Check data and allow correction.
- Record
Confirm receipt in the responsible system.
- Follow up
Assign an owner and reply channel.
Validate on the server and preserve entered information
Browser validation helps detect errors early but can be bypassed. The server must validate fields, limits and files before accepting them. Define formats carefully: international names and numbers do not always fit rules designed for a single example. Overly restrictive validation can reject legitimate information without improving enquiry quality.
Show a message explaining the problem and possible correction. Associate it with the field and preserve valid data. If the network fails, distinguish “submission could not be confirmed” from a success confirmation. Define retry behaviour and protection against duplicates. A disabled button may prevent some clicks, but does not replace consistent handling of repetitions on the server.
Define destination, access and displayed information
Design what happens after submission: where the record is kept, who receives a notification, who follows up and how a pending enquiry is identified. If it depends only on email, test the address, message classification and a delivery failure. A shared inbox without an owner can receive every enquiry and still leave people without replies.
Present privacy information consistent with the data and suppliers used. Separate requested contact from additional options, such as promotional communications; do not add preselected choices for different purposes. Optional analytics or third-party resources should respect applicable choices before loading. Technical review checks behaviour; the wording and grounds for processing need to match the specific case.
Test the paths commonly forgotten
Prepare fictitious data and test in an appropriate environment. Include valid completion, an empty field, long text, accented characters, a slow response and repetition. Test keyboard and mobile use. For attachments, try the agreed limits and confirm that the destination does not accidentally make the file publicly accessible.
Common errors are showing success before saving, erasing the whole message after a failure and counting button clicks as received enquiries. In every test, compare the interface with the actual record. After changing the form, repeat notification and follow-up too: changing a field name may break the message sent to the team even when the page looks correct.
| Case | Result to check |
|---|---|
| Valid enquiry | One record and consistent confirmation |
| Invalid email | Instructions beside the field and data preserved |
| Temporary failure | Clear status, recovery and no false success |
| Retry | Duplicate handling according to the contract |
| Without optional resources | Essential contact remains usable |
Deliver the form contract
The worksheet should accompany the interface and implementation. Keep success and failure examples, owners and evidence of receipt. When the team wants to add a field, return to the initial question: which decision now depends on it? This lets the form evolve with support instead of becoming an inventory of information nobody uses.
Worksheet for your project
Objective and the team’s next action: Field / purpose / required / format / limit: Instructions and error messages: Data and attachments that must not be requested: Record destination and owner: Notification and reply channel: Confirmation shown to the visitor: Repetitions, failures and retry: Privacy information and optional resources: Test cases and request references: Keyboard and mobile results: Date, version and person responsible for approval:
Sources and criteria
Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.
