> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/search-and-workspace/using-workspace/asking-questions-and-exploring-nexthink-content.md).
# Asking questions and exploring Nexthink content
Workspace can answer a wide range of questions related to Nexthink Infinity, DEX concepts, workflows, and product documentation. It reviews Nexthink documentation and provides recommended steps, linking to relevant pages and training materials.
Workspace can also help you troubleshoot issues with Nexthink itself, by referencing the Nexthink support knowledge base (KB) directly in the conversation.
## Example question types
* "How do I configure a webhook?"
* "What is the difference between hard and soft navigations?"
* "What is the limit of campaigns I can create in Workplace Experience?"
* "I see some active devices not reporting any data in Nexthink. Why?"
You can also add context relevant to an intended task:
* "How can Nexthink help me troubleshoot MS Teams call quality issues?"
***
RELATED TOPICS
* [Workspace](/user-guide/search-and-workspace.md)
* [Using Workspace](/user-guide/search-and-workspace/using-workspace.md)
---
# 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://docs.nexthink.com/user-guide/search-and-workspace/using-workspace/asking-questions-and-exploring-nexthink-content.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.
