Chat Form
Forms interrogate. Conversations listen.
A chat form asks one thing, waits, and responds to what it actually heard — including “why do you need that?” and “sorry, I meant Thursday”.
What is a chat form?
A chat form is a form presented as a conversation: one question at a time, in a messaging interface. YourForm chat forms run on a language model, so respondents can correct earlier answers in plain language, ask why a field is needed, and answer two questions in one sentence.
The problem
Why do people abandon forms they meant to finish?
A form is a list of demands from a stranger. Twenty-three fields, no explanation of why any of them are needed, no way to ask. The only feedback loop is turning red after you get something wrong.
Watch someone fill one in. They scroll to the bottom first to see how bad it is. They skip the optional questions. When they mistype an email four fields back, they scroll up, hunt for it, fix it, and lose their place. Each of these is a moment where leaving becomes the easier option.
The information you are asking for has not changed. What changed is that you now ask for all of it at once, in silence, with no way to negotiate.
Nobody abandons a conversation at question four. They abandon a wall of twenty-three fields at question zero.
The difference
Is this just a form with speech bubbles?
Most “conversational” builders are a normal form wearing a chat skin: the bubbles are cosmetic, the questions are a fixed queue, and typing anything unexpected gets you an error. The test is what happens when a respondent goes off script.
| Chat-styled form | YourForm Chat Form | |
|---|---|---|
| Fixing an earlier answer | Start over, or scroll back and hunt for the field | “Actually my name is Namo” updates that field and continues |
| “Why do you need this?” | Unhandled — treated as the answer to the question | Answered in one short line, then the question is asked again |
| Two answers in one message | The whole sentence is stored in one field | Split across the fields they belong to |
| Question order | Fixed queue regardless of what was said | Skips what has already been answered in passing |
| Waiting | Spinner until the whole reply is ready | The reply streams as it is written, so the pause is filled |
How it works
How a chat form works
- 1
You write questions, not scripts
The builder is the same one every other format uses — a list of questions with types and validation. There is no dialogue tree to draw and no intents to train.
- 2
The model runs the conversation
Gemini 2.5 Flash Lite handles phrasing, extraction and follow-ups against your question list. It cannot invent questions you did not write; the schema is built from your form.
- 3
Answers are extracted as they arrive
Replies stream so the first words appear immediately, and answers are matched to fields while the sentence is still being read.
- 4
It confirms before it submits
The respondent sees everything captured and can change any of it in plain language before the row is written.
Capabilities
What you get
Corrections in plain language
No edit icons, no going back. The respondent says what they meant and the right field changes — the same way they would correct a person.
A reason for every awkward field
Asked why you need a phone number, the form answers in one line rather than stonewalling. Hesitation is where forms lose people.
Quick replies where they help
Multiple choice renders as tappable chips instead of asking someone to type “Medium”. Conversation is the default, not a purity test.
Your Google Sheet is the database
Answers land in a sheet you own, in real time. There is no separate dashboard holding your respondents’ data hostage, no export button to remember, and nothing to migrate if you ever leave.
Conditional logic, on the free plan
Show a question only when an earlier answer calls for it. Most builders put branching behind the paid tier; here it is included from the first form you make.
Change format without rebuilding
Questions, logic and responses are stored independently of how the form looks. Pick a different format from the sidebar and the same form is re-rendered — no re-typing, no lost answers.
Honest fit
Is a chat form right for what you are building?
Every format is wrong for something. Knowing which one you are in saves more time than any feature list, so here is where this one wins and where it does not.
Reach for it when
- Lead qualification, where the next question depends on the last answer
- Support intake, where people describe problems in their own words
- Onboarding flows that would otherwise be a twenty-field wall
- Audiences who live in messaging apps and find forms alien
- Any form where you keep getting useless one-word answers
Pick another format when
- A three-field newsletter signup — a conversation is slower than a box
- Forms people need to scan in full before answering anything
- Precise tabular entry, like twelve monthly figures in a row
- Situations where an AI-written sentence would be a compliance problem
Questions
Chat Form questions, answered
- What is a conversational form?
- A conversational form asks one question at a time in a chat interface and responds to what the person actually writes. Unlike a form with chat styling, it handles corrections, clarifying questions, and answers that arrive out of order.
- Do conversational forms get better completion rates?
- They tend to help most where a traditional form is failing for a specific reason: too many fields visible at once, questions that need explaining, or answers that are naturally written as sentences. For a short form with obvious fields, a plain form is usually faster and you should use one.
- Can the AI ask questions I did not write?
- No. The response schema is built from your question list, so the model can only fill fields you defined. It chooses phrasing and follow-ups; it does not invent new fields or store answers you never asked for.
- What happens if someone answers two questions at once?
- Both answers are extracted and written to their own fields, and the already-answered question is skipped rather than asked again. This is the single most common reason chat-styled forms feel broken, and it is handled here.
- Is it slow to wait for an AI reply?
- Replies stream as they are generated, so the first words appear almost immediately rather than after a spinner. The response schema is ordered so the conversational reply is produced before the bookkeeping fields.
- Where are chat form answers stored?
- In your connected Google Sheet, one row per submission, one column per question — exactly the same shape as every other format. The conversation is the interface, not the storage format.
The other four
The same questions, published four other ways
Format is a setting, not a rebuild. Your questions, logic and collected responses stay exactly where they are when you switch.
Build one and send it to five people.
That is usually enough to know whether a chat form suits your audience. Two forms and 200 responses a month are free, and responses go to your own Google Sheet from the first one.