> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/resources/support.md).

# Support

Contact Nested Knowledge’s support team, and learn what information to share for the fastest resolution.

The fastest way to get in touch with Nested Knowledge's support team

<a href="mailto:support@nested-knowledge.com" class="button primary">Email us at <support@nested-knowledge.com></a>

### What Information Should I Share?

Include all the relevant details so the team can help you as efficiently as possible:

* If your request relates to a specific nest, include the link to it. This can be found in the URL bar and copied and pasted.
* Describe the steps you’re taking, what happens when you take them, and what you expect to happen instead.
* If you’re running into an error message, include the error message in full.
* Screenshots are extremely helpful.

For site issues, see [Report a bug](/resources/support/report-bugs-and-suggest-improvements.md). For common quick fixes, see [Troubleshooting basics](/resources/support/troubleshooting-basics.md).

### When Will I Get A Response? <a href="#when-will-i-get-a-response" id="when-will-i-get-a-response"></a>

Nested Knowledge aims to respond to every message within one business day. The support team works across various timezones across continents: North America, Europe and Asia but busy times this might not be possible. Though rest assured the team always gets back to you as soon as they’re able.

### Search The Docs

If you require a more immediate answer, explore our documentation for an answer.

<button type="button" class="button primary" data-action="ask" data-icon="gitbook-assistant">Ask a question…</button>

### See Also

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-wand-magic-sparkles">:wand-magic-sparkles:</i><br><strong>Ask AI</strong></td><td>Ask questions about Nested Knowledge while you work in a nest.</td><td><a href="/resources/support/ask-ai.md">Ask AI</a></td></tr><tr><td><i class="fa-lightbulb">:lightbulb:</i><br><strong>Workflow Tips &#x26; Tricks</strong></td><td>Find practical guidance for each stage of your review.</td><td><a href="/review-workflow/workflow-tips-and-tricks.md">Workflow Tips &amp; Tricks</a></td></tr><tr><td><i class="fa-book">:book:</i><br><strong>Guides</strong></td><td>Follow walkthroughs for planning and running your review.</td><td><a href="https://docs.nested-knowledge.com/guides/">Guides</a></td></tr><tr><td><i class="fa-youtube">:youtube:</i><br><strong>Training Videos</strong></td><td>Watch product training videos on YouTube.</td><td><a href="https://youtube.com/nestedknowledge">https://youtube.com/nestedknowledge</a></td></tr><tr><td><i class="fa-bug">:bug:</i><br><strong>Report a Bug</strong></td><td>Report a product issue or suggest an improvement.</td><td><a href="/resources/support/report-bugs-and-suggest-improvements.md">Report Bugs And Suggest Improvements</a></td></tr><tr><td><i class="fa-screwdriver-wrench">:screwdriver-wrench:</i><br><strong>Troubleshooting Basics</strong></td><td>Try common checks for issues with the Nested Knowledge tool.</td><td><a href="/resources/support/troubleshooting-basics.md">Troubleshooting Basics</a></td></tr></tbody></table>


---

# 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.nested-knowledge.com/resources/support.md?ask=<question>&goal=<user_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.