Contact form best practices: field design that converts

A contact form is where curiosity becomes a lead. But ask for the wrong fields, in the wrong order, and you'll watch people abandon halfway through. Contact form best practices matter because every missing field costs you a conversion.

This guide walks through ten contact form fields and strategies that shift the needle on form completion rates, response satisfaction, and actual lead quality. We'll cover gaps most guides skip—like security threats, accessibility compliance, and the real trade-off between data richness and submission volume.

Email address

The email field is non-negotiable. It's your only reliable way to reach someone who has expressed interest. Without it, even a completed form is worthless.

Use a proper HTML5 type="email" input so mobile browsers show the email keyboard and validation happens client-side. Pair it with clear, accessible labelling. Don't hide it behind placeholder text alone—use a visible label above the field. Test your field in a screen reader; anyone relying on ARIA labels needs to hear "Email address, required, text input" clearly.

Keep email optional only if you have a fallback contact method (phone, live chat during business hours). If it's required, be explicit: "Email is required so we can reply to you."

Phone number

Phone fields trip up international forms and frustrate users with strict validation. The best approach: make it optional unless you genuinely need to call (e.g., you're a plumber, a therapist, or a recruitment agency).

If you do require it, don't lock the field to UK numbers only. Use a library like libphonenumber to validate international formats flexibly, or use a country-code selector (like Twilio's format). Never strip or auto-format without user consent—some people paste formats your regex doesn't expect, and they'll abandon rather than reformat.

In industries with high callback expectations—trades, clinics, consultancy—a phone field can improve conversion because it signals you'll respond quickly. But set response-time expectations upfront. If you say "we'll call within 2 hours", keep that promise. Broken expectations tank repeat inquiries and damage trust more than a slower response time announced honestly.

Message or enquiry details

The open-text field is where you collect the actual problem. Don't ask for a novel. A simple "Tell us what you need" with a 500–1000 character soft limit encourages detail without overwhelming the user.

This is where the conversion data-richness trade-off plays out. Requiring a detailed message reduces abandonment because users know they're answering a question, not writing an essay. But some industries (consulting, retainer services) benefit from longer context—in those cases, use progressive profiling: ask for the message first, then ask follow-up questions only if the initial message suggests a good fit.

An emoji-picker or templated examples ("I need a website redesign", "I have a technical issue") can guide users without forcing them into rigid categories. Keep it human and conversational.

Company name

Company name is useful if you're B2B. For freelancers, coaches, and service providers, it's less critical—and optional fields hurt completion rates. Make the call based on your actual sales process.

If you collect it, don't validate too strictly. Some people use trading names, some use personal names, some use "N/A" or "Freelance". Accept what they give you.

Website or portfolio URL

A URL field can save you time pre-qualifying leads. If someone is shopping for a web designer and you can see their current site, you immediately understand their budget and taste. This field is almost always optional, but don't make it required—people without a web presence might be perfect clients.

Use type="url" and allow optional validation (don't error on "no www" or "https only"). A portfolio link is more useful than a business website, so ask specifically: "Link to your current website or portfolio (optional)."

Budget or price range

This is the elephant in the room. Asking for a budget in a contact form feels aggressive to many small businesses, yet it filters out 90% of unqualified inquiries before you waste a call.

The honesty: collecting budget upfront reduces form submissions but increases lead quality. A service-based business (agency, consultant, trainer) might see a 40–60% drop in submissions after adding budget, but the remaining leads convert 3–4× faster. A local service (plumber, electrician) might see a smaller drop because budget questions feel normal.

Frame it tactfully: "What's your rough budget range? (This helps us understand the scope.)" Offer radio buttons ("Under £1k", "£1–5k", "£5–10k", "£10k+") rather than a text field. People avoid typing numbers but will click a button.

Skip this field if you're in high-volume, low-touch sales (e.g., newsletter signup, free trial). Include it if you're in consultative, bespoke work.

Industry, role, or use case

Knowing what someone does helps you personalise the follow-up and route the lead to the right team member. For B2B forms, industry is gold: "Are you in e-commerce, SaaS, services, other?"

Use a dropdown or radio buttons with 4–8 options, plus "Other" with a text box. Open dropdowns with 50+ options paralyse users; stick to your actual customer segments.

This field usually doesn't tank completion rates because it feels low-effort. Its value is post-submission: you can send industry-specific follow-up emails and prioritise high-fit leads.

Accessibility compliance and security

Two gaps most guides skip: WCAG compliance and contact form security. Both shape conversion and trust, though invisibly.

Accessibility. Every field needs a visible, associated <label> tag (not just placeholder text). Use aria-required="true" and aria-invalid="true" on error states. Colour alone must never indicate required vs optional—use text ("Required") or a symbol with aria-label. Test your form in a screen reader (NVDA, JAWS, or Mac VoiceOver). A user with low vision or dyslexia won't submit a form they can't navigate.

Read our complete guide to web accessibility for small business websites for detailed WCAG standards.

Security. Contact forms are common phishing and credential-stuffing targets. Attackers scrape your form, auto-fill it with fake data, and use it to collect valid email addresses or test stolen credentials.

A CAPTCHA (reCAPTCHA v3, hCaptcha) stops automated submission bots but can frustrate accessibility users and slow mobile users. Use it if you're in a high-spam vertical (B2B SaaS, recruitment); skip it if you're low-volume (freelance therapist, one-person consultancy).

Better: rate-limit your form endpoint (one submission per IP per 60 seconds), validate email format strictly, and log suspicious patterns. If you use Resend or Formspree for form handling, they handle spam filtering behind the scenes.

Never ask for passwords or payment card data on a contact form. Never auto-populate fields with user data from an external service unless you've explicitly told the user why.

Required fields vs optional fields

The default rule: ask for as few required fields as possible. Research from Unbounce shows a 3-field form converts ~26% higher than a 5-field form.

But "fewer" doesn't mean "vague". A form with just "Name" and "Message" is useless because you can't reach them. The minimum viable contact form is:

• Email (required)
• Message or enquiry details (required)
• Everything else optional

From there, add required fields only if:

1. You genuinely can't help without the information.
2. Your target audience expects to provide it (e.g., a plumber asking for address before quoting).

Progressive profiling is the middle ground: show a 2-field form initially, then reveal 2–3 more fields conditionally based on the user's first answer. "What brings you here?" → if they pick "Website design", show budget and current website URL. This feels less overwhelming and improves abandonment metrics.

Sitewright

Sitewright builds bespoke contact forms as part of a full site, wired to Resend or Formspree. Forms are hand-coded in React with accessibility built in. You get WCAG-compliant labels, client-side validation, and spam protection without extra bloat.

• Custom form fields via drag-and-drop page builder (Grow tier+) → edit forms yourself without code.
• Real-time form submission alerts → know instantly when a lead arrives.
• ARIA labels and semantic HTML baked in → screen-reader compatible from launch.
• Rate-limiting and email validation on every form → stops credential-stuffing and spam bots.
• Contact form replies via transactional email → lead notifications arrive reliably, every time.

Feedback or NPS field

Optional, but powerful for lead qualification. A simple "How likely are you to recommend us to a colleague? (1–10)" tells you whether someone is genuinely interested or just browsing.

This field is low-effort for users but high-value for you: scores of 8+ are hot leads; scores of 1–5 are tire-kickers. You can route them differently or adjust follow-up tone.

Use a slider or radio buttons (not a text box). Don't make it required—it'll tank completion rates if people feel they're being graded.

Timeline or urgency

For service-based businesses, urgency matters. "When do you need this?" filters dreamers from buyers and helps you forecast pipeline.

Offer radio options: "Immediately", "Within 2 weeks", "Within 1–3 months", "Just exploring." People who click "Immediately" are warmer leads; you can call them the same day.

This field is optional and rarely causes abandonment. It's worth including if your sales cycle is long or your team can't accommodate last-minute projects.

Picking the right one

A contact form is a conversation starter, not a questionnaire. The art is knowing which fields serve your sales process and which ones are just noise.

Sitewright embeds forms into a full website, so context matters. A pricing page might have a 2-field form ("Email" + "Let's talk pricing"); a homepage might have a 4-field form ("Email", "Company", "Message", "Budget"); a resource download might have a 5-field form with progressive reveal. The form matches the journey.

If you're building from scratch or redesigning an existing form, audit your last 50 submissions. Which questions did you actually use to qualify or prioritise? Keep those fields required; make the rest optional. You can always ask follow-up questions in the reply email.

• Fewer required fields = higher completion rates, but lower-quality data. Balance urgently matters.
• Progressive profiling (conditional fields) = best of both worlds when you have multiple lead sources or varied audience segments.
• Accessibility compliance and security are invisible until they fail. Invest in proper labels, validation, and spam protection upfront.
• Response-time transparency boosts trust. "We'll reply within 24 hours" is more powerful than "we'll reply soon."
• A well-designed form captures the right leads at the right time. The rest is follow-up.

Test your contact form with real users before launch; watch where they pause, what they skip, and what they complain about. The numbers will tell you exactly which fields earn their place.