How to get more contact form submissions

To get more contact form submissions, reduce unnecessary fields, explain what happens next and make the form easy to complete on mobile. Before testing persuasive copy or video, confirm that submissions actually work and reach the right person.

Check the complete submission path

Make a clearly identified test enquiry. Check required fields, validation errors, the confirmation message and delivery to the intended inbox or system. Repeat on a phone. A submit-button click is not proof of a successful submission.

Look for failures that visitors cannot recover from: an error that clears their message, a consent checkbox hidden below an overlay, or an unhelpful message after a network failure. Preserve entered information where practical and explain what the visitor can do next.

Ask only for information you need now

Review each field with the person who handles enquiries. Keep it if the answer is needed to respond, route the request or assess a real requirement. Collect details later when they do not affect the first reply.

For example, a service business may need the requested service and a way to reply. It may not need a full postal address before an initial conversation. This is a design example, not a rule that every form should use the same fields.

Use visible labels and mark optional fields clearly. Match the input type to the information, such as email or telephone. Do not rely on placeholder text as the only label.

Explain the next step

Tell visitors who receives the message and what happens after submission. State an expected response time only if the team can meet it. Make privacy information accessible beside the form without turning it into a wall of legal copy.

Reassurance should address a real concern. Show relevant contact details or customer evidence where it helps visitors assess the business and build trust. Avoid repeated proof blocks that push the form out of view.

Use video only when it answers something useful

A short introduction can explain who will read the request or what a consultation involves. Keep the same information in text. Do not require visitors to watch before contacting you, and check that a floating player does not cover the form or submit button.

Test the video as a separate change. Adding it alongside a shorter form and a new offer makes it difficult to identify which change affected submissions.

Measure completed enquiries and their quality

Define a successful submission using the confirmation or server response, rather than every click on the submit button. Separate genuine enquiries from spam and repeated tests. Compare completed submissions with the number of visitors who had a reasonable opportunity to use the form.

Review whether the enquiries contain enough information for the next step. A higher submission count is not necessarily useful if it produces more irrelevant requests. At low traffic volumes, allow enough observations before drawing conclusions and report the underlying counts.

What should you change first?

Fix broken delivery and mobile usability first. Then remove demonstrably unnecessary fields and clarify the next step. Once the form works reliably, test supporting copy, placement or an optional video introduction one change at a time.