Lead Conversion
The form works. So why is the lead not in your CRM?
A form can accept a submission and still fail to deliver the lead. Here are the four places it goes missing, and how to find out which one is yours.
A form can accept a submission, thank the visitor, send you an email, and still never create a record in your CRM. The two things are separate deliveries from the same event, and one can fail silently while the other keeps working for months.
That’s the reason this particular failure survives so long. Nothing looks broken. The visitor got a confirmation. You got an email. The only thing missing is the record you’d need to follow up properly, count at the end of the month, or tie to a source.
The four places a lead goes missing
In roughly the order we find them:
- The delivery was never set up. The form sends an email and nothing else. Common on sites where the form came with the template and the CRM arrived later.
- The connection exists but the fields don’t match. The CRM requires something the form doesn’t collect, or expects a value from a fixed list and receives free text. The record is rejected at the door.
- The connection broke and nobody was told. An API key expired, a permission changed, a plan downgraded. Automation tools usually keep a log of the failure. Almost nobody reads it.
- The record arrives and lands somewhere nobody looks. It’s created, but on the wrong object, without an owner, or with a status that keeps it out of the view your team actually works from.
The last one is the most frustrating, because the integration is technically working and the lead is still effectively lost.
Why the notification email hides it
An email notification and a CRM record are two different jobs. The email is an alert: it tells somebody a thing happened. The record is the thing itself: it has an owner, a status, a source, a history, and it can be counted.
When the email keeps arriving, the alert keeps working, so nobody investigates. Meanwhile the month-end number comes out of the CRM, and the CRM is missing leads. The gap looks like a bad month rather than a broken pipe.
If your team answers leads out of an inbox, you don’t have a lead process. You have a habit that works until somebody’s on holiday.
What you can check in the next thirty seconds
Fill in your own form. Use a real email you can access and put “test” in the message so nobody panics.
Then follow it all the way through, in this order:
- Did the confirmation page load, or did you get an error or a blank page?
- Did the notification email arrive?
- Is there a new record in the CRM with your name on it?
- Does that record have a source, and is it assigned to somebody?
Any step that fails is your answer. Do it from a phone on cellular data rather than the office wifi, because that’s how most of your customers will do it, and a surprising number of failures only show up there.
Why counting is the real fix
Testing a form tells you it works today. What you want is to know when it stops.
Three numbers should agree every month: submissions recorded by the form, notifications sent, and records created in the CRM. When they diverge, something between them failed and the smaller number tells you where. It’s a five-minute check and it’s the only thing that catches a slow leak, because a slow leak never announces itself.
The other thing worth watching is the repeat submission rate. If the same person submits twice in a few minutes, something on their end didn’t confirm properly. On one site we worked on, that rate went from around 1% to nearly a quarter of all submissions when the page every form redirected to was accidentally set to draft and started returning a 404. Submissions were still recording, so nothing looked wrong from the inside. The rate was the only thing that would have shown it.
When to bring somebody in
The diagnostic is cheap and you can do most of it yourself with the list above. Where it gets involved is when the site has several generations of form, or when the CRM has been configured by several people over several years and nobody can say which fields are required and why.
The work is making one submission produce one complete record, every time: consistent fields on every form, a mapping that matches what the CRM expects, an owner and a source on arrival, and an alert when a delivery fails rather than a silence. That’s part of how we handle integrations.
The measure of success isn’t that the form works. It’s that you’d know within a day if it stopped.
Common questions
How would I even know leads are missing?
Compare counts. Your form tool, your email notifications, and your CRM should agree on how many submissions happened last month. When they do not, the gap is real and the smaller number is where the leak is.
Our notification emails come through fine. Is that not proof?
It proves the form fired and the email sent. It says nothing about whether the record reached the CRM, because those are usually two separate deliveries from the same submission. One can fail while the other keeps working, which is why the failure goes unnoticed.
Could a required field be causing it?
Frequently. If the CRM requires a field the form does not collect, or expects a value from a fixed list and gets free text, the record is rejected at the door. The submission still succeeded from the visitor's point of view, which is what makes it hard to spot.
Is a notification email enough on its own?
It is enough to answer the lead and not enough to run the business. An inbox has no owner, no status, no follow-up, and nothing you can count at the end of the month. The email should be the alert, not the record.
How often should this be checked?
Test after any change to the form, the CRM, or anything between them, and once a quarter regardless. A submission that used to work can stop working because something upstream changed, and nothing announces it.
More in this category
Your quote button can be dead for six seconds and nobody will tell you
A form that records every submission can still be losing you customers. What we found on a 34-form site, and the two habits that would have caught it.
How many fields should a quote form have?
Every field you add costs you submissions, and some of them earn it back. How to decide which questions belong on the form and which belong on the call.
Why your leads arrive with no idea where they came from
If most of your leads show up as direct traffic, the forms are the reason, not the analytics. Here is what to check and what it costs you.
Want this looked at on your site?
Send yourself a test enquiry right now and follow it all the way to the CRM record. If it does not arrive, we can find out where it stopped.