Customers
Forms
Enquiries from your website arriving as contacts, with the consent people actually gave recorded against them.
A form is a page you build here and embed on your own website. What somebody submits becomes a contact, and whatever they ticked becomes a consent record — the same record the consent rules read before anything is ever sent to them.
What happens to a submission
- 1
The submission is stored whole
Separately from the contact it produced, and always — including when it is held as spam and including when it matched somebody who already exists. What was typed and when is the record that settles a dispute about whether somebody opted in, and it has to survive the contact being edited, merged or erased.
- 2
A contact is created or matched
Matched on the email address, including one sitting on a merged-away record. An existing contact is filled in where fields are blank and never overwritten — somebody curated that record, and a form answer is not more authoritative than a person.
- 3
Consent is recorded either way
Ticked or not. An unticked box is a recorded refusal, not an absence, because *they said no* and *we never asked* are different facts and only one of them means you may ask again.
Marketing consent cannot be required
The tick box for it is disabled, not merely refused when you save. Consent given as the price of submitting a form is not freely given and does not count — and a record of it is worse than no record, because it looks like evidence and is not.
The wording is the evidence
What you type as the consent wording is stored word for word on every consent record the form produces, alongside how it was obtained, the page it came from and the submitter's address. The answer alone is not a defence; what matters is what was in front of them when they agreed.
Editing the form afterwards therefore cannot change what somebody agreed to. Their record keeps the wording they were shown.
Spam
A submission caught by the automated checks is stored and stops there — no contact is created. The visitor is told exactly what everybody is told, because revealing which signal caught it is how the next attempt stops tripping it.
Held submissions are shown to you, with the reason. That one is the submission somebody comes looking for when a client says they filled the form in and never heard back, and it is the only way a false positive is ever found.
Embedding
The snippet is an iframe, not a script tag. A script would ask you to run our code on your own site with access to everything on the page; an iframe can only draw inside its own box. An optional line of script lets the frame size itself, and the form works without it.
Opening a service desk ticket
A form can also raise a ticket, so a *Report a problem* form lands in the queue with a clock on it rather than only on a timeline. Per form, and off by default: most forms are not support requests, and a newsletter sign-up raising a ticket would put a response-time promise on somebody who asked for a PDF.
A held spam submission never raises one
That would put an SLA clock on a robot and fill the queue with exactly what the spam check exists to keep out. And a form that opens a ticket is refused unless it collects an email address — a ticket is answered by replying, and one whose requester left only a mobile number is one nobody can answer.
It works without JavaScript
The form submits through an ordinary POST if scripts are blocked. A contact form that silently does nothing loses exactly the enquiries you never hear about.
What it does not do
- There is no conditional logic — no showing one question because of the answer to another.
- There is no file upload.
- There is no styling: the form inherits nothing from your site and imposes nothing on it.
- A submission does not raise a task or notify anybody. It appears against the contact.