Contact form backend

Contact form backend for websites that already have a form UI

If the website already has a contact form design, the missing piece is not a form builder. It is the backend that receives the submission, blocks spam, stores the lead, and routes it to the right team.

Keep your existing form design Searchable inbox and exports Team notifications and integrations

Try without signup Read the docs

§ 01 · Overview What you get

Use the form you already have

Formserve is built for forms that already exist in HTML, frameworks, site builders, or AI-generated projects.

Capture real business workflows

Store submissions, notify the owner, and route leads to downstream tools without rebuilding the frontend.

Support technical and non-technical stakeholders

Developers keep control over endpoint settings while business owners can get a focused inbox view.

§ 02 · Context A contact form backend should solve the whole path after submit

A working contact form is more than a POST target. It should catch spam, preserve the lead, notify the right people, and make follow-up operationally clear.

Formserve handles that full path while staying simple on the frontend. The website keeps its own form markup and submits directly to Formserve.

This is especially useful for small business sites, agency client websites, and static marketing pages where speed matters more than building custom backend infrastructure.

§ 03 · Context What you get after launch

A central inbox for every submission.

Delivery visibility across email, webhooks, and integrations.

Optional business-owner access without exposing technical configuration or billing controls.

§ 04 · Context Backend, not builder — why that distinction matters

Many form tools try to own the whole form, including the UI. That means learning a drag-and-drop builder, accepting their markup, and often shipping a branded embed or iframe that does not match your site. If you already have a contact form you like, that is a step backwards.

Formserve is deliberately a backend, not a builder. You keep the exact HTML and CSS you already have. Only the submission behaviour changes, so the form posts to your endpoint instead of a route you would otherwise have to build and host.

That keeps the product simple to describe and simple to adopt: bring your own form, get a real backend behind it. It also means there is nothing to migrate if you redesign the form later — as long as the fields still POST, the same endpoint keeps working.

§ 05 · Setup How to connect it

Create an endpoint for the contact form.

Replace the form action with the endpoint URL and keep method POST.

Add the _honeypot field, allowed domains, and notification recipients.

Submit from the live site and confirm the lead lands in the inbox.

§ 06 · Example Keep the form simple

contact-form-backend.html — minimal

<form action="https://formserve.io/f/YOUR_ENDPOINT_KEY" method="POST">
  <input type="text" name="_honeypot" tabindex="-1" autocomplete="off" style="position:absolute;left:-9999px" />
  <input type="text" name="name" required />
  <input type="email" name="email" required />
  <textarea name="message" required></textarea>
  <button type="submit">Send</button>
</form>

§ 07 · FAQ Common questions

Is Formserve a contact form builder?

No. Formserve is the backend and inbox layer for contact forms already on your site. You keep your own HTML and CSS; only the submission behaviour changes.

Can I use the same backend for more than one form?

You can, but usually each business workflow should get its own endpoint so submissions, notifications, spam rules, and routing stay clear and separately manageable.

Do I have to change my form's HTML or design?

No. In most cases you only change the form action to your endpoint URL, keep method POST, and add the hidden _honeypot field. The layout, styling, and fields stay exactly as they are.

How does Formserve handle spam on a contact form?

With invisible methods first — a hidden honeypot field, rate limiting, allowed domains, and keyword and email blocklists — scored on a 0 to 100 spam scale. There is no CAPTCHA by default, so conversion is not affected.

Can non-technical team members see the submissions?

Yes. A business owner or client can get a focused inbox view of incoming leads without access to endpoint configuration, integrations, or billing, which the developer continues to manage.