Skip to content

Contact and intake forms

Contact, enquiry, waitlist and RSVP forms are a platform feature: spam protection, validation, an email to you and an optional auto-reply, with nothing to build.

Last updated September 17, 2026

On this page

A contact form, an enquiry form, a waitlist, an RSVP: any form a visitor fills in without signing in is an intake form. The builder does not hand-build these. It registers the form with the platform, which handles the part that matters: accepting a submission from a stranger safely.

How a form works

Submissions land in a table

The builder creates a table for them, readable only by admins, so nobody can browse other people's messages.

The form is registered

The registration permits exactly one thing: creating a row in that table. Nothing else opens up.

A visitor submits

The fields are validated against the table (required fields, types, allowed values) and the visitor sees any mistake next to the right box.

You hear about it

You get an email for each submission. Optionally the visitor gets an automatic reply.

Spam

Every form carries an invisible field that real people never fill in and bots do. Submissions that trip it are quietly accepted and dropped, so the bot learns nothing. Volume is also kept within sensible bounds without you doing anything.

Asking for one

Add a contact form to the footer with name, email and message, and email me when someone sends one. To add an auto-reply: send the person a thank-you email that says we reply within one business day.

Where submissions go

Open the form's table under Database. Submissions are ordinary rows, so you can search them, mark them handled with a field the builder adds for you, or feed them to an automation ("every Monday, email me the week's enquiries").

Forms need no accounts. This is the one write a visitor can make without signing in. Everything else a visitor changes in your app needs an account, which is what keeps the data honest.
Was this page helpful?