> For the complete documentation index, see [llms.txt](https://docs.taqnyat.sa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taqnyat.sa/product-docs/core-concepts/building-a-chatbot-scenario/go-to.md).

# Go To

The **Go To** unit redirects the user to another predefined point in the chatbot scenario. It is useful when you want to reuse an existing path instead of rebuilding the same flow again. Chatbot\_en

## Steps

{% stepper %}
{% step %}

### Add a Go To unit

Add the **Go To** unit at the point where you want the conversation to jump to another existing part of the scenario.
{% endstep %}

{% step %}

### Select the destination

When you open the unit, a dropdown list appears containing the units that are already configured in the scenario.

Choose the unit you want the user to be redirected to.
{% endstep %}

{% step %}

### Identify unnamed units

If a unit has not been given a custom name, it can be identified using its system-generated ID.

If the ID does not appear, use the **Sync** icon to refresh and display it. 
{% endstep %}
{% endstepper %}

### Important notes

* The destination unit cannot be entered manually.
* You must select it from the available list.
* New units cannot be created directly from the **Go To** interface. 

### Example

If the user enters a value that is not handled in the current path, the **Go To** unit can redirect them to an existing fallback path or another service-related path.

### What’s next?

Continue to **Input Value** to learn how to store data and variables collected during the conversation.