> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/general/faq/how-do-i-escalate-an-issue.md).

# How do I escalate an issue?

Most questions are answered fastest by TalentMap support. Bring in your Project Manager when the problem affects many participants or a deadline.

***

## Who to contact

* **Something in Compass is not working, or you are stuck on a task.** Contact TalentMap support through the chat icon in Compass or email <support@talentmap.com>.
* **The problem affects many participants at once, or a launch date, reminder, or presentation is at risk.** Contact your Project Manager directly.
* **A question about your questionnaire, results interpretation, or action planning.** Contact your TalentMap consultant or Project Manager. See [Schedule a Meeting with your Consultant or Project Manager](/knowledge-base/step-1-prepare-for-action/schedule-a-meeting-with-your-consultant-or-project-manager.md).

***

## What to include

Give support what they need to reproduce the problem in one message:

1. The survey name.
2. The page you were on and what you clicked.
3. What you expected and what happened instead.
4. A screenshot or the exact error text.
5. If it is a participant issue, the survey link the participant used (never their answers).

***

## Related Articles

* [Troubleshooting: Where to Look First](/knowledge-base/general/troubleshooting-where-to-look-first.md)
* [My survey link is not working, what do I do?](/knowledge-base/step-4-deploy-employee-survey/survey-live-faq/my-survey-link-is-not-working-what-do-i-do.md)
* [Who will be responsible for different aspects of the project?](/knowledge-base/step-1-prepare-for-action/prepare-for-action-faq/who-will-be-responsible-for-different-aspects-of-the-project.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.talentmap.com/knowledge-base/general/faq/how-do-i-escalate-an-issue.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.