> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/complaints-management/access/pgr-user-manual/employee-user-manual/fme-resolve-complaints.md).

# FME - Resolve Complaints

Once the complaints are actioned, the FME marks the issue as resolved. The complaint is closed subsequently.

To mark the complaint as resolved, Search for the complaint using the complaint number**.** Or, the list of complaints assigned to the FME is available on the panel; click on the specific complaint.

![](https://lh5.googleusercontent.com/7Cy5hfyiTQlnJt5eUmu0PRrnJEHIRMHq0_fiHx06L7EMKy8y4vJVKSrt0eyKc8aWRKTJLBMU3GOVLlLB2oM1g3040lSNrPt-os7q0NbKv5atoXa4Fl8C0k36d-7utE82UzuFX9dv)

Click on the **Take Action** button and then click on **Resolve**. Enter any comments and upload files as evidence as required.

![](https://lh4.googleusercontent.com/8-QPcpvMWKujijeczPWywwCxDiCQ6nLXYiuJErEqEwRv9Jj_Q_TxniIvNYaC3L1QBbbEYT9lYpbdzbaU-lS63z_3gujphQF3JhtLeY-YqUxG1k0qy5NjiLs4DPg1lT4krdcwLYa0)

Click on the **Resolve** button to close the complaint. The complaint timeline is updated to Resolved. A notification is also sent to the citizen stating that the complaint is resolved.

![](https://lh4.googleusercontent.com/8-QPcpvMWKujijeczPWywwCxDiCQ6nLXYiuJErEqEwRv9Jj_Q_TxniIvNYaC3L1QBbbEYT9lYpbdzbaU-lS63z_3gujphQF3JhtLeY-YqUxG1k0qy5NjiLs4DPg1lT4krdcwLYa0)

The system will display an acknowledgement message. Click on the **Go To Home** button to navigate back to the home page.


---

# 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.digit.org/complaints-management/access/pgr-user-manual/employee-user-manual/fme-resolve-complaints.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.