> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/site-faq/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/site-faq/faq/general/what-response-rate-should-we-try-to-achieve.md). # What response rate should we try to achieve? 75%+, and our goal is to help you reach an 80% response rate. TalentMap works closely with its clients to achieve a high response rate. We provide you with best practices on how to obtain high response rates, and we monitor response rates closely to ensure that there is continuous improvement in our systems and the best practices we share with you. One of the keys to our high response rates is our online reporting tool. With our online reporting tool, the survey champion can view response rates in real time and filter down by demographics to see what groups require a little more encouragement and support to complete the survey. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.talentmap.com/site-faq/faq/general/what-response-rate-should-we-try-to-achieve.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.