Business Contact Form: Which Fields Do You Actually Need?

For most business websites, three required fields are enough: name, email address and message. Everything else, such as phone number, company or timeframe, works better as optional. Fields you don't need for a first reply are best left out altogether.

No law lists which fields must be required. If you operate in Germany, though, the GDPR (DSGVO in German) sets a principle that shapes the answer: personal data must be limited to what is necessary for the purpose (data minimisation, Article 5(1)(c)). For a contact form, that means: make required only what you genuinely need to reply.

This guide covers the form itself. If your form works but nobody uses it, the diagnosis in website visitors but no enquiries is the better starting point.

Field by field: required, optional or avoid

The table assumes a typical contact form on a service business website. If you have a good reason to deviate, for example because you only advise by phone, write that reason down.

Note: this is practical guidance based on data minimisation, not a legal list. A form that leaves name and email optional is not wrong if you are happy to answer anonymous questions.

Why one name field, and why the phone number is optional

A single name field works better than separate first and last name fields, especially if your clients come from many countries. MDN, the web developer reference, notes that a single full-name field "avoids dealing with the wide diversity of human names". Google's web.dev guide on forms likewise recommends letting people enter their name in one input.

The phone number is the classic debate. If you can answer by email, you don't need it. As a required field it would then be hard to square with the rule that data must be limited to what is necessary. As an optional field labelled "for a call back", you still get the number from everyone who actually wants a call.

web.dev puts the general rule plainly: don't ask for data you don't need. Every extra field makes the form longer, and stored data is a responsibility.

The privacy notice next to the form

Under Article 13 GDPR, you inform people at the time you collect their data, including who is responsible, the purpose, the legal basis, how long you keep the data and their rights. The full details belong in your privacy policy (Datenschutzerklärung). Next to the form, a short note with a link is usually enough in practice.

Adapt the wording to what you actually do. The deletion point reflects the GDPR principle of storage limitation (Article 5(1)(e)): keep data only as long as needed for the purpose. How long that is for you can also depend on German tax and commercial record-keeping rules, so check with your tax adviser.

If your site is bilingual, the notice and the form labels should be in the same language as the page.

Do you need a consent checkbox?

Many forms show a required checkbox saying "I consent to the processing of my data". For simply answering an enquiry, that is often not the right construction. Besides consent (Article 6(1)(a)), the GDPR provides other legal bases:

• Article 6(1)(b): processing needed for steps taken at the person's request before entering into a contract, for example a request for a quote.
• Article 6(1)(f): legitimate interests, for example for general questions, unless the person's interests override them.

Which basis fits your form depends on the case and should be stated in your privacy policy. Have this reviewed by your data protection adviser or a lawyer familiar with German and EU data protection law. Additional purposes are different: a newsletter, for example, needs its own voluntary consent, such as a checkbox that is not pre-ticked.

Accessibility: labels, required fields, errors

A form that some people can't use loses enquiries. The key points from the web standards:

• A visible label for every field. WCAG 2.2 requires labels or instructions where input is expected (Success Criterion 3.3.2, Level A). A placeholder inside the field is not enough, because it disappears as soon as someone types.
• Mark required fields in the label, for example "(required)", or mark the optional ones with "(optional)". If you use an asterisk, explain it at the top of the form.
• Error messages that explain what went wrong and how to fix it, such as "Please enter an email address including @".
• The right input types and autocomplete values, so phones show the right keyboard and browsers can fill in name, email and phone.
• A success message after sending, so people know the enquiry arrived.

Spam protection without picture puzzles

Picture puzzles (CAPTCHAs) are a barrier for many people. W3C's accessibility working group writes that CAPTCHAs often prevent people with disabilities from completing a task, and describes alternatives. For a small contact form, these are often enough:

• Honeypot: a field hidden from humans that only bots fill in. The W3C note says this approach is easy to implement and should be considered.
• Rate limiting: one sender can only submit a certain number of times in a short period.
• Server-side checks: for example a minimum time between loading and sending the form, and plausibility checks on the input.
• Your mailbox's spam filter for whatever gets through.

If you use a third-party CAPTCHA service, also check whether it sends data to others or stores information on the visitor's device. That can affect your privacy policy and whether you need consent under § 25 TDDDG, the German rule on cookies and similar technologies.

Before and after

Which questions help you without overloading the form also depends on what your pages already answer. For structure and content, see the pages a small business website needs.

At Ichii, a contact option is part of the business website with up to 10 pages (€790 net plus VAT, one-time). We decide together which fields your form asks for. You supply the text for your privacy policy and Impressum; the legal review is a job for your adviser.

Your next step

Go through your current form with the table above and remove every required field you don't need for a first reply. If you are planning a new website, note the fields you want in your brief straight away. Our website brief template has room for that, and our business website page shows what's included and the price.