A qualification form asks the questions an owner/admin needs before deciding whether to speak with a candidate. Only the school's owner and admins can read, compose, publish, and manage forms. A closer or setter cannot use the form workshop or see its responses. The respondent needs no school account: they open a public address tied to the school and the form.
For Maya Chen, create a short Agentic AI Developer interest questionnaire. Ask what she wants to build, how much experience she has, and whether she wants a conversation. The same form can be attached to target programs or cohorts, but zero attachments is valid. A form response is evidence for triage, not an enrollment or payment.
Open CRM → Forms and choose New form. Enter the Form title and an optional Description. The form begins as Draft, with no public address. Use Edit the form later if its title, description or attachments need changing.
In Composition, use Add a question for each prompt. Give each a stable Question key, the Question asked, an Answer type, and whether an answer is required. Choice questions need offered options. Reorder the questions, then inspect Preview; its Send my answers button is inactive because preview records nothing. A draft can be saved incomplete, but an empty or invalid choice list cannot serve a useful respondent.
Choose Publish when the draft is ready. The workshop shows Version 1, its Public address, and Open to responses. Use Copy the public address and send the complete link to Maya. The address follows /en/f/{school}/{form} on your site; the school and published version are resolved from that link, not from a value Maya chooses in a request.
| Workshop state | What Maya receives at the public address | Owner/admin action |
|---|---|---|
| Draft, never published | No questionnaire or shareable public address | Finish questions and Publish |
| Live, version published | The current frozen published version | Share the address; use View responses after submissions |
| Draft changed after publication | Still the earlier published version | Check changes, then Publish the changes to create the next version |
| Closed to responses | The address exists but serves no questionnaire | Turn Open to responses on when ready |
| Unpublished | The address stops answering; its version history remains | Publishing again makes a new version, rather than restoring the old one |
Editing a question or the form title after publication changes the draft only. Maya still sees the published version until you choose Publish the changes. Her submitted answers remain readable with the wording and answer types she saw, even after later publications. The public address does not change when you rename the form after its first publication.
Warning
To pause submissions temporarily, switch off Open to responses. Unpublish also stops the address, but publishing later creates another version. Neither action erases earlier responses. If Maya reports an unavailable link, check the form's Live/Closed state and the exact school/form address before sending a new one.
Each form has a Theme, chosen at the top of the Preview tab:
| Theme | What the candidate sees |
|---|---|
| SaaS (default) | All the questions on one page, then Send my answers |
| Typeform | A dark welcome screen with Start, then the name, the email and one question per screen, with a progress bar and previous/next arrows |
The preview switches as soon as you pick a theme, before anything is saved. Choose Save theme to keep it on the draft. The theme a candidate sees is the one frozen in the published version: after saving a new theme, choose Publish the changes to apply it. Changing the theme never changes the questions or the answers already received.
In the Typeform presentation, Maya can answer with the keyboard: A, B, C… pick a choice, Enter confirms a step (in a long answer, Enter adds a new line and ⌘/Ctrl + Enter confirms), and the arrow keys move to the previous or next question. Her application is only sent when she presses Send my application — Enter in a field never sends it. If the server refuses an answer, she is taken back to that question with the reason, and her other answers are kept.
Continue with application triage once Maya submits. Form composition, theme, publication, and response reading are school screen flows; there is no public /api/v1/forms or application-triage endpoint today.
In form creation or the workshop Preview settings, enable Save incomplete responses, then publish. The default mode saves only the final submission. Progressive mode saves after a valid name and email: classic forms save after a pause, Typeform saves on validated steps. The status says whether changes are saved; invalid edited values remain unsaved. Candidates can return in the same browser; another browser or email lookup cannot recover their answers. Publishing new questions does not change an already-started response. Closing or unpublishing blocks saving and recovery immediately. Descriptions preserve plain-text line breaks in both themes.
Owners/admins can also manage forms through the API or MCP. Save the draft definition/settings first, then explicitly publish. Never enable AI without consent.
Name and email are fixed required identity fields shown before custom questions in Composition and Preview. They are included automatically: do not recreate them. They cannot be deleted or reordered, and they are excluded from AI qualification. Custom criteria remain attached to stable question keys when questions move.
Use Edit name and email labels in Composition to change their labels and descriptions/help. Their required status and fixed identity binding remain unchanged. Restore localized defaults with the editor reset button; publish to apply edits. In Preview choose Typeform (light) for a light version of the same one-question-at-a-time experience; Typeform keeps its dark appearance.