> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/work-manager/work-manager/feedback-features.md).

# Feedback Features

Information on how client users can provide feedback to you on specific work items, via feeback links available in the footer of emails sent from Enate.

## Customers can provide feedback via Email links <a href="#a-getting-customer-feedback-via-email" id="a-getting-customer-feedback-via-email"></a>

If the ‘Allow Feedback’ setting is ticked in the Ticket's Builder settings (see [here ](/enate-help/builder/builder/service-lines-screen/creating-ticket-case-and-action-types-in-a-service-line.md#c-creating-a-new-type-of-ticket)for more information on how to do this), outgoing emails will contain a footer-based link for recipients to give feedback scores.

<figure><img src="https://3859925423-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWYnDNwe3Cuo4zlGbs5-887967055%2Fuploads%2F4zO29YrBmW4yQ6Uqjt0y%2FEmail%20Feedback%20Link.png?alt=media&amp;token=fce313ae-915d-476a-8d20-33a25cbe1be7" alt=""><figcaption></figcaption></figure>

They can do this at any point in the processing of the Ticket. When a client user clicks on any of these links, a browser window will be opened for them showing the Enate Feedback for&#x6D;*.* It offers the same feedback icons as shown in their email, but allows a user to change their selection should they wish, and also to add an additional comment before submitting.

<figure><img src="https://3859925423-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWYnDNwe3Cuo4zlGbs5-887967055%2Fuploads%2FqJeCsHClg50UMMQ99RpL%2Fimage.png?alt=media&amp;token=b0cff73a-9481-450d-bca5-612cf16c05c1" alt=""><figcaption></figcaption></figure>

All feedback and comments are subsequently stored in Work Manager against this Ticket, for Users to [view](#c-displaying-recent-feedback-details-via-work-items).&#x20;

Further to this, feedback data is stored in the Data Warehouse, allowing longer-term analysis of feedback data (i.e. you can build reports to analyse this data across multiple different criteria).

## Displaying client Feedback details on Tickets for Users to View <a href="#c-displaying-recent-feedback-details-via-work-items" id="c-displaying-recent-feedback-details-via-work-items"></a>

When dealing with a Ticket, if a client user has provided feedback (via the feedback footer links in one of the emails they have received from Enate) Users are able to see the customer’s current feedback rating via the 'smiley face' icon link in the ribbon bar of the Ticket:

<figure><img src="https://3859925423-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWYnDNwe3Cuo4zlGbs5-887967055%2Fuploads%2FPpVg6BeJDl6NCU5lsAN9%2FEmail%20Feedback%20Ribbon%20Link.png?alt=media&amp;token=6c475b00-4f51-4cff-bbe8-1e4520cac29b" alt=""><figcaption></figcaption></figure>

Clicking on this will open a feedback popup displaying the client user's feedback rating/s (via emoticon), along with any associated comments.  The overall average rating, between 1 and 5 - calculated when feedback is given multiple times on a single Ticket - is also show at the top of the popup. Latest feedback is shown at the top of the screen.

<figure><img src="https://3859925423-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWYnDNwe3Cuo4zlGbs5-887967055%2Fuploads%2Fsm8rG0kpdepdw8QE1WXJ%2Fimage.png?alt=media&amp;token=9132e523-c704-42ea-832f-1feef7450545" alt=""><figcaption></figcaption></figure>

Further to this, this feedback data is also stored in the Data Warehouse, allowing longer-term analysis of feedback data (i.e. you can build reports to analyse this data across multiple different criteria).


---

# 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.enate.net/enate-help/work-manager/work-manager/feedback-features.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.