Structured form fields
Structured fields (the blueprint) let the agent capture comparable answers — scales, choices, short text — while keeping the conversation natural. You define them in the builder; the agent weaves them into dialogue.
When you should add structured fields
- You need numbers you can chart or export — NPS, satisfaction, feature priority, segment tags.
- Multiple stakeholders will compare answers across sessions or time ranges.
- You want Form statistics in analysis alongside qualitative notes.
- Compliance or reporting requires specific data points every time.
When to skip or keep it minimal
- Purely exploratory discovery with a small sample — rich notes may be enough.
- You only need themes and quotes, not aggregate counts.
- Too many fields make the chat feel like a form; prefer 3–7 chartable fields per study.
How the agent uses them
Each field has a type (text, single choice, scale, etc.) and a prompt. The agent maps them to natural questions and shows UI widgets when explicit input is needed. Values save on the session and roll up in analysis.
Draft vs. published
Changes in the builder stay in draft until you approve and publish. Live participants always see the published blueprint. If you change fields after launch, use republish carefully — new fields only apply to new sessions.
Tips
- Use clear field labels — they appear in Form statistics and exports.
- Prefer choice and scale types when you want charts; free text for open capture.
- Align field ids with your reporting vocabulary early to avoid rework.