> ## Documentation Index > Fetch the complete documentation index at: https://rasa.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Try Your Assistant > Rasa Studio — Try Your Assistant **Try your assistant** in Rasa Studio provides powerful tools to test and inspect how your trained assistant behaves. Whether you're reviewing the logic behind a conversation or converting an interaction into a test, this feature helps ensure everything works as expected. ## Before You Start Make sure your assistant has been trained at least once. > Need help? [See the training guide](/docs/studio/test/train-your-assistant) for more information on how to train your assistant. ## Starting a Conversation To access the **Try your assistant** page: 1. Click **Try your assistant** in the left-hand navigation of Rasa Studio. 2. If your assistant supports multiple languages, choose one from the dropdown. Select Language 3. Ensure the correct assistant version is selected. See Assistant Version Want to switch versions? Go to **Assistant Versions** and click the chat icon next to the version you want to test. Select Assistant Version Once ready, start the conversation by sending a message. ## Switching Between Chat and Voice If your license includes voice capabilities, you can switch between chat and voice modes: 1. Use the toggle above the message input to switch to voice. Then click "Call". Switch to Voice 2. Allow microphone access, speak to your assistant, and view real-time transcripts in the chat panel. Currently, voice input is limited to English. Voice Conversation 3. By default, Studio uses Deepgram for speech-to-text (STT) and Cartesia for text-to-speech (TTS). You can customize this setup and choose a different provider outside of Studio. [Learn more about building voice assistants](/docs/pro/build/voice-assistants) ## Activate Assistant Version The assistant version will be inactive after one hour or when the maximum number of active assistants is reached. To reactivate and test it, go to **Assistant versions** and click the arrow icon. Once reactivated, you can test the version again. Activate Assistant Version ## Basic Mode: Live Flow Preview Basic Mode is the default mode when testing. It provides: * A live chat interface * A **Live Flow Preview** panel that shows your assistant moving through different conversation paths Use this mode to quickly check if your assistant follows the correct logic. Basic Mode in Try Your Assistant ## Inspector Mode: Debugging and Insights Toggle **Inspector Mode** (top right corner) to unlock deeper insights: Enabling Inspector Mode #### 1. View Events Click on any user or assistant message to view slots set, flows triggered, and other key events. Tracking Key Events #### 2. Predicted Commands Select a user message to view the predicted command and understand why a specific path was taken. Predicted Commands in Inspector Mode #### 3. Model Details Click on an assistant message to see the prompt, input, and token usage — useful for understanding performance and API costs. Model Details in Inspector Mode ## Speed Up Testing Beyond analysis, Inspector also provides tools to speed up your conversation testing workflow. #### Conversation Replay 1. Select the **Replay** icon next to a "Waiting for user input" event. This will trigger the conversation to replay back that point. 2. Try out different inputs for testing different outcomes of the conversation. Replay your assistant #### Generate Tests from Chat Once you're happy with a conversation, you can export it to **share with your team**, or **generate a test case** for your assistant. Select the menu icon in the top right of your conversation panel. * **Download logs** if you'd like to review the full deployment logs of your running assistant. * **Download conversation** — Saves your conversation as a YAML transcript. When your assistant has a Studio-managed language slot, the file includes a `language` field identifying the language the conversation was in. * **Download E2E Tests** If you'd like to save your conversation and use it as an **end-to-end (E2E) test** to validate assistant behavior. For more details on the testing format and how to run E2E tests as part of your workflow see the [Pro guides for testing](/docs/pro/testing/evaluating-assistant). Download ## Related topics - [Studio Architecture](/docs/reference/architecture/studio.md) - [Your First Assistant](/docs/studio/tutorial.md) - [Introduction](/docs/studio/test/introduction.md) - [Train Your Assistant](/docs/studio/test/train-your-assistant.md) - [Introduction to Actions](/docs/studio/build/actions/introduction.md)