-
How to build one.
Five steps. The two everybody skips are the last two.
Decide what the reply must contain.
Cut every field you can.
Design the form on the canvas.
Publish and send yourself a test.
Check the inbox and spam folder.
-
Where the answers go, and what is not documented
The documented promise is short. Forms collect information from visitors, including subscription and contact details, and the answers reach your inbox. For a marketing site that is usually the whole requirement, and it is worth knowing that it really is the whole requirement before you plan anything more elaborate on top of it.
What is not published anywhere is the detail underneath. Which field types you can place. Whether anything checks what was typed before it is sent, or whether one question can depend on the answer to another. Whether submissions are filtered for spam, whether a visitor can attach a file, whether the destination address can be changed or pointed at more than one person, whether you can download a record of past submissions, and how long they are kept. We are not going to guess at any of it.
So place a form in the app and read what it actually offers before you build a process on top of it. The app is the authoritative source and this page is not. If what you need depends on one of those details — a hiring form that wants a CV attached, a support form that has to land in a shared queue — check it there first and design around what you actually find.
Then submit a real test from the published page, from a device that is not the one you built it on, and look in the spam folder as well as the inbox. A form that silently drops enquiries looks exactly like a form nobody is filling in.