> 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/gro-reject-complaints.md).

# GRO - Reject Complaints

In certain cases, the GRO might reject registered complaints. This usually happens when the complaint is beyond the operational scope of the department or the complaint is invalid.

To reject complaints, navigate to the Inbox and search for the complaints waiting to be assigned. Click on a complaint to open and view the complaint details.

![](https://lh3.googleusercontent.com/l_X2sCpQMHQwAVn8p1ld0fSyTztM2RTy7sdBB3gRPXXxn2jDtJCravCnn0Gy-a4kpEBL1iDVKYc8fDciHgEenm3n72VFIXBS8_Ftk6lrKzfphOAo8uZy7kVoTRcWBQ5Gnrg8k6Yt)

Click on the **Take Action** button and then click on the **Reject Complaint** option in case the complaint does not look valid or relevant.

![](https://lh3.googleusercontent.com/YV7NXgWgAFRfe02jW44F_44JT7HCxfA73H5w2HgfVVLn-4hN9useSrLyHtFvw-Qfh2Qfdr18pSzUJeG7X4rPX-aQGCW4LR34p7BJZ8FABllM6epD4qxrC-BKXhF3w35UWgC0Zvmq)

Select a reason for rejection and add additional comments if any. Upload files to support the reason for the rejection. Click on the **Reject** button. The complaint is rejected.


---

# 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/gro-reject-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.