Why aren't my website leads showing up in my CRM?
Because somewhere between the form and the CRM, one link in the chain broke without telling anyone. A website lead passes through four or five systems before it shows up on your screen: the form itself, a spam filter, a connector or webhook, the CRM's own rules, and the alert that's supposed to reach your phone. Any of them can fail while the prospect still sees "Thank you, we'll be in touch." The fix is almost never a rebuild. It's a 15-minute test that follows one lead from end to end and finds where it stops.
We wire forms into agents' CRMs for a living, and the failure is rarely dramatic: an expired login, a renamed field, a duplicate rule nobody remembers turning on.
Where do website leads get lost?
Think of the lead as a package with five handoffs. Each one has a typical way of failing, and almost none of them produce an error the prospect or you will see.
| Handoff | How it fails quietly | Where to look |
|---|---|---|
| 1. The form | The submit button works but the form posts nowhere, or a plugin update broke it. The visitor still gets a thank-you page. | The form tool's or website's submission log |
| 2. Spam protection | A CAPTCHA or spam filter flags a real person, often an older visitor on a phone, and discards or quarantines the entry. | The spam or "blocked" tab in the form tool |
| 3. The connector | The Zapier-style automation, plugin or webhook that carries the lead loses its login or gets switched off. | The connector's run history and connection status |
| 4. The CRM's rules | The CRM rejects the record because a required field is empty or a value doesn't match a dropdown, or it merges the lead into an older contact. | The CRM's import or error log, and the existing contact with that phone or email |
| 5. The alert | The lead is in the CRM but no one knows. The notification email went to spam, or went to an address no one checks. | Your spam folder and the CRM's notification settings |
Why does the connector stop working without warning?
Because most connectors run under someone's login, and logins change. If the person who set up the integration changed their password, left the agency, or revoked an app's access, the connection can stop passing data and nothing on the website changes.
Some tools also switch themselves off. Zapier's help documentation says a Zap is turned off automatically when 95% of its runs in the last seven days resulted in errors and it ran more than 20 times in that period. Sensible, but one bad week, say after a CRM field was renamed, can leave the automation off until someone notices, and any warning goes to whoever owns the account, which may not be you.
The honest counterpoint: connectors are reliable when someone watches them. The problem is setting one up at launch and never opening its run history again.
Why would the CRM reject a lead it received?
CRMs enforce their own rules, and a website form doesn't always know them. The common ones we run into:
- A required field the form doesn't send. If the CRM requires a last name and your short form only asks for a first name, the record can fail on arrival.
- A value that doesn't match a dropdown. The form sends "Medicare Supplement" and the CRM field only accepts "Med Supp." Some CRMs drop the whole record over one mismatched value.
- Duplicate merging. Many CRMs match new entries to existing contacts by email or phone number and update the old record instead of creating a new one. A spouse using the shared household phone, or a prospect who filled out your form last year, can vanish into an existing contact, sometimes with tags or fields overwritten. The lead was saved, but it never shows up as new.
Duplicate merging surprises agents most, because the CRM did exactly what it was set up to do. Check those settings before you blame the website.
Why aren't the email alerts arriving?
If you rely on a "new lead" email, the first suspect is your spam folder, and the second is the sending address. Many website forms send their notification "from" your own domain without being authorized to. Google's email sender guidelines require all senders to set up SPF or DKIM authentication for their sending domains, and say mail that doesn't meet the requirements may be marked as spam or rejected. A form that sends unauthenticated mail from your domain is exactly the kind of message that ends up there.
Fixing the DNS records is worth doing. But the bigger fix is not using email as the main channel for leads at all. Send the lead to the CRM first and treat the email as a backup. Then have the CRM push a text or app notification to your phone, because a lead that sits in an inbox for an afternoon is already cooling. We covered why speed of follow-up matters more than call-versus-form in do calls or web forms convert better for agents.
How do you test your lead form in 15 minutes?
- Use the live site, on your phone, on cellular. Not the page builder's preview, and not office Wi-Fi. Pick a real page a prospect lands on, such as a county or Medicare page.
- Submit with real details you control. A real email address and a phone number that can receive texts. Fake addresses on test domains often get rejected by email tools and CRMs, which makes a working setup look broken.
- Check the form's own log. Did the submission get recorded? Look in the spam or blocked tab too.
- Check the connector's run history. Find your test run. A "success" there only means the connector sent it, so keep going.
- Find the contact in the CRM. Search by the phone number. Confirm it's a new record, every field came through, the source page is attached, and any consent checkbox value arrived too.
- Time the alert. Note how long until your phone buzzed. If it took more than a few minutes, or never came, that's your fix.
- Repeat with a second test lead using the same phone number. This shows you how your CRM handles duplicates before a real household does.
Do this once a month, and every time something changes: a new theme, a new plugin, a CRM switch, a staff member leaving. Integrations tend to break after changes, not at random. During Medicare's Open Enrollment Period, October 15 to December 7, test weekly. That's when a broken form costs the most.
What about consent records?
If your form carries TCPA consent language for calls and texts, the CRM should receive the consent too, not just the name and number. That means the checkbox value, the time of submission and the page it came from. If the connector drops that field, you have a lead with no record of what they agreed to. Confirm the exact language and what records you need with your FMO or carriers. This isn't legal advice, and the rules differ by line of business.
Does any of this affect AI search?
Not directly; no AI assistant sees your CRM. But being cited by one only pays off if the person who clicks through reaches you. Our AEO guide for insurance agents covers getting found. This post is about not losing the lead once you are.
Frequently asked questions
Why are my website form submissions not showing up in my CRM?
Almost always because one link between the form and the CRM failed without an error message. The usual causes are an expired connector login, a field the CRM requires that the form doesn't send, a spam filter discarding the submission, or the CRM merging the lead into an older contact. Submit your own form and follow that one test lead through every step to find which link broke.
Why am I not receiving emails from my website contact form?
Check the spam folder first, then confirm the notification address on the form has no typo. If both are fine, the email is probably being sent from an address your domain hasn't authorized. Google's sender guidelines require every sender to set up SPF or DKIM, and unauthenticated mail can be marked as spam or rejected. Better still, don't rely on email at all: send the lead to your CRM and use email only as a backup alert.
How do I test my website form integration?
Submit the live form, not a preview, from your phone on cellular data, using a real email address and phone number you control. Then confirm four things: the site showed a confirmation, the submission appears in the form tool or website's log, a new contact appears in the CRM with every field filled in, and your phone received an alert. Note the time each step took.
How often should I test my website lead form?
Once a month at a minimum, and every time anything changes: a new website theme, a CRM switch, a password change on the account that owns the connector, or a new plugin. Integrations tend to break after changes, not at random. During Medicare's Open Enrollment Period, October 15 to December 7, test weekly, because that is when a broken form costs the most.
Can a CRM delete or merge a website lead?
Yes. Many CRMs check new submissions against existing contacts by email or phone number and update the old record instead of creating a new one. A returning prospect or a couple sharing one phone number can disappear into an existing contact, sometimes with tags or fields overwritten. The lead was saved, but nothing in your new-leads view shows it.
Where we fit
Every site we build sends form leads straight into your own CRM with the source page attached, and alerts your phone, and we run the end-to-end test with you before launch so you've seen a lead arrive with your own eyes. What's included with each plan is on the what you get page.
Not sure your form is reaching you?
Bring your URL to a 15-minute call. We'll submit a test lead with you, trace it through your form, connector and CRM, and show you where it stops.
Book a free 15-minute demo →