> For the complete documentation index, see [llms.txt](https://docs.klink.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.klink.cloud/dashboard-and-reports/reporting/call-reports/satisfaction-survey.md).
# Satisfaction Survey
{% hint style="info" %}
'Satisfaction Survey' report provides statistics about the key pressed collected from callers for a queue and its agents. This topic describes the report details, and shows you a report example.
{% endhint %}
### Report details
| Parameter | Description |
| ------------------------------------- | ----------------------------------------------------------------------- |
| KEY: {key\_pressed}({numeric} Points) | The key pressed by caller and corresponding score for the key. |
| Total KEY | The total number of keys that were collected for the queue or an agent. |
| Total Points | The total satisfaction survey scores for the queue or an agent. |
| Average Points | The average satisfaction survey scores for the queue or an agent. |
{% hint style="info" %}
Note: Average Points ＝ Total Points / Total KEY, where the calculated average points will be truncated to two decimal places without rounding up.
{% endhint %}
### Report example
The following report shows the satisfaction survey of Queue.
---
# 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.klink.cloud/dashboard-and-reports/reporting/call-reports/satisfaction-survey.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.
