Skip to content

Form · reads submission

Intake form

Collect structured input.

Fields to fill, that write straight into the data.

Four questions. Each one is an email that no longer has to be sent.

What are you making?

Packaging for a tea rangeLong text

Budget range

€2,000–5,000Choice

Needed by

30 NovDate

Existing brand?

Yes, needs refreshYes / No

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

The shortest form that avoids a second round trip, which is the only sensible design target.

Every field is something you would otherwise have to email back about.

Answers arrive attached to the enquiry rather than in an inbox.

How it works

  1. 1

    Fields are chosen by asking which email you would otherwise have to send.

  2. 2

    The form is published and answers arrive attached to the enquiry rather than in an inbox.

  3. 3

    Required is used sparingly, because every required field costs completions.

  4. 4

    The last answer is visible, which is how you notice a question people are misreading.

Best for

Intake, applications, requests.

Not the right choice for

Anything a conversation collects better — which, here, is a lot.

What a row holds

Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.

FieldTypeFilled from
FieldrequiredtextThe question, phrased as it will be read by somebody who knows nothing.
TyperequiredtextWhat kind of answer — long text, choice, date, yes/no.
RequiredrequiredchoiceYes or No. Every required field is a reason somebody abandons the form.
Last answertextWhat the most recent submission said, so the form can be judged by its output.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

  • No conditional logic or branching.
  • No file uploads beyond what the destination supports.
  • No spam protection beyond what the platform provides.
  • Answers are per submission and are not aggregated; that is Surveys.

Before it works

What you have to provide, if anything.

  • Write fewer fields than you want. Four is usually enough and six is usually too many.
  • Pair with Contacts so a submission becomes a person rather than a message.

In practice

A studio whose every new enquiry started with three clarifying emails.

Ask what they are making, the budget range, when they need it and whether there is an existing brand.
What was said to the agent

What the agent built

A four-field intake form, required where it mattered.

What changed

The three clarifying emails became zero. Quotes went out the same day rather than the same week.

Questions

What data does the Intake form page use?

It reads submission records the agent has collected. Collect structured input. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a form the wrong choice?

Anything a conversation collects better — which, here, is a lot. It is best for: intake, applications, requests.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.

Ask for it in a sentence

You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.

Build your agent free

Agents

More

👤
Profile
FAQ