Fix forms that won't submit or notify you

Forms are usually the most important thing on a page — if a lead fills one out and nothing happens, you can lose the lead without ever knowing it happened. This article covers the three separate ways a form can "fail" (it doesn't submit, it submits but nothing notifies you, or it submits duplicates/spam) and how to fix each.

#Symptoms

• Clicking submit does nothing, shows a spinner forever, or throws an error.
• The form appears to submit (thank-you message or redirect happens) but no contact shows up in your account.
• A contact is created, but you never got an email or SMS notification about it.
• The same person shows up as two or three separate contacts after filling out a form more than once.
• Submissions are flooded with obvious spam (gibberish names, random links in message fields).

#Likely causes

1. A required field or field type validation is blocking submission — for example, a phone field that requires a specific format, or a field marked required that's hidden by custom CSS so the visitor can't actually fill it in.
2. Custom code on the page is interfering. A conflicting script, an aggressive ad blocker on the visitor's browser, or custom CSS/JS you added can break the form's submit behavior without any visible error.
3. The form submitted successfully, but nothing is watching for it. Submission and notification are two different things — a form can create a contact just fine while having zero automated notification configured.
4. The notification action or workflow is misconfigured or was turned off. Automated email notifications and workflow-based notifications live in different places, and it's easy to set up one but assume the other is also active.
5. Duplicate contacts happen when the form doesn't have a way to recognize a returning visitor — usually because the form only matches on name instead of email or phone, or because multiple forms with different field mappings feed the same list.
6. Spam submissions come through when a form has no bot protection and is public-facing (linked from ads, indexed by search engines, or embedded on a high-traffic page).

#Step-by-step fixes (most common first)

#1. Test the form yourself, end to end

Submit a real test entry with your own contact details on the live published page (not just inside the builder preview). Note exactly what happens: does it visibly submit, show a thank-you state, and does a new contact appear in your account within a minute or two?

#2. Check whether the contact was actually created

Search for the test contact you just submitted. If the contact exists but you got no notification, the form itself is working — the problem is in notifications (skip to step 5). If no contact was created at all, the form itself failed — continue to step 3.

#3. Look for a hidden required field or bad validation

Open the form in the builder and review every field marked required. A field that's set to required but hidden by custom CSS, hidden by a "show/hide" interaction, or misconfigured to expect a specific format (like a phone number field that rejects your test number's format) will silently block submission for real visitors even though it looks fine to you as the editor.

Screenshot coming soon

The form editor with a required field highlighted and its validation settings expanded

#4. Test with custom code removed

If the page has custom CSS or JavaScript (tracking snippets, animations, sticky elements), temporarily disable it and test the form again. If it starts working, the custom code is interfering — check the browser console for JavaScript errors that reference the form or its submit handler, and adjust or remove the conflicting code.

Tip: Ad blockers and privacy browser extensions on a visitor's device can also silently block form scripts. If your own test works in a clean browser but a colleague's doesn't, have them test with extensions disabled before assuming it's your setup.

#5. Set up (or re-check) notifications

Notifications are configured separately from the form itself, in two possible places:

• Form-level notifications: open the form, use the notification bell icon, and confirm an email notification is turned on with a valid recipient address, and that any auto-responder to the submitter is configured correctly.
• Workflow-based notifications: check whether a Form Submitted workflow trigger exists for this specific form, that the workflow is published (not just saved as a draft), and that its notification action (internal notification, email, or SMS) points to the right person and hasn't been disabled.

Both can exist at once — if you're only checking one, you might miss where the setup actually broke.

#6. Fix duplicate contacts by standardizing the match field

Make sure the form requires and correctly maps an email or phone field, since that's what the system uses to recognize a returning contact instead of creating a new one. If you have multiple forms feeding the same audience, confirm they all map their email/phone fields consistently — one form using a differently-named custom field for email is a common cause of silent duplication.

#7. Reduce spam submissions

• Add a reCAPTCHA or similar bot-verification element to the form if available in your builder.
• Add a honeypot-style hidden field if your form type supports it, which real visitors never fill in but bots often do.
• Review where the form is linked from — an indexed or widely shared form URL attracts more bot traffic than one that's only reachable through your funnel flow.

#How to verify it's fixed

1. Submit a fresh test entry on the live page using a private/incognito browser window.
2. Confirm a new contact appears with the correct field values, without duplicating an existing contact.
3. Confirm you receive the expected notification (email and/or SMS) within a few minutes.
4. If a workflow handles the notification, check the workflow's execution history to confirm it ran without errors.
5. Have someone outside your team test once, especially if the original report came from a real visitor rather than your own testing.

#When to contact support

Reach out if a form fails to create a contact even with all required fields correctly filled, no custom code on the page, and a clean browser — or if a workflow's Form Submitted trigger shows the form was submitted but the workflow never ran. Include:

• The exact form name and the page/funnel step it's on.
• A screenshot of the form's field settings, especially any required fields.
• The time of a specific failed test submission.
• Whether the contact was created (check by searching the email/phone you tested with).
• A screenshot of the notification settings or workflow trigger you expect to fire.

#Related articles

• Changes not showing after publishing
• Layout looks wrong on mobile or a specific browser
• Tracking and pixels not firing

#Frequently asked questions

#The form works when I test it, but a customer says it didn't. What now?

Ask what device and browser they used, and whether they have an ad blocker installed. Also confirm they were on the live published URL, not a cached or outdated link someone shared with them. Most "works for me, not for them" reports trace back to a browser extension or a stale cached page.

#Can I get both an email and a text notification from one submission?

Yes — set up an email notification directly on the form and add an SMS action inside a Form Submitted workflow, or handle both entirely through the workflow if you prefer one place to manage it.

#Why do I see contacts with no name, just an email?

That usually means the form only required an email field and the visitor skipped optional fields, or a partial/abandoned submission was still captured. Review which fields are marked required if you need more complete data every time.

#Will adding bot protection reduce real submissions?

A properly configured verification step has minimal impact on real visitors. If you notice a drop in legitimate submissions after adding it, test the form yourself on mobile — some verification widgets render poorly on small screens and are worth double-checking there.