Form abandonment

Why didn't they finish the form?

Your analytics can tell you that many visitors start a contact or quote form and never send it. It can't tell you why. Was the price unclear, a field confusing, the form broken on their phone, or were they just comparing options? The quickest way to find out is to ask.

By The Little Ask editorial team ·

Illustration of an unfinished web form next to a small question bubble

Summary

  • Analytics shows where. A question shows why.
  • Ask after someone hesitates, never while they type.
  • Never read what they typed into the form.

Try the three example questions. Nothing you type is sent or stored.

The usual reasons, and why you can't guess

Teams often assume the form is too long. Sometimes it is. But visitors also leave because they needed information the page didn't give them, because they didn't trust what happens after submitting, because something didn't work on their device, or simply because they weren't ready yet. Each of these needs a different fix, so guessing wrong wastes effort.

  • Missing information: price, delivery time, what happens next.
  • Trust: "Will I get sales calls?"
  • Technical problems: a validation error, a button that doesn't respond, a field that won't accept a valid phone number.
  • Timing: they were just looking, which is fine to know.

When to ask

  • After they've started the form, not on arrival.
  • When they show signs of leaving: exit intent on desktop, a quick scroll up or time without progress on phones.
  • After a validation error, if you suspect the form itself is the problem.
  • Never after they've submitted. Pause the survey for visitors who completed the form.
  • Never mid-typing. Interrupting someone who is filling in the form is the surest way to lose them.
How exit intent works on desktop and mobile

Ask for opinions, not form data

A form abandonment survey doesn't need anything the visitor typed. Knowing that someone started the form, hit an error or submitted is enough - those are events, not values. Collecting half-filled names, phone numbers or emails from people who chose not to send them is both a privacy problem and unnecessary.

Questions that work

  • "What stopped you from completing the form?" Open text. The most useful single question.
  • "Did anything prevent you from sending your request?" Yes/No, with an optional "What wasn't working?" if they say yes. Good for catching technical issues.
  • "Was there anything you needed to know first?" Surfaces missing information.
More example questions

Turning answers into fixes

Read the answers weekly and group them by theme. A few people mentioning the same field on mobile is a strong signal to test that field on a real phone. Change one thing, then see whether the theme fades. AI grouping can help once there are many answers, as long as each theme links back to what people actually wrote.

How AI groups feedback into themes