The short verdict
- A form that shows “Thanks!” has not necessarily sent anything.
- Generated forms often have no backend, a test key, or email that lands in spam.
- Test it from outside, on a phone, and check the inbox, every time you change the site.
01The silent failure
This is the problem we most want people to check today. A visitor fills in your form, clicks send, sees a friendly confirmation and waits for your reply. You never receive anything. Neither of you knows. On a site where the form is the main way to get in touch, that can go on for weeks.
It happens because building a form that looks right is easy, and making it actually deliver a message needs several pieces outside the page.
02The five usual causes
1. There is no backend
The builder drew the form and a success state, but the submit handler only shows the message. Nothing is sent anywhere. This is common when the form was generated before any email service was connected.
2. A test or expired key
The form posts to a service like a database, an email API or a form tool, using a key from the prototype. The trial ended, the key was rotated or the free tier ran out, and errors are swallowed without telling anyone.
3. Email that lands in spam
The message is sent, from an address on your domain, without the SPF, DKIM and DMARC records that prove it is allowed to. Your own inbox treats it as suspicious and hides it.
4. Spam protection that blocks people
A captcha that fails on some browsers, or a strict filter that throws away anything with a link. Real enquiries get caught along with the bots.
5. It broke after an edit
Someone prompted a design change to the contact section, and the tool regenerated the form without its connection. The form still looks identical.
03How to test it properly
- Use a different device and network. Your phone, on mobile data, not your logged-in laptop.
- Use an email address you do not own. A friend’s, or a fresh one, so you see what a stranger sees.
- Check the inbox and spam folder of every recipient. And note how long it took.
- Reply to it. Make sure the reply goes to the visitor, not to a no-reply address.
- Submit with mistakes. Leave a field empty, type an invalid email. Errors should be clear and next to the field.
- Repeat after every change. Put it on your launch checklist and your monthly one.
“A form is not a design element. It is a pipe, and you only find out it is blocked by testing it.”
04Making it reliable
Send every submission to two places: an email inbox and somewhere stored, like a spreadsheet, a CRM or the form tool’s dashboard. If email fails, nothing is lost. Set up the domain’s email records properly. Use spam protection that does not ask humans to prove anything, like a honeypot field or an invisible check. And set up a simple alert if no submissions arrive for an unusually long time.
Webflow forms store submissions in the site settings as well as emailing them, which covers the first point by default. Our own form runs through a small function that logs every send for the same reason.
05Questions people ask
How do I know if I have already lost enquiries?
Check the form service’s logs or dashboard, if there is one. If the form never had a backend, there is no record, and the honest answer is that you cannot know.
Is a mailto link a safer option?
It never fails silently, but many visitors do not have a mail app set up on the device they are using. Offer it next to a form, not instead of one.
What are SPF, DKIM and DMARC?
DNS records that tell inboxes which services may send email for your domain. Without them, form emails often go to spam.
Can you test my form?
Yes. Send us the link and we will test it from outside and tell you where the message goes.
