> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/use/handle-conversations/webagent/use-keyboard-shortcuts.md).
# Use keyboard shortcuts
Use keyboard navigation in WebAgent.
Use the keyboard navigation and shortcuts available in your WebAgent environment to move through WebAgent and perform supported actions.
## Use keyboard navigation
1. Open WebAgent.
2. Use the keyboard navigation supported by your browser and organization.
3. Move through the available WebAgent controls.
4. Activate the control you want to use.
The available shortcuts and tab order can depend on your WebAgent version, browser, and enabled features.
## Common shortcuts
| Shortcut | Action |
| ------------------------------------- | ---------------------------------------------- |
| Alt + U | Open or close MePerson. |
| Alt + N | Open the dialpad tab. |
| Alt + F11 | Open the dialogues tab. |
| Alt + F12 | Open the call history tab. |
| Alt + L | Sign out. |
| Alt + H | Toggle hold for the active audio conversation. |
| Alt + Backspace | Disconnect the active conversation. |
| Alt + T | Open or close the transfer menu. |
## Tab navigation order
When you use Tab or Shift + Tab, WebAgent moves through available controls in the current context. The order can include:
1. Active-conversation buttons.
2. Contact-information tabs and links.
3. Conversation tabs.
4. Text-editor controls and response input for active text conversations.
5. UI plugin tabs when UI plugins are configured.
6. Open left-tab content.
7. Left-side navigation.
## If a shortcut does not work
If an expected shortcut does not work, use the visible WebAgent controls instead. Report the shortcut, page, and action to your supervisor or administrator so they can confirm the current keyboard-support behavior for your environment.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://atlas.anywhere.now/use/handle-conversations/webagent/use-keyboard-shortcuts.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.