Standing service builder-site-forms-and-integrations-kept-working · revised 11 October 2026
Standing service
Keep your builder site's forms and integrations working, month after month
Each month we test up to three forms and three embeds or tags on your Webflow, Squarespace or Wix site, fix what has broken inside the builder, and tell you what only you can change.
This starts a conversation by email. Nothing is charged, and nothing is tested or monitored, until we have agreed scope and terms with you in writing.
The responsibility you hand over
Forms and pasted snippets break silently. A builder changes how custom code is handled, a plan or email address changes, an app updates, and nobody notices until a customer says they never heard back. The site looks fine while enquiries are lost.
Who it’s for: Owner of a small-business site on Webflow, Squarespace or Wix whose enquiries and tracking depend on a few forms and pasted snippets that nobody checks.
Usually starts when: A form quietly stopped delivering last time, an enquiry was lost, or builder changes keep breaking a widget or a tag.
The result: Each form you name delivers a labelled test submission to the right inbox every month, each named embed and tag still loads, and each month you see what was tested, what failed and how it ended.
What stays true, and what we do about it
No response-time guarantee is published for this new service. A target is agreed in writing before it starts, set to what a service at this stage can actually keep.
Hours are agreed in writing before the service starts. At launch the service is not staffed round the clock, so we do not offer round-the-clock cover.
What must remain true
- Each named form delivers a labelled test submission to its inbox and stores it
- Each named embed loads on its pages and each named tracking tag sends one page view per load
What we watch
- A labelled test submission through each named form on the published site each month, and the builder's own list of stored submissions
- A browser check of each named embed and tag on its pages each month
- Each month, the help articles and update notes the builder publishes on forms, custom code and integrations, compared with your named items; the builder gives us no advance notice of changes
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| The monthly test shows a form that did not store or deliver a submission. | We trace the failing stage and prepare the builder-side correction; once your account holder has published it where the builder needs that, we test again, or we tell you what only you can change. Priced as: Builder form delivery repair |
| A named embed or tag breaks a page or fires twice. | We find the cause, correct the placement or duplicate and show the before and after browser record. Priced as: Builder embed or tag fix |
| The builder announces a change to how forms, custom code or integrations behave. | We read the notice, check your named items against it and tell you whether anything needs attention. |
| A month ends. | We send a short written summary of what was tested, what failed and how each ended. |
We do on our own
- Send labelled test submissions from the published site and read the builder's stored submissions list
- Check the named pages in a browser
- Prepare a restore of the named forms and embeds to their last known good settings, within the agreed number of small fixes; your account holder publishes it
We ask you first
- Any change of recipient, plan, domain, billing or payment setting
- Adding or removing a tracking tag or an app
- Publishing any change that touches pages other than those named
We escalate to you when
- The cause is outside the builder, such as your mail provider rejecting its messages or a vendor outage
- A fix would need a plan upgrade or a change of recipient
- Failures pass the agreed number of fixes in a month
How you know it held. Each month you get the tests run, the result for every form and embed and what was changed, with a test log you can compare with your own inbox. A fix counts as delivered only after your account holder has published it where the builder needs that and the retest on the published site passes.
How we keep it true
This service is never finished. Each month's summary shows whether the named forms and embeds stayed working, and it continues until you end it.
Make one Webflow, Squarespace or Wix form deliver every submission to you Job Each time it fires
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.
Up to two small fixes a month between both jobs, as agreed
A small fix is one setting of the same method as the stand-alone job; a failure that needs the whole stand-alone job is quoted at that job's price.
Fix one tracking snippet or widget embed that breaks a page on your site builder Job Each time it fires
One pasted snippet or widget on a Webflow, Squarespace or Wix page loads without breaking the page, and a tracking tag fires once per page view, with any builder limit named.
Counted in the same two small fixes a month
A small fix is one tag placement of the same method as the stand-alone job; a failure that needs the whole stand-alone job is quoted at that job's price.
What is included, and what is not
- A monthly test log for each form and embed
- A fix for each failure we can fix inside the builder, with before and after evidence
- An explanation, when the cause is outside the builder, of what only you can change
Included
- A labelled test of up to three named forms on one site once each calendar month, on a day agreed in writing, checking that each is stored and delivered
- A browser check of up to three named embeds or tags on their pages once each calendar month, on the same day
- Small fixes inside the builder, up to two a month. A small fix changes one setting or one tag placement on a named form or embed, with before and after records; unused fixes do not carry over. A failure that needs the whole stand-alone repair job is quoted at that job's listed price
- A short written summary each month, and a note of any builder notices we found when we read its published help articles and update notes during the monthly check
Not included
- Redesigns, new pages or new features
- Changes to mail provider settings, domain records, plans or billing, which stay with you
- Out-of-hours cover or any guaranteed response time
- Spam and bot protection design, consent banners or privacy advice
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
For each named form, the monthly labelled test is stored by the builder and delivered to the named inbox.
Evidence: The monthly test log with times and a screenshot of each stored entry.
For each named embed and tag, a browser check shows it loads without new console errors and tags fire once per page view.
Evidence: Browser records for each named page.
Every failure in the month is listed with how it ended, and each fix has a before and after record.
Evidence: The written monthly summary compared with your own inbox and stored submissions.
Sign-off. You read each monthly summary and accept each fix. A fix counts as delivered when you accept it.
If it fails. If we cannot fix a failure, we say so, explain what we found and what it would take, and it does not count against the monthly number. If the service is not working for you, you can end it at the end of any month.
When it fits, and when we stop
It fits when
- One site on Webflow, Squarespace or Wix, with its forms using the builder's own form tool
- You can give builder access at the role named in the access section, and name an inbox for test deliveries
- A person on your side approves changes that touch recipients, plans or tags
We stop and tell you if
- Most failures come from your mail provider or another party outside the builder and cannot be changed
- Failures regularly exceed the agreed number of fixes, so we agree a different scope
- The forms are third-party embedded services, which are not covered
What could go wrong
Every fix lists the old value of each setting, so you can put it back. Ending the service leaves the site as it is, with open fixes finished or handed back.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A monthly test misses a break that happens between checks. | Monthly testing is not continuous monitoring; we say so, and you can tell us when you change anything so we test sooner. |
| Test submissions clutter your records or trigger other automations. | Tests are labelled, and we agree beforehand which connected tools could react. |
| Access to the site is wider than you intended. | We ask only for the role named in the access section; on some builders that is an administrator-level role. You create it and can remove it at any time. |
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.
Stays with a person
- You approve any change of recipient, plan, tag or app
- Your account holder publishes every change
Access we would need
- Builder access to one site at the role named in the access section, kept in place until you end the service or remove it
- A test mailbox you control
Questions
How is this different from buying one repair?
A repair is the whole job: it traces every stage, fixes the cause and hands over a test log. This service tests your named forms and embeds every month and covers small fixes of one setting each within the monthly price; a failure that needs the whole repair is quoted at the repair's listed price.
Is it continuous monitoring?
No. It is a monthly test and a review of builder notices. If you change something between tests, tell us and we test sooner.
What if the problem is my email provider?
We tell you what we found, with the delivery record, and what only you or your mail administrator can change.
Who publishes a fix?
Your account holder, wherever the builder needs a publish for a change to go live (on Webflow, changing a form's notification settings needs the site to be republished). A fix counts as delivered only after it is published and the retest on the published site passes.
Send an enquiry
Send us
- The site address, the builder and the names of the forms, embeds and tags you want kept working
- The inbox that should receive each form's messages, with the first part masked
- How often things have broken so far, as best you know
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
- The agreed number of fixes a month and who to tell when something is outside the builder
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); Webflow lets only those two roles open the custom code section. Squarespace: the Administrator permission, because only owners and administrators can connect storage to a form block or add code injection. Wix: the Website Manager role; Wix's Website Designer role cannot reach the Inbox or contacts, and Wix's pages do not say which role reaches every setting, so we confirm that in your dashboard before quoting. A standing service keeps this access in place month after month: the same role stays until you end the service or remove it. You remove it in the builder's own people or permissions settings, and our monthly tests stop from that moment. 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-site-forms-and-integrations-kept-working” as the subject.