Custom Question input types
Custom Questions support text, select (single and multi), numeric, date, file upload, and others depending on configuration. Pick the input that gives you the right shape of data — a multi-select is not a free-text field.
In short: Pick the input type that matches the answer shape. Single-select for “one of these,” multi-select for “any of these,” text for open-ended, numeric for numbers, file for documents.
Available input types
| Type | What it captures | Best for |
|---|---|---|
| Text | Free-form string | Names, descriptions, references |
| Long text | Multi-line free-form string | Comments, narratives |
| Single-select (dropdown or radio) | One value from a fixed list | “Which carrier are you currently with?” |
| Multi-select (checkboxes) | Zero or more values from a fixed list | “Which discounts apply?” |
| Numeric | A number (integer or decimal) | Years, counts, dollar amounts |
| Date | A calendar date | Effective dates, birthdates, milestones |
| Boolean (yes/no) | True or false | Eligibility flags, simple toggles |
| File upload | A document or image | Photos, certifications, statements |
The exact set may vary slightly by configuration. Where supported, you can group multiple inputs under a single Custom Question — for example, a “Vehicle modifications” question with one multi-select for the type of modification and a long-text input for description.
Choosing the right type
A few rules of thumb:
- Use a select instead of text whenever the answer is one of a known list. Selects produce clean, queryable data; text answers vary in spelling and capitalization.
- Use multi-select instead of multiple yes/no questions when the options are mutually compatible. “Which discounts apply: [auto-pay] [bundling] [loyalty]” is one multi-select, not three booleans.
- Use numeric for anything you’d want to sum or compare. Text “5 years” can’t be aggregated; numeric
5can. - Use date for actual dates. Don’t capture a date as text.
- Use file upload sparingly. Each file consumes storage; ask whether you actually need the document or just need confirmation it exists.
Validation
Per input, you can typically configure:
- Required — must be answered to progress
- Min/max for numeric and date inputs
- Pattern matching for text inputs (where supported)
- File type/size restrictions for file inputs (defaults are SALT’s standard limits)
Validation runs when the consumer tries to advance past the step. Failed validation shows an error and keeps them on the step.
Modifiers (visibility logic)
Inputs can be hidden or shown based on other answers. Examples:
- Show “type of pet” only if “Do you have pets?” = yes
- Show “additional drivers” only if “How many drivers?” > 1
- Hide “carrier name” if “currently insured” = no
Configure modifiers on the input. SALT runs the logic in real time as the consumer answers — they only see relevant inputs.
Common questions
Can a single Custom Question have inputs of different types? Yes. A Custom Question is a container; the inputs inside it can each be a different type.
Can I configure a select with a long list (50+ options)? Technically yes, but UX-wise you’ll get drop-off. For long lists, consider an autocomplete or splitting the question into a hierarchy (“Region” → “State within region”).
Do file upload inputs follow the same size/type rules as Form-level document uploads? Yes — the same standard limits apply (PDF, JPEG, PNG, GIF, WEBP; up to 25 MB).
How do I change the type of an existing input? Edits to a published Custom Question apply to new answers only. For a structural change like input type, the cleanest path is to publish a new Custom Question and archive the old.