How it works
A form backend takes the form, so your site does not have to.
A static site, a theme or a page builder can show a form but cannot process one. A form backend receives the submission, checks it and passes it on.
Three steps, as planned
Step 1: Add your site
Tell Prosphere which domain you run. Each site gets its own address for forms.
Step 2: Point your form
Set the form's action to that address. Any site that can send a form can use it.
Step 3: Read one inbox
Submissions from every site appear together, each marked with its site.
What happens to a submission
It is checked
A hidden honeypot field, a timing check and a bot test catch most automated spam before it reaches you.
It is labelled
Each message records the site and page it came from, so you do not guess which website a question is about.
It is delivered
You get it in the inbox, and optionally by email or by webhook to another tool.
Ways to handle a contact form
General approaches, not a ranking of named products.
| Question | A mailto link | A plugin per site | A shared form backend |
|---|---|---|---|
| Works on a static site | Yes | No | Yes |
| One inbox across sites | No | No | Yes |
| Spam filtering | No | Depends on the plugin | Yes |
| You maintain it per site | No | Yes | No |
A general comparison of approaches. The shared form backend column describes what Prosphere is being built to be.