Conditional logic is what makes a ChatWisp form feel hand-tailored to each person. Instead of every respondent seeing every question, you set rules like "only ask this if the earlier answer was a low score" or "only ask this if they chose Enterprise." The result: shorter forms, smarter conversations, higher completion, and cleaner data.
When to branch
- After any scored question — add a low-score branch ("what fell short?") and, for NPS, a promoter branch ("what would you tell a friend?").
- After a category question — ask the one follow-up that only makes sense for that segment.
- As a screener — an early question can gate the rest ("Have you used the product? No → skip the detail questions").
How conditions work
You pick a trigger question, an operator, and a value. The operators adapt to the question type:
- Scores and numbers: equals, doesn't equal, greater/less than (or equal), between.
- Dates: equals, before, after, between.
- Single choice: is / is not / is one of several.
- Multi-choice & ranking: includes any / all / none / exactly.
- Allocation: presence only — branch on whether it was answered.
- Text: contains / doesn't contain / equals / doesn't equal.
Every type also supports the simple presence checks: answered / empty / not empty.
Setting up branches
Draw a branch visually in Map view by connecting a question's branch port, or add a condition inside a question's editor in List view. ChatWisp validates your logic and warns you about broken or impossible conditions before you publish.
Keep it shallow
One level of branching is almost always right — roughly two to five branches across five to seven core questions is the sweet spot. The goal is a smarter form, not a maze.
Related
The 14 question types · Previewing, publishing & the form lifecycle