---
title: "Contact forms: fields, errors and delivery · Lyntev"
description: "Define fields, instructions, validation, errors and enquiry receipt. Includes a field contract, completed example and test matrix."
url: "https://lyntev.com/en/guides/create-contact-form"
language: "en-GB"
date_published: "2026-11-21T17:20:13.047Z"
date_modified: "2026-11-21T17:20:13.047Z"
---

1. [Home](<https://lyntev.com/en>)
2. [Practical guides](<https://lyntev.com/en/guides>)
3. How to create a contact form that collects what is needed and confirms delivery

# 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 [Lyntev](<https://lyntev.com/en/company>). Updated on 18 November 2026.
About 5 minutes to read.

[Start reading](<https://lyntev.com/en/guides/create-contact-form#leitura>)[Download worksheet](<https://lyntev.com/recursos/en/criar-formulario-contacto.txt>)

**A request that stays connected**The same reference follows the request and prevents duplicates.

Translation published on 21 November 2026. [Original Portuguese guide](<https://lyntev.com/guias/criar-formulario-contacto>); source revision 18 November 2026.

By the end, you can:

- Justify every field requested
- Handle errors without losing the person’s work
- Confirm recording, notification and follow-up

In this guide

1. [Link every field to a decision](<https://lyntev.com/en/guides/create-contact-form#decidir-os-campos>)
2. [Keep instructions close to the field](<https://lyntev.com/en/guides/create-contact-form#rotulos-e-preenchimento>)
3. [Fictitious example: request a maintenance assessment](<https://lyntev.com/en/guides/create-contact-form#exemplo-de-pedido>)
4. [Validate on the server and preserve entered information](<https://lyntev.com/en/guides/create-contact-form#validacao-e-erros>)
5. [Define destination, access and displayed information](<https://lyntev.com/en/guides/create-contact-form#rececao-e-privacidade>)
6. [Test the paths commonly forgotten](<https://lyntev.com/en/guides/create-contact-form#matriz-de-ensaios>)
7. [Deliver the form contract](<https://lyntev.com/en/guides/create-contact-form#ficha-formulario>)
8. [Sources and criteria](<https://lyntev.com/en/guides/create-contact-form#fontes>)

## 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.

Link every field to a decision

| Illustrative field | Decision supported | Rule |
| --- | --- | --- |
| Service | Route the enquiry | Required, understandable options |
| Email | 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 |

- [Choose fields for a catering enquiry for a conference in Coimbra](<https://lyntev.com/en/website-design/coimbra#city-focus>)

## 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.

- [W3C: accessible forms](<https://www.w3.org/WAI/tutorials/forms/>)
- [MDN: field types and attributes](<https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input>)

## 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.

From completing the form to support

1. **Explain**

  Say what is requested and why.
2. **Validate**

  Check data and allow correction.
3. **Record**

  Confirm receipt in the responsible system.
4. **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.

- [MDN: form validation](<https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation>)

## 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.

- [Your Europe: privacy and cookies](<https://europa.eu/youreurope/business/growing/digitalising/online-privacy/index_en.htm>)
- [Plan a CRM connection](<https://lyntev.com/en/guides/connect-website-form-crm>)

## 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.

Test the paths commonly forgotten

| 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.

- [W3C: formulários acessíveis](<https://www.w3.org/WAI/tutorials/forms/>)
- [MDN: tipos e atributos dos campos](<https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input>)
- [MDN: validação de formulários](<https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/Form_validation>)
- [Your Europe: privacidade e cookies](<https://europa.eu/youreurope/business/growing/digitalising/online-privacy/index_en.htm>)

## Continue to your next decision.

- [See an example landing page for registrations](<https://lyntev.com/en/services/landing-page-design>)
- [Integrate forms and CRM](<https://lyntev.com/en/guides/connect-website-form-crm>)
- [Assess accessibility](<https://lyntev.com/en/guides/make-website-accessible>)
- [Measure confirmed enquiries](<https://lyntev.com/en/guides/measure-website-results>)

[Explore the guide library](<https://lyntev.com/en/guides>)

## Put this decision into practice.

Steps, examples and worksheets to prepare the work in your business.

[Find a reading path](<https://lyntev.com/en/guides#percursos-title>)

### [How to prepare a multilingual website without contradictory information](<https://lyntev.com/en/guides/prepare-multilingual-website>)

Translate the whole journey and organise maintenance for every version.

### [How to prepare website quote requests that the team can assess](<https://lyntev.com/en/guides/prepare-website-quote-requests>)

Collect what is needed for the next decision and explain what happens after submission.

## Explore the research behind this decision.

Articles with sources, clearly identified examples and worksheets for assessing websites, AI customer service and business management systems.

[Explore all articles](<https://lyntev.com/en/research>)

Experience and measurement · About 12 min

### [Your website gets visits. Why aren't you receiving enquiries?](<https://lyntev.com/en/research/website-visits-without-enquiries>)

A method for finding obstacles between a visit and an enquiry: audience, offer, forms, performance and measurement, with a practical observation guide.

## Would you like to apply this to your business?

Send us your worksheet or explain what you need to improve. We help you choose the next step for your project.

- [Lyntev assistant Immediate answers about services, prices and timescales, with a cost estimate. Read the assistant guide](<https://lyntev.com/en/help/ai-assistant>)
- [WhatsApp +351 928 412 891. The message is only sent when you confirm it in WhatsApp. Write on WhatsApp](<https://wa.me/351928412891?text=Hello!%20I%20came%20from%20the%20Lyntev%20website%20and%20would%20like%20to%20discuss%20a%20project.>)
- [Form Describe what you need and receive the reply by email. Complete the form](<https://lyntev.com/en/contact>)
- [Email contacto@lyntev.com Send an email](<mailto:contacto@lyntev.com?subject=Request%20for%20information>)

![Wellinton Oliveira](<https://lyntev.com/media/autores/wellinton-oliveira.webp>)

Written by

[Wellinton Oliveira](<https://lyntev.com/en/company>)

CEO of Lyntev

Technology with context, original analysis and sources you can consult.
