Field types
Intake Bots use conversational fields to collect data from respondents. Each field type includes built-in validation and can be enhanced with AI intelligence.
Intake Bot field types
Section titled “Intake Bot field types”| Field type | What it collects | Notes |
|---|---|---|
| Text | Short text answer | Min/max length, regex validation supported |
| Email address | Format validated automatically | |
| Phone | Phone number | Format validated automatically |
| URL | Website link | URL format validated |
| Textarea | Long text answer | Min/max length |
| Number | Numeric value | Min/max value, decimal precision configurable |
| Date | Date (and optional time) | Range limits supported; typed input (“next Friday”) parsed by AI |
| Boolean | Yes/No answer | Displayed as two options |
| Select | Single choice from options | Options defined by the builder |
| Multi-select | Multiple choices from options | Options defined by the builder |
| File | Document, image, or PDF | File type restrictions, size limits, AI Document Extraction supported |
| Geolocation | GPS coordinates | Browser Geolocation API; static map preview shown |
| Repeating Group | Multiple instances of fields | Use for collecting multiple items (children, addresses, products) |
| Hidden | Silent value storage | Value set via URL parameter, embed attribute, or static default; also used for calculated totals |
| Record Lookup | Search and pick an existing Record row | Can be scoped with row filters and carry extra columns from the matched row |
Calculated (hidden number) fields
Section titled “Calculated (hidden number) fields”A hidden number field can total a group of other fields tagged with a shared score group. Choose the aggregation: sum, average, min, max, or count.
- Unanswered items in the group are excluded from the total and flagged, so routing rules can require a complete score before acting on it.
- Optional bands attach a label such as “low” or “high” to ranges of the total.
- A content block can interpolate the running total and its band mid-conversation with
{{field_name}}and{{field_name.band}}. That display is not saved. - The server recomputes the canonical total at submit, on web and WhatsApp alike.
Record Lookup: row filters and carry
Section titled “Record Lookup: row filters and carry”Record Lookup fields support two additional behaviors beyond the basic search-and-pick:
- Row filters scope a lookup to the rows matching a column value (for example,
question_id equals P1). This lets one shared Record Type back many different lookup questions instead of requiring one table per question. A label that repeats across the table stays unambiguous because it’s resolved within its own scope. - Carry values let a lookup copy other columns from the matched row onto namespaced submission paths (for example, a numeric score behind a Likert-scale label). The stored answer itself stays the human-readable label; carry values resolve server-side and write nothing if a label matches more than one row.
AI mode compatibility
Section titled “AI mode compatibility”AI Field Intelligence can be configured per field to change how the Intake Bot interacts with the respondent.
- Value Extraction: The AI pulls the specific value from a conversational response. Works on text, email, phone, URL, textarea, and number fields.
- Socratic Negotiation: The AI asks follow-up questions to clarify or verify the answer. Works on textarea, text, and number fields.
- Strict Validation: The AI ensures the answer meets specific criteria before proceeding. Works on any field.
- Document Extraction: The AI reads uploaded files to pre-fill subsequent questions. Applies to file fields.
Voice input support
Section titled “Voice input support”Respondents can use voice to fill out fields. Two modes are available:
- Polish mode (0.25 credits): Transcribes and cleans up spoken text. Available for text and textarea fields.
- Extraction mode (1 credit): Transcribes and extracts structured data. Available for email, phone, URL, number, date, boolean, select, and multi-select fields.
Privacy and security
Section titled “Privacy and security”On Business and Enterprise plans, you can apply additional protection to sensitive fields:
- Private: Excludes the field value from all AI processing. The data is stored separately.
- Encrypted: Stores the value with at-rest encryption using Supabase Vault.
Record field types
Section titled “Record field types”Records store the structured data generated by submissions. You can also define custom fields for Record Types.
| Field type | Use case |
|---|---|
| Text | Names, titles, short descriptions |
| Long text | Notes, detailed descriptions |
| Number | Quantities, prices, scores |
| Date | Deadlines, start dates, milestones |
| Select | Single choice from predefined options |
| Multi-select | Multiple choices |
| Reference | Link to another Record |