Form monitoring & delivery

Your contact form is broken and nobody has told you.

Every form service on the market tracks the enquiries that reach it. None of them can see the ones that never left the visitor's browser — the empty field the browser discards, the endpoint that stopped answering, the spam check that silently refuses real people. We check the form itself, every night, and tell you the morning it stops working.

We set it up for you and show you what your forms are really doing.

46enquiries one dental practice typed into a field that discarded them
14broken forms found across 6 client sites in a single sweep
0.66%our measured notification failure rate, every one accounted for
Nightlyevery page of every site we look after, checked while you sleep

A broken form and a quiet week look identical

That is the whole problem. The evidence of a form that has stopped working is an empty inbox, and so is the evidence of an ordinary Tuesday. Nobody investigates an empty inbox until a customer rings to ask why their message was ignored.

The field with no name

A form control with an empty name is not a broken field — the browser throws the value away before the request is sent. Nothing reaches the server, so nothing is logged, and no form service can warn you.

The endpoint that moved

The form posts into nothing. Many setups still show the success message, because it fires on the click rather than on a response. A confirmation is not proof of delivery.

The spam check that refuses people

Set too strictly, or with its script missing from the page, spam protection rejects genuine visitors. Most systems discard what they reject, so the lead and the evidence disappear together.


How it works

Point your forms at us, then stop worrying about them

1

We wire it up

WordPress, Elementor, a static export or hand-written HTML — if it can POST, it works. We do the setup and test every form on the site end to end, and fix whatever we find broken on the way through.

2

We store, then deliver

The submission is written down before anything is sent. Email, webhook, Slack and SMS each get their own delivery record, so a failure is a delayed lead rather than a lost one — and it can be retried.

3

We watch it every night

We fetch the live public page — the one your visitor is served, not the one in your editor — and confirm the form can still physically submit. If it cannot, you hear it from us first.


What you get

Broken-form detection

Nightly checks on every page: fields the browser would discard, forms pointing at dead endpoints, missing spam scripts. The failure class nobody else looks for.

A delivery record for every leg

Every email, webhook, Slack message and SMS is logged separately with its outcome. When something fails you get the reason, and the ability to resend.

Spam held, not destroyed

Suspected spam is scored and quarantined for review rather than deleted. A false positive is a lead you can still rescue instead of one you never knew about.

UK GDPR built in

Retention periods that actually delete, subject access exports, and erasure that removes the data rather than just the row. Compliance as engineering, not a checkbox.

Goes where your data goes

Webhooks, Slack, scheduled notifications, mailing lists, CSV and JSON export, and API tokens for anything else you need to wire it into.

Set up by a person

Not a signup form and a documentation link. We install it, test every form, and tell you what we found — which, so far, has never been nothing.


Where we differ

The established form backends are good at their job. The distinction is not quality, it is what is possible to see from where they sit: a service that only receives submissions cannot report on the submission that was never sent.

CapabilityTypical form backendFormHam
Stores submissionsYesYes
Delivery log and retriesYesYes
Spam filteringYesYes — held for review, never silently deleted
Detects a field the browser discardsNo — nothing arrives to inspectYes
Detects a form posting nowhereNoYes
Detects spam protection blocking real visitorsPartiallyYes
UK GDPR retention, DSAR and erasureVariesBuilt in
Someone sets it up and fixes it for youSelf-serveIncluded

Simple pricing, no free tier

£10 per site per month, or £100 a month for up to ten sites if you are an agency. Setup is £150–£250 once, per site, and includes fixing what we find.


Common questions

How is this different from Formspree, Formspark or Basin?
They handle submissions that reach them, and they do it well. None of them can see a form that stopped being able to submit, because in that case nothing arrives for them to log. We check the rendered page itself, so we catch the failure that produces no submission at all.
Do I have to use WordPress?
No. Any HTML form on any host can post to us — exported WordPress, Astro, Hugo, Eleventy or hand-written HTML. The WordPress and Elementor plugin is a convenience, not a requirement.
What happens when a notification fails?
The submission is stored before anything is sent, so it is never lost. Each delivery leg is logged separately with its outcome and reason, and can be resent once the cause is fixed.
Is my data handled under UK law?
Yes. Retention periods that actually delete, subject access exports, and erasure that removes the data rather than just the database row. UK GDPR and the Data Protection Act 2018 are treated as build requirements.
Can I take my data with me?
Always. Export any form to CSV or JSON whenever you like, and use API tokens or webhooks to push submissions wherever you need them.
Is there a free plan?
No. Setup is done by hand and the nightly monitoring runs per site whether or not you are looking, so a free tier would be funded by the customers who pay. There is a 14-day trial instead.

Find out what your forms are actually doing

Tell us your site and we will check every form on it. If they all work, we will say so and you have lost nothing.

Talk to us