What is a good contact form conversion rate?

Benchmarks put view-to-submit for contact forms around 9%. A better test is your own form: measure it, change one thing and compare.

How many fields should a contact form have?

As few as you need for the first reply: usually name, email and a message. Ask the rest in the conversation.

Should I add a phone field to my contact form?

Make it optional and say why you'd use it. A required phone field is one of the most common reasons people stop.

Does a captcha lower contact form conversions?

It can, especially visible puzzle captchas. Invisible spam checks or a honeypot field add less friction.

Contact form conversion rate: benchmarks, and how to get more people to send it

The Formleak team

Published 22 October 2026

Quick answer

Fewer than 10% of people who see a contact form send it: Zuko's benchmark data puts it at 9.09%, the lowest of any form type it tracks. To improve yours, cut fields you don't need before the first reply, explain the ones you keep, and find the field where people stop.

What's a normal contact form conversion rate?

In Zuko's benchmark data, 9.09% of people who see a contact form submit it, the lowest rate of any form type they've tracked. Across all form types, about 34% of people who start a form don't finish it (Zuko).

Those are two different numbers, and it helps to keep them apart:

View to start: how many visitors begin filling in the form. Low? The form may be hard to find, look long, or not answer "what happens next?".
Start to send: how many people who began actually sent it. Low? Something inside the form stops them, usually one field.

Your own form before and after a change is a better comparison than any benchmark. Traffic source, offer and audience change these numbers a lot.

Where contact forms lose people

Phone number, especially when it's required and nobody says why.
Budget or company size dropdowns, which feel like a sales filter.
A long message box with no hint of what to write.
A send button that says "Submit", with no idea of what happens next.
Captchas and error messages that appear only after clicking send.

Fixes, with new wording

Phone: before and after

Before: Phone*
After: Phone (optional, if you'd rather we call)

Optional and explained: people who want a call still give it.

Message: before and after

Before: Message*
After: What can we help with? (a sentence or two is enough)

A question and a size hint make starting easier.

Send button: before and after

Before: Submit
After: Send my question: we reply within 1 working day

Says what happens next, and when.

Two more fixes that often help: ask only what you need for the first reply (name, email, question), and show error messages next to the field as soon as someone leaves it, not after they click send.

Find your own leaking field

Measure view-to-start and start-to-send separately, so you know whether the problem is outside or inside the form.
If it's inside, look at the field funnel: the field where the most people stop is your first fix.
Change that one field, note the date, and compare the same number of days before and after.

Formleak gives you that field funnel for every form from one line of code, with a suggested fix and new wording for the worst field. See how to read the field funnel and what the suggested fix does.

Frequently asked questions

What is a good contact form conversion rate?: Benchmarks put view-to-submit for contact forms around 9%. A better test is your own form: measure it, change one thing and compare.
How many fields should a contact form have?: As few as you need for the first reply: usually name, email and a message. Ask the rest in the conversation.
Should I add a phone field to my contact form?: Make it optional and say why you'd use it. A required phone field is one of the most common reasons people stop.
Does a captcha lower contact form conversions?: It can, especially visible puzzle captchas. Invisible spam checks or a honeypot field add less friction.