Advanced node type: Decision node with scoring

Decision node with scoring

The Decision node (available on Business and Enterprise plans) evaluates multiple weighted conditions and selects the highest‑scoring path.

Use cases

• Lead qualification (score customer responses to route to appropriate sales team).
• Priority routing (compute urgency score to prioritise tickets).
• Product recommendation (score answers to recommend the best product).
• Diagnostic confidence (score symptoms to suggest most likely cause).

Configuring a Decision node

1. Drag a Decision node onto the canvas.
2. In properties, add paths (outcomes). Each path has:
   • Name (e.g., 'High priority', 'Low priority')
   • Target node (where to go if this path is chosen)
3. For each path, add scoring rules:
   • Condition (expression, same syntax as Condition node)
   • Weight (integer, positive or negative)
4. The node computes total score for each path (sum of weights for satisfied conditions).
5. The path with the highest score is followed (ties go to the first defined path).

Example: Support priority scoring

Path: 'Critical priority'

• Condition: answers['q_issue'] == 'System down' → weight +50
• Condition: answers['q_employees_affected'] > 100 → weight +30
• Condition: tier == 'Enterprise' → weight +20

Path: 'Normal priority' (default)

• No conditions, weight 0

If a customer has 'System down' (50) and 'Enterprise tier' (20) → total 70 for Critical, 0 for Normal → Critical wins.

Negative weights

Use negative weights to deduct score:

• answers['q_has_workaround'] == 'Yes' → weight -20 (reduces urgency)

Accessing scores in audit log

When a Decision node executes, the session log records the final score for each path and the chosen path. Useful for debugging scoring logic.

Limits

• Maximum 10 paths per Decision node.
• Maximum 20 scoring rules per path.
• Scores range from -10,000 to +10,000 (overflow wraps).