Form design standards
- Collect only required fields to reduce abandonment in conversational forms.
- Use explicit labels, examples, and validation hints for each input field.
- Split long forms into staged steps with progress context.
Build
Forms and Data Capture Guide
Design reliable form nodes, validation logic, and variable mapping for clean downstream automation.
Audience: Bot builders and operations analystsRead Time: 8 minUpdated: May 2026
Validation and routing
- Enforce type validation for email, phone, dates, and identifiers.
- Add retry prompts with bounded attempts before escalation.
- Route incomplete or invalid data to remediation branches.
Variable mapping and usage
- Use stable variable naming conventions across all flows.
- Map outputs to API payload fields with null-safe defaults.
- Sanitize and redact sensitive fields before analytics export.
Operational Checklist
- OKEvery field has clear validation rules.
- OKRetry and fallback behavior is configured.
- OKVariable names follow a documented convention.
- OKSensitive fields are redacted where required.
Related Guides
Next Action
Apply this guide in your workspace and keep notes for your team in one shared SOP so onboarding and support remain consistent.