> 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/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/complaints-management.md).

# Complaints Management

## Overview

Users can file a complaint using the HCM app. There are a few assumptions:

* Not all complaints will be logged using the complaints module. Users may prefer raising complaints on WhatsApp groups/calls, and may not be registered in the system.
* Complaints are most likely to be logged by users on behalf of other users (Most common use case: Supervisors raising complaints on behalf of users).

## User Roles

<table><thead><tr><th width="166.109375">User Role</th><th width="284.203125">Scope of Action</th><th>Role Description</th></tr></thead><tbody><tr><td>Registrar</td><td>Create and view complaints.</td><td>Registrars can raise technical complaints on the application</td></tr><tr><td>Field Supervisor</td><td><p></p><p>Create and view complaints.</p></td><td>Assist the frontline teams and raise the issues communicated by them on the application</td></tr><tr><td>Supervisor</td><td><p></p><p>a. Create and view complaints.</p><p>b. Resolve complaints, re-assign complaints back to the helpdesk, and reject complaints.</p></td><td>Monitor the overall campaign and provide assistance for the issues raised by the field teams</td></tr><tr><td>Helpdesk user</td><td><p>a. Create and view complaints.</p><p>b.  Resolve complaints, assign complaints, and reject complaints.</p></td><td>Helpdesk users are the support team established to provide assistance throughout the campaign.</td></tr></tbody></table>


---

# 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/health/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/complaints-management.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.
