Picture this: a real estate agency asks "What type of property are you looking for?" — and regardless of the answer, new build or resale, serves the same next question. Nonsense. Someone shopping for a new build and someone on the resale market are different people with different needs.
Branch logic solves that: the quiz shows different questions to different people based on their answers. Result — higher engagement, sharper lead qualification, and a personalized experience for every visitor.
What branching in a quiz is
Branch logic (conditional logic) is a set of rules like "IF answer = X, THEN jump to step Y." Instead of a linear survey, the customer only sees the questions relevant to them.
Without branching:
Question 1 → Question 2 → Question 3 → Question 4 → Lead Form → Result
(everyone sees the same sequence)
With branching:
Question 1: "Property type?"
├── New build → Question 2a: "Ready or under construction?"
└── Resale → Question 2b: "How many previous owners?"
Each branch leads to its own question series and, ultimately, to a relevant result.
Why this matters for business
Lead qualification. If a customer answers "Budget under $2,000" — route them to a different branch, don't force them to answer premium-service questions.
Fewer steps. Instead of 15 questions for everyone — 7–8 relevant questions per segment. Fewer steps = more people finish.
Cleaner data. Each lead only passes through questions that fit their situation. You get clean data without empty "N/A" answers.
Different results for different audiences. One quiz can branch into 3–5 different results, each with its own CTA and recommendation.
Condition types in Qwizoo
Qwizoo supports these operators for transition rules:
| Operator | Use |
|---|---|
selected | An answer is selected in single/multiple choice |
not selected | An answer is NOT selected |
equals | A text field contains the exact value |
contains | A text field contains a substring |
greater than | A numeric field > value (slider, number) |
less than | A numeric field < value |
answered | Any answer provided |
not answered | Field left empty |
score ≥ | Total quiz score ≥ value |
score ≤ | Total quiz score ≤ value |
Conditions can be combined with AND or OR.
Step-by-step branching setup in Qwizoo
Add steps in the editor
First create all quiz steps, including the "alternative" steps for different branches. Name them clearly: "Questions for B2B," "Questions for B2C."
Open the step settings
Click the step after which branching should happen. In the right-hand panel find the "Transition logic" section.
Add a rule
Click "+ Add rule." Set a condition: "If the answer to [step X] = [value Y]." Choose which step to jump to when the condition matches.
Set the default transition
If none of the rules match — where to go next? That's the fallback. Typically it's the next step in the main sequence.
Verify the logic in preview mode
Qwizoo shows the transition graph as a tree. Run through the quiz in preview with different answers and make sure each branch leads where it should.
Practical examples
Example 1: Insurance quiz
Question 1: "What are we insuring?"
├── Car → Auto branch (make, year, usage type)
├── Apartment → Home branch (area, floor, building year)
└── Business → Business branch (business type, headcount)
Each branch → its own Lead Form → its own result with relevant CTA
Example 2: B2B lead qualification
Question 1: "Project budget?"
├── Under $5,000 → Skip premium questions → Lead Form (basic package)
├── $5,000–20,000 → Middle-market questions → Lead Form (standard)
└── Over $20,000 → Enterprise questions → Lead Form (premium + phone)
Example 3: Skip logic for optional questions
If the customer answers "No" to "Do you have a current vendor?" — skip "What issues with your current vendor?" and move on.
Common branching mistakes
Too complex a tree. More than 5 levels of nesting and the quiz becomes painful to maintain and debug. Simplify: merge similar branches.
Dead branches. Make sure every branch leads to a Lead Form and a Result. A quiz that "hangs" on a step is a conversion disaster.
Forgetting the default transition. If no condition matches, the quiz won't know where to go. Always define a fallback.
Not testing every branch. Test every answer combination before publishing. Qwizoo's preview mode shows which path is taken for each answer.
Branching + scoring
Branching can be combined with a point system. Each answer adds (or subtracts) points. At the end, the transition depends on the total score:
- Score ≥ 80 → "You're an ideal candidate" → Premium CTA
- Score 50–79 → "You're a good fit" → Standard CTA
- Score < 50 → "Start with the basics" → Basic CTA
This lets you auto-segment leads by "quality" and route the hottest straight to sales.
When branching isn't needed
Not every quiz needs complex logic. If your audience is homogeneous and every question matters equally to everyone — a linear quiz will be simpler and just as effective.
Add branching when:
- there are 2+ clear audience segments
- some questions are only relevant for part of visitors
- you want different results for different groups
- your current quiz has a completion rate below 50%
Conclusion
Branch logic turns a quiz from a simple survey into an intelligent qualification tool. The customer feels the quiz "gets" their situation — and they're more willing to leave a contact.
Start simple: two segments, two paths, two different results. Even that will lift conversion. Add complexity gradually, where you see drop-offs.
After setting up branching, wire up Follow-up emails for each branch separately. Each segment gets the most relevant content possible.
