> For the complete documentation index, see [llms.txt](https://studio.docs.ai.vonage.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studio.docs.ai.vonage.com/voice/nodes/flow-control/context-switch.md).

# Context Switch

The *Context Switch* node enables the user to get out of context to jump to another intent while being prompted to fill a specific parameter. This means that the user can switch to the intents of the Context Switch node during the conversation. Imagine this node as a classification node without the entry point - accessible at any point during the flow. 

![](/files/-MhwjeZvS90KXqk-2N9r)

{% hint style="warning" %}
*Please note the following:-*

* *the context switch node can only be used once in a flow.*
* *If in a collect input node the parameter collected is listed as a sys.any entity type, then chances are that the input will not be passed to the context switch. In these cases better to use classification node with the required intent.*
* *Context switch intents are currently not recognized in the Listen node.*
  {% endhint %}

### When to use it?

The user is being prompted to give their order number to help track their package in a *Collect Input* node with *sys.serial number* as the attached entity. 

Let's say, the user doesn't want to fill in this detail, but rather be transferred to a virtual assistant. Instead of giving the order number, the user can say "I want to speak to an agent" and they are being transferred accordingly.

![](/files/-Mi1BrQxLE35tnMvjBpW)

{% hint style="info" %}
*Context switch is great to include important intents that you know your users may randomly pick up in the middle of the conversation. This includes things like agent requests and going back to the main menu. The context switch node helps you recognise when your user has said something like “main menu” and routes it back to where you want it to connect in the flow. Best practice is to let the user know that they have picked this flow and then lead them to it.*
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://studio.docs.ai.vonage.com/voice/nodes/flow-control/context-switch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.