> 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/complaints-resolution-v2.10/deploy/setup/production-setup/deploy-complaints-management/unified-approach/3.-add-dept-and-complaints.md).

# 3. Add Dept & Complaints

## Overview

This phase creates the core masters used by CMS. These masters drive routing and SLA.

### 3.1 What you’ll create

You will create:

* Departments (Water, Sanitation, Electricity, etc.)
* Designations (Engineer, Manager, Supervisor, etc.)
* Complaint Types (Water not coming, Garbage not collected, etc.)

### 3.2 Download the template

Step 1: Find the Common Master section.

Step 2: Run the download cell.

Step 3: Open `Common and Complaint Master.xlsx` from the notebook files.

<figure><img src="/files/1leXL9P6Ub7kv1f1XUtK" alt=""><figcaption></figcaption></figure>

### 3.3 Fill Sheet 1: Departments & designations

<figure><img src="/files/7R0tLIUrzb8suOQjBkrC" alt=""><figcaption></figcaption></figure>

Example Data:

| Department Name\* | Designation Name\* |
| ----------------- | ------------------ |
| WATER DEPARTMENT  | engineer           |
| WATER DEPARTMENT  | manager            |
| WATER DEPARTMENT  | supervisor         |
| SANITATION        | engineer           |
| SANITATION        | supervisor         |
| ELECTRICITY       | technician         |

Important:

* You can add multiple designations for one department
* Department names must be EXACTLY the same spelling

### 3.4 Fill Sheet 2: Complaint types

<figure><img src="/files/5bbvUOl0X5T84K83pbsm" alt=""><figcaption></figcaption></figure>

Example Data:

| Complaint Type\* | Complaint sub type\* | Department Name\* | Resolution Time (Hours)\* | Search Words             |
| ---------------- | -------------------- | ----------------- | ------------------------- | ------------------------ |
| Water Issues     | Tap broken           | WATER DEPARTMENT  | 24                        | water,tap,broken         |
| Water Issues     | No water supply      | WATER DEPARTMENT  | 12                        | water,supply,no water    |
| Garbage          | Not collected        | SANITATION        | 8                         | garbage,waste,collection |
| Street Light     | Not working          | ELECTRICITY       | 48                        | light,street,bulb        |

Important:

* Department Name must match EXACTLY with Sheet 1
* Resolution Time is in hours
* Search Words help citizens find complaints (use commas)

### 3.5 Upload and process

<div align="left"><figure><img src="/files/royr1Z2L32BUYftQwroQ" alt=""><figcaption></figcaption></figure></div>

### 3.6 Check results

<div align="left"><figure><img src="/files/5RyL1ljNWMteiT7NavFl" alt=""><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="/files/a9CeSm16AdBYz9aQ5Dux" alt=""><figcaption></figcaption></figure></div>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/complaints-management/complaints-resolution-v2.10/deploy/setup/production-setup/deploy-complaints-management/unified-approach/3.-add-dept-and-complaints.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.