---
title: The 14 question types
description: Every ChatWisp question type, when to use it, and what makes it unique — a reference for collecting rich, clean, chartable data.
canonical: https://chatwisp.ai/knowledge-base/building-forms/question-types
updated: 2026-08-19
---

# The 14 question types

# The 14 question types

ChatWisp offers 14 question types, each with a purpose-built control. The golden rule: **never default everything to a text box.** Because the AI harvests stories by *following up* on structured answers, you get the richest data by choosing the right type and letting the conversation capture the narrative around it.

## 1. Short text
For short labels and identifiers — names, job titles, a city, one-liners. Example: "What is your role on the team?"

## 2. Long text
For stories and open-ended detail — the "why," a memory, detailed feedback. Use sparingly (about one in four questions at most) and always pair it with a **[probing](/knowledge-base/ai-interviewer/conversation-style-probing) intent**. Example: "Tell me about the last time our product saved your day."

## 3. Single select (choose one)
For mutually exclusive categories — role, plan, segment, yes/no. The best anchor for branching. Up to about 10 choices (12 maximum), each can carry an **image** for visual cards. Example: "Which best describes your team?"

## 4. Multi select (choose any)
For non-exclusive sets — "select all that apply." 2–12 choices, images supported. Example: "Which channels did you hear about us through?"

## 5. Rating (stars)
For a quick satisfaction or quality pulse on one specific thing. Typically 1–5 stars. Add a probing intent like "on a low score, find the exact step that felt rough." Example: "How would you rate the onboarding experience?"

## 6. NPS (Net Promoter Score)
*The* loyalty question — "how likely are you to recommend us?" Scored [0–10](/blog/nps-follow-up-questions), shown with a dedicated gauge and Detractor / Passive / Promoter bands. Always pair with follow-ups, and use at most one per form. Example: "How likely are you to recommend ChatWisp to a colleague, from 0 to 10?"

## 7. Number
For countable quantities — team size, frequency, age, budget. Set an optional minimum and maximum, and branch on thresholds. Example: "How many people are on your team?"

## 8. Date
For calendar moments — deadlines, start dates. A date picker appears, and spoken dates ("next Tuesday") are understood. Example: "When does your current contract end?"

## 9. Email
For contact capture. **Always typed:** even in a voice form, respondents type their email into a proper field, so the address is captured correctly. Best placed last and kept optional. Example: "What is the best email to reach you if we follow up?"

## 10. Phone
For callbacks and SMS. Like email, the number is **always typed**, so digits are never lost. Only ask with a clear reason. Example: "If you would like a callback, what number should we use?"

## 11. Scale (slider)
For intensity, effort, confidence, or percentages — finer than five stars. Label both ends. Choose a visual style: **classic**, **gradient**, or **notched**. Example: "How much effort did it take to get set up?" (0 = Effortless, 10 = Exhausting).

## 12. Likert (agreement)
For agreement with a **statement** on a Strongly Disagree to Strongly Agree scale. Phrase it as a statement, not a question. Example: "The onboarding emails told me exactly what to do next."

## 13. Ranking
For relative priorities — "put these in order." Forces trade-offs that multi-select hides; results show as a medal podium. Use 3–7 items. Example: "Rank what matters most when you choose a vendor."

## 14. Allocation (distribute points)
For weighted trade-offs — "split 100 points across these." Where ranking tells you *order*, allocation tells you *by how much*. 2–6 items, default total 100. Example: "Split 100 points across what we should build next."

## A note on images

Option images and Classic-form cover images are something **you** add yourself in the editor. When Wispy or the setup wizard generates a form, it deliberately will not insert images — keeping the structure clean and leaving the visuals to you.

## Related

[Conditional logic & branching](/knowledge-base/building-forms/conditional-logic) · [The form builder: the three workspaces](/knowledge-base/building-forms/the-form-builder)