Job builder-form-submissions-not-reaching-owner · revised 11 October 2026
Make one Webflow, Squarespace or Wix form deliver every submission to you
One form on a Webflow, Squarespace or Wix site delivers a test submission to the named inbox and keeps a stored copy; the cause and each setting changed are written down.
You might be seeing
- Customers tell you they used the form but no email arrives
- The form shows a thank-you message, yet the builder shows no submission or the inbox shows no email
- Notifications stopped after you changed your email address, plan or the form itself
No passwords, keys, card details or admin invites needed to start.
What usually happened
A builder form passes through three separate stages: the page accepts the submission, the builder stores it, and a notification is sent to an address. Each stage has its own settings and its own failure, so a missing email can mean a button that does not submit, a storage option that is off, an outdated recipient, a custom action that bypasses the builder, or a mailbox that filters the sender.
Who it’s for: Owner of a small-business site built on Webflow, Squarespace or Wix whose enquiry or booking form seems to send nothing to anyone.
Usually starts when: A customer says they sent a message and you never saw it, or the notifications stopped after an email address, plan or setting changed.
The result: A test submission from the live page, with every field filled, is stored by the builder and arrives at the named address, and you hold a short note of the failing stage, the setting that changed and the sender addresses your mail administrator should allow.
Check whether this job fits
Answer these without sending logins or customer messages. Nothing is submitted unless you choose to contact us.
Checks you can run yourself
Send one labelled test
On the published page, submit the form with the word TEST in the message and note the time. Then look in the builder's own submissions list, your inbox and your spam folder.
Look for: If the builder shows the entry but no email arrives anywhere, the fault is in notification or filtering. If it shows nothing, the fault is earlier.
What you get
- A plain-language diagnosis naming the stage that failed
- The corrected form settings, with a before and after list
- A test log with the time of each submission, storage entry and delivered email
Included
- One form on one Webflow, Squarespace or Wix site, traced through page, storage and notification to the stage that fails
- Correction of the builder-side settings for that form: recipient, storage option, automation or notification rule, submit control and hidden required fields
- Test submissions from the published page, with sent and received times recorded
- A written list of the sender addresses to allow at your mail provider and the settings changed, with their old values
Not included
- Changing your mail provider, its spam filters or your domain mail records; see the email authentication guide for that work
- Spam and bot blocking, which is a separate job from missing real submissions
- Forms made with a third-party form service embedded in the page, or custom-coded forms
- New integrations to a customer database or sheet that never existed
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
A labelled test submission from the published page, with every field filled, appears in the builder's stored submissions and arrives at the named address (inbox or spam folder), with the times of each step recorded.
Evidence: The test log, a screenshot of the stored entry and the received message with private details masked.
The delivered message contains every field you named, none empty or cut short.
Evidence: The received message compared with the field list.
If a second recipient is named, a second labelled test reaches that address too.
Evidence: A second test log line and a screenshot of the received message.
The list of settings changed shows old and new values for each, and the sender addresses to allow match the builder's own documentation.
Evidence: The before and after settings list with documentation links.
Sign-off. You send your own test, see it arrive, and sign off before payment. Your authorised account holder confirms any change to recipients.
If it fails. If the agreed checks fail, you do not pay for this fixed scope. We hand over the findings and agree whether to stop or re-quote; no surprise work.
When it fits, and when we stop
It fits when
- The form is a native form of the builder, on a site that is published by the builder, not exported to another host
- You can send a test submission from the live page and open the builder dashboard that should hold it
- The inbox that should receive it is one you or your mail administrator can check, including spam
We stop and tell you if
- The form is from an embedded third-party service, or the site code was exported and hosted elsewhere, where the builder does not process submissions
- The site is on a trial or a plan whose limit has been reached, so the plan must change first, which is your decision
- The only cause left is your mail provider rejecting the builder, and its administrator will not change it
What could go wrong
The handover lists every setting changed with its old value, so each can be put back by hand. Test entries can be deleted from the builder's submissions list.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| The notification is sent correctly but your mail provider keeps filtering it. | We record the delivery attempt and give you the sender addresses to allow; we cannot guarantee inbox placement at a provider we do not control. |
| Test submissions create entries or trigger other automations connected to the form. | We label tests clearly and ask you before the first test which connected tools could react. |
| Changing the recipient sends private enquiries to the wrong person. | Every recipient change is confirmed by you in writing before it is saved. |
An independent reviewer checks the redacted before and after evidence, the list of changes and the way back, and looks separately at anything that touches customer data, payments or logins, before you see the result.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the form, the expected recipient and the test method in writing
- Reproduce the missing delivery with a labelled test submission from the published live form and record each stage: page, builder storage, notification, inbox
- Compare the form's recipient, storage and automation settings with the builder's own documentation and fix the one that fails
- Send a second test and a test to a second address if one is named
- Have a separate reviewer check the settings list and the test log
- Hand over the diagnosis, settings changes and the sender addresses your mail administrator should allow
This is a one-off job, not emergency cover or a subscription. We confirm eligibility, the total price, a start window and a delivery date before you accept. Work starts only after agreed inputs, secure access and necessary permissions are in place. Builder plan, app, domain and payment-provider charges are yours and are excluded unless the written quote includes them. No charge or booking is created by an enquiry.
Need to keep it working?
If forms keep breaking when you change your site, a monthly check of forms and embeds is available as a separate standing service.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Check the builder's own form troubleshooting article first; many cases are a wrong recipient or the spam folder. support.squarespace.com
- If the real cause is your own mail domain's authentication, your mail provider's set-up guides cover it, and it is a different job from a builder form.
Questions
Do you need my email password?
No. We never ask for mailbox passwords. We ask you or your mail administrator to check the inbox and spam folder for the labelled tests.
What if the email goes to spam?
We record that, give you the sender addresses to allow and show you where to add them. We cannot control how your mail provider filters.
Does this cover a form from another service?
No. Only the builder's own form tool is covered. An embedded form is handled by the service that made it.
Send an enquiry
Send us
- The page address of the form and which builder it is on
- What you see after pressing submit, and whether the builder dashboard shows any entry for a test you send
- The address that should receive it, written with the first part masked, and roughly when notifications last worked
Later, once you agree
- Builder access at the role named in the access section, set up by you and removable at any time
- A mailbox or alias for test deliveries that you control
- Any email provider message log or bounce you can export, with other people's details removed
You keep the live site, the builder account, the domain and all customer data. Access is agreed with you in writing before any work starts, and no work starts until it is. Any access we use is through a company-controlled account, never a personal login. The role depends on the builder. Webflow: the Designer or Site manager role, on a paid full seat in your Workspace (or a guest invitation, which Webflow allows only to a Freelancer or Agency Workspace). Squarespace: the Administrator permission, because Squarespace lets only owners and administrators connect storage to a form block. Wix: the Website Manager role; Wix's Website Designer role cannot reach the Inbox or contacts. Delivery tests always run from the published live form, never from a duplicate or trial copy of the site: Squarespace says a duplicate is a new trial site, and its trial sites send no form email. We name the exact role and any seat or plan charge in the quote before you invite anyone; those charges are yours. You can remove our access at any time. No passwords or payment details go by ordinary email, and your authorised account holder publishes the final change.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “builder-form-submissions-not-reaching-owner” as the subject.