> For the complete documentation index, see [llms.txt](https://docs.blockbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockbrain.ai/~/revisions/cIYk4huBoAvhOouMPj2d/use-cases/employee-support.md).
# Employee Support
1. **Upload documentation**: Upload all relevant user manuals, documentation, and customer support tickets to a central knowledge base.
2. **Instant access to internal information**: Provide your colleagues and users with immediate access to internal information, ensuring they always have the necessary data at their fingertips.
3. **Retrieve step-by-step guides**: Effortlessly access detailed step-by-step instructions with relevant images or screenshots from hundreds of files.
4. **Reduce onboarding time**: Shorten the onboarding time of new team members by 50% by providing them with quick access to all necessary documentation and training materials.
5. **Efficiently resolve inquiries**: Resolve 80% of questions without employees needing to escalate or ask colleagues for help, increasing productivity and reducing interruptions.
6. **Organize information**: Keep all documents neatly organized and easily searchable, allowing users to quickly find what they need.
With the Knowledge Bot Retriever, your company can optimize information access, improve onboarding processes, and increase overall efficiency.
---
# 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.blockbrain.ai/~/revisions/cIYk4huBoAvhOouMPj2d/use-cases/employee-support.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.
