# DECISION node

In this example overview, prerequisites are established through the ['Function' node](https://docs.borndigital.ai/digital-agent/conversation-flow/nodes-explained/function-node) or some variable in the[ 'Answer' node ](https://docs.borndigital.ai/digital-agent/conversation-flow/nodes-explained/answer-node)before reaching the 'Decision' node. To witness its application, refer to the chapter [Creating Your First Virtual Assistant](https://docs.borndigital.ai/digital-agent/building-new-projects):

* **County:** Tracks the number of times the user crosses the ['Function' node](https://docs.borndigital.ai/digital-agent/conversation-flow/nodes-explained/function-node).
* **Value:** Assuming the value is set to 32, multiple scenarios are crafted based on these values to bifurcate the [Conversation Flow](https://docs.borndigital.ai/digital-agent/conversation-flow).

<figure><img src="https://content.gitbook.com/content/6iQTvxgRZRwPS1NgIGEb/blobs/aGeTF1yeRjnZQXsw4j0v/BD_Bx_Decision_node.gif" alt=""><figcaption><p>Decision node in nutshell</p></figcaption></figure>

Precise conditions within the ['Decision' node](https://docs.borndigital.ai/digital-agent/conversation-flow/nodes-explained/decision-node) hold utmost significance. Conditions are processed sequentially, moving from the first to the last. When a condition is met, the connected target node is triggered.&#x20;

In cases where no conditions match, the ['Decision' node](https://docs.borndigital.ai/digital-agent/conversation-flow/nodes-explained/decision-node) resorts to the 'Other' path, similar to a fallback function seen in other nodes. Visualize it as akin to an SQL Case function (when/else logic).

{% hint style="info" %}
Consider altering the condition order based on your flow logic and priority for optimal decision-making within your [Conversation Flow](https://docs.borndigital.ai/digital-agent/conversation-flow)
{% endhint %}