A contact form that gets more submissions asks only for the fields that are truly needed, keeps a visible label above every field, shows errors instantly and clearly, opens the right keyboard on mobile and lets the browser autofill. After sending, it shows a clear thank-you screen, links to the KVKK privacy notice and offers alternative channels such as phone and WhatsApp.
The form is the moment a visitor on a business site becomes a lead. Small mistakes in its design and wording let enquiries quietly disappear, no matter how much traffic you send to the site. The sections below go through the form field by field.
How many fields should a contact form have?
A contact form should have only as many fields as you really need to respond to the enquiry; for most service businesses that means a name, a phone number or email, and a short message. Every extra field increases the effort. If details like budget or company size can be asked in the first call, they should not be required on the form.
- —Essential: full name, phone or email (one of the two may be enough), message.
- —Optional: company name, service of interest (dropdown), preferred time to call.
- —Avoid: national ID number, full home address, date of birth and other data the enquiry does not need.
- —For long quote forms: split fields into 2-3 steps and add a progress indicator.
How should required fields and labels be shown?
Required fields and labels should be shown in a way that never disappears while the form is being filled in. Every field needs a visible label above it; placeholder text should not stand in for the label, because it vanishes once the user starts typing. Required markers should be consistent: if most fields are required, marking the rest as "(optional)" is clearer.
Visible labels are also an accessibility requirement: screen readers announce the field together with its label, and clicking the label focuses the field. Placeholder text should only offer an example, such as a format hint like "05XX XXX XX XX" in a phone field.
For your project
How should form errors be shown to users?
Form errors should be shown right next to the field concerned, as soon as the user leaves that field, with a sentence that explains how to fix the problem. Writing "The email address seems to be missing an @ sign" instead of "Invalid input" saves the user from guessing. When the submit button is pressed, all errors should be summarised and focus moved to the first invalid field.
- —Signal errors with text and an icon, not colour alone.
- —Do not show errors before the user has finished typing; validate on leaving the field.
- —Never wipe what the user entered after an error; only mark the invalid field.
- —Accept different phone formats, including spaces and dashes.
Which technical details make forms easier on mobile?
The technical details that make forms easier on mobile are the correct input types, autocomplete attributes and touch targets large enough for a finger. A type="tel" field opens a numeric keypad and a type="email" field opens a keyboard with the @ sign. Values like autocomplete="name", "email" and "tel" let the browser fill saved details with a single tap.
- —Use type="tel" and type="email" to open the right keyboard.
- —Add autocomplete="name", "email", "tel" and "organization" values.
- —Keep fields and buttons large enough to tap comfortably; do not shrink text on mobile.
- —Lay the form out in a single column; side-by-side fields raise the error rate on mobile.
- —For spam protection prefer invisible methods (a honeypot field, server-side rate limiting); heavy puzzles tire out real users too.
What does KVKK require on a contact form?
The most basic KVKK requirement on a contact form is that visitors can easily reach the privacy notice (aydınlatma metni) at the point where data is collected. Under Turkish Law No. 6698, the data controller must disclose why data is processed and to whom it may be transferred. A link to the notice directly below the form is the practical way to meet that duty.
Informing and explicit consent are different things. Processing data to answer the visitor's own enquiry usually does not rely on explicit consent; but if you want to use the same data for marketing messages, you need a separate, unticked consent checkbox. Merging the two into one checkbox is a common mistake. For wording specific to your situation, consulting a lawyer is advisable.
How should the form heading and submit button be worded?
The form heading and submit button should be worded so that visitors know exactly what happens when they fill in the form. A "Contact us" heading with a "Submit" button sets no expectation; a heading like "Get a reply about your project within 24 hours" with a "Request a quote" button explains both the benefit and the next step. Only promise a response time you can keep.
- —Heading: state the benefit or the response time, not just "Contact".
- —Short description: say in one sentence who will reply and how soon.
- —Button: concrete text that starts with a verb, such as "Request a free discovery call".
- —While sending: disable the button and show a loading state to prevent double submissions.
- —Placement: do not confine the form to the contact page; add a short version at the end of service pages too.
A short reassurance near the form also reduces hesitation: a line such as "Your details are only used to reply to your enquiry", together with the privacy notice link, sums up what happens to the visitor's data. The sentence does not replace the privacy notice, but it complements it.
What should happen after a form is submitted?
After a form is submitted, the visitor should land on a thank-you screen or page that clearly confirms the enquiry arrived and explains what happens next. A sentence like "We have received your message and will call you within one working day" removes the uncertainty. The same step also serves as the trigger for conversion tracking in Google Ads and GA4.
A form does not suit every visitor. Some want to talk right away, so a tappable phone number and a WhatsApp link should sit next to the form. If clicks on those channels are tracked as separate conversions, you can see which channel really brings enquiries. Also remember to test regularly that form notifications actually reach your inbox.
