> 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/cms-v2.11/access/pgr-user-manual/citizen-user-manual/reopen-complaints.md).

# Reopen Complaints

| <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/ybWARDPmo1FIqqxhq6wn/image.png" alt="" data-size="original"> | <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/8uBT1C76uLAnBFukEHvG/image.png" alt="" data-size="original"> |
| ------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| To reopen the complaint navigate to the **Complaints > My Complaints** menu option.                                                   | Click on the closed complaint that you want to reopen.                                                                                |
| <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/u1VQ7IEpuR1ak0rUUz4U/image.png" alt="" data-size="original"> | <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/ZL49ABuA9Udcm4XJ8BZ2/image.png" alt="" data-size="original"> |
| Scroll down to the **Complaint Timeline** section. Click on the **Re-Open** button on the timeline.                                   | Select the appropriate reason for reopening the complaint.                                                                            |
| <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/apzWxYxZl7PnldCzut9H/image.png" alt="" data-size="original"> | <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/kYYO7rB5qYbr8SsumUhJ/image.png" alt="" data-size="original"> |
| Click on the camera icon to upload any photos related to the complaint.                                                               | Enter any additional information in the **Provide Additional Details** section. Click on the **Reopen Complaint** button once done.   |

{% hint style="info" %}
The Re-Open button will only be available for 5 days after the department employee resolves and closes the complaint. The 5 days is the default period. This is configurable, and the number of days can vary depending on the State or ULBs. The citizen or CSR will not be able to reopen complaints once this period is over.
{% endhint %}

| <img src="https://content.gitbook.com/content/xNs29HvQfLFAPZCcDd7D/blobs/5gwGJiY9DeA53w6RTfcX/image.png" alt="" data-size="original"> | The notification along with the complaint number is sent to your registered mobile number. You can track the complaint status using a mobile or web app. Click on the **Go back to the home page** 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/cms-v2.11/access/pgr-user-manual/citizen-user-manual/reopen-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.
