There Is One Field on Your Form Doing Most of the Damage

Two Tools, One Gap

Open your analytics. It will tell you how many people landed on the page with your contact form on it. Open your CRM. It will tell you how many submitted it. The difference between those two numbers is usually enormous, and everybody has made their peace with it.

What nobody can tell you is what happened in the middle.

Somebody arrived, read your page, decided they wanted to talk to you, and started typing. Then they stopped. That is a real event, with a real cause, happening to real people every day, and there is no row for it anywhere. Analytics counted a pageview. Your CRM counted nothing. The person who was two fields away from becoming a customer is filed under bounce.

Everyone Measures the Edges

The tools that claim to work on this measure the edges of the gap, not the gap itself.

Heatmaps show you where a mouse went, which is not the same as where a person gave up, and they tell you nothing about someone on a phone. Session recordings exist, but nobody is watching four hundred recordings to find a pattern. Form analytics products mostly report completion rates, which is the number you already had.

And the abandoned-cart tools built for e-commerce assume a cart. A consultation request is not a cart. Nobody adds a divorce to a basket.

The Thing That Makes This Solvable

We were already reading form fields. That is how ReCapture works: it captures the contact details somebody entered before they abandoned the form, so a business can follow up on inquiries that never arrived.

Which means we were sitting on the answer and using it for something else. If you know what somebody typed, you know which field they were on when they stopped typing. Not inferred, not modelled. The actual field.

So we built Breakpoint, and it does one thing: it names the field where your form loses the most people, from the sessions that never submitted.

Why It Is Almost Always Mobile

The first thing worth saying about Breakpoint is that it splits by device, because that is usually where the answer is hiding.

Take a phone number field. On a laptop somebody types ten digits and moves on. On a phone the numeric keyboard inserts a space, or the formatting mask fights the autofill, or the validation rejects a leading one. The person tries twice, cannot work out what is wrong, and leaves.

On your desktop that field is fine. You have tested it yourself, probably more than once. It has never failed for you. Meanwhile it is quietly killing a third of your inquiries, and the only people who know are the ones who left.

An aggregate completion rate will never surface that. Split by device, it is obvious in about four seconds.

What This Costs in Media Dollars

Here is the part that matters if you are buying traffic.

ReCapture already attributes every captured inquiry back to the channel and campaign that produced it. Put that next to Breakpoint and you can do arithmetic that was previously impossible.

Suppose you spent four thousand dollars on paid search last month, driving people to a page with that phone field on it. Breakpoint says sixty-one percent of the mobile visitors who reached that field stopped there. Attribution says most of your mobile traffic came from paid search.

You are not looking at a form problem. You are looking at a substantial portion of your advertising budget buying people who were then turned away by an input mask.

Nobody gets fired for a form field. Somebody absolutely gets fired for the equivalent in wasted spend, and until now there was no way to connect the two.

What We Deliberately Did Not Build

The obvious next step is to fix the form automatically. Detect the broken field, patch it, done.

We are not doing that, and the reason is worth stating plainly: the promise ReCapture makes is that nothing changes about how your forms work. Your submitted leads go exactly where they went before. We add a line of JavaScript and we read, we do not write.

Rewriting a client's live intake form from a third-party script is the single worst thing this software could do. Breaking somebody's contact form at two in the morning is not a feature, it is an incident.

So Breakpoint diagnoses. What you do about it is yours.

What You Actually See

It sits on the dashboard as one line: this form loses most people at Phone, with how many reached it, how many stopped there, and the percentage. Open it and you get every field in order, how many made it that far, and where the fall is steepest. Toggle between all traffic, mobile, and desktop.

It needs a handful of sessions before it says anything, because a pattern from four people is not a pattern. After that it fills in on its own and keeps updating.

Field names only, incidentally. Never what anyone typed into them. The diagnosis does not require reading somebody's message to know they abandoned it.

The Honest Summary

Most form advice is generic. Use fewer fields. Do not ask for a phone number. Put the submit button above the fold.

Some of that is right some of the time, and all of it is guesswork applied to your specific form. Breakpoint replaces the guess with the field name. It is a small thing to build on top of data we already had, and it answers a question that has been unanswerable since forms existed.

One field on your form is doing most of the damage. It takes about a week of real traffic to find out which one.