> 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/csr-search-track-complaints.md).

# CSR - Search/Track Complaints

Employees can search for specific complaints using the registered mobile number of citizens or by entering the last few digits of the complaint number.

![](https://lh4.googleusercontent.com/ia_YmtCk7dI0r8rRqcAUBf-QWZHw3KysBiIGszG2sStEoPwAYLW_OZ3RUMpfAkIt3L0FQJovdzHC1lQFGfvF_er_alsfCS8e_JTtNEz4fg6nB5fUnKoeABHXJKzpCAZiSay8IV2D)

Navigate to the homepage and click on the **Inbox** option to view the registered complaint. The employee inbox contains the list of complaints assigned to the logged-in employees for further action.

![](https://lh6.googleusercontent.com/2Tle4aM9UQwKPHdIOGsiJKt-wb-QdmOhgDeZENeyJqBzVvTOkeDNqPIO3WMgSVDLe1XOHEJLomr_3EZzHdbZyNErDAcI60eM43otmos86kO-UszdaHD7-eZxAEulQmPlxM6ob6he)

To search complaints navigate to the **Complaints** home page. Enter citizen **Mobile No.** Or, enter the last 6 digits of **Complaint No.** 

![](https://lh4.googleusercontent.com/j0JnZRs9mPr5N_JUPjQBkg00CRyMNj_hrXKJDRp82FgLEfbmc3Rih51d4zijL87tkfH9iIxV6ef1mxRt6lSNJ4krjrZ3wLv0WrHLsglqUwznDq_aLJylY5L_tB_dT_x7ngNUgijK)

Click on the **Search** button. You can also use the **Filter By** parameters in the left panel of the screen to narrow down your search. The available filters include **Complaint SubType**, **Locality**, and **Status**. The system retrieves and displays the matching records. 


---

# 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/csr-search-track-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.