Structured form fields

Where to edit

In the dynamic builder, open the structured form list. Add a row, set the label participants will hear/see, then open field settings. Settings have three tabs: Field settings, When to ask, and Follow up details.

Field types

• Text — free text (short and long are the same type).
• Single choice / Multiple choice — chips the participant can tap; add an “Other” option when the answer space is wide.
• Rating — choose scale 1–5 or 1–10 in field settings.
• Yes / No, Number, Date — structured capture for filters and charts.
• File upload — CV, screenshot, invoice photo; optional MIME accept filter.

How the agent uses fields

Required fields are collected in organizer order before exploratory themes open. The agent asks one topic per turn and can render selectable UI (chips, rating buttons) instead of only free text. Captured values appear in Form statistics and session detail.

When to ask (timing)

The When to ask tab controls whether and when this field is shown — before the agent asks it live.

• Always — ask this field in the normal blueprint order (default).
• Tell agent when to ask — write instructions (e.g. “only after they mention pricing”). The agent waits for that theme in dialogue.
• Conditional logic — show this field only if earlier fields meet rules (equals, not equals, contains, empty / not empty). Conditions can only reference prior rows.

Use Always for email, NPS, or must-have slots. Use Agent timing for soft thematic gates. Use Conditional when a follow-up field depends on a previous choice (e.g. ask “why low?” only if rating ≤ 2).

Follow up details (depth after the answer)

The Follow up details tab controls how deeply the agent probes after this field is answered — separate from global session shape.

• None — capture the value and move on; no extra probes on this slot.
• If short answer — one follow-up only when the reply is vague or too short.
• 1 follow-up — always ask one clarifying question after this answer.
• 2–3 follow-ups — deeper thread on this topic before advancing.

Guidelines for follow-ups (optional text) tell the agent what to dig into — e.g. “If they mention competitor X, ask which feature they miss.” Guidelines apply when depth is not None.

When to ask vs follow-up vs session shape

• When to ask — whether/when the field appears at all.
• Follow-up details — how deep to go after that field’s answer.
• Session shape (objectives) — overall pacing style for the whole interview.

Draft vs published

Builder changes stay in draft until you publish. Live participants see the published blueprint. New fields apply to new sessions; completed sessions keep their original captures.

Tips

• Prefer 3–7 chartable fields so the chat does not feel like a form.
• Use clear labels — they show in Form statistics and exports.
• Put must-have fields early with When to ask = Always.
• On rating or NPS, set Follow-up to at least “If short answer” or “1 follow-up” for detractors.
• Conditional When to ask needs at least one prior field to reference.