> 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/deploy/configure.md).

# Configure

## Objective

To ensure the **Complaint Management** functions smoothly across all interfaces—**citizen portal, mobile app, dashboards, and employee interfaces**—a set of core configurations must be completed **before deploying the service**.

***

## Configurations Needed 

Before deploying the `ccrs-services` application image, the following configurations and data must be **preloaded**:

1. [**Workflow Configuration**](/complaints-management/deploy/configure/workflow.md) **-** Define workflows for each stage of the complaint lifecycle (e.g., registration, assignment, resolution, closure).
2. [**Master Data (MDMS)**](/complaints-management/deploy/configure/master-data.md) **-** Load necessary master data, including service definitions, complaint types, departments, roles, and ULB information.
3. [**Localisation Messages**](/complaints-management/deploy/configure/localisation.md) **-** Add translations for all UI labels, error messages, and service names across supported languages.
4. [**Persister Configuration**](/complaints-management/deploy/configure/persister.md) **-** Configure how and where data will be stored (PostgreSQL DB mappings for CMS-related actions).
5. [**SLA Configuration**](/complaints-management/deploy/configure/service-level-agreement-sla.md) **-** Establish service-level agreements for each complaint type and department to monitor and track resolution timelines.
6. [**IDGen Configuration**](/complaints-management/deploy/configure/id-generation-idgen.md) **-** Define ID formats for generating unique complaint IDs using the ID generation service.
7. [**Inbox**](/complaints-management/deploy/configure/inbox-v2-and-elastic-search.md) **&** [**Indexer Configuration**](/complaints-management/deploy/configure/indexer.md) **-** Configure inbox filters for employees and indexing settings for search and reporting.
8. [**Boundary Configuration**](/complaints-management/deploy/configure/boundary.md) **-** Load geospatial boundaries (e.g., wards, zones) to map complaints accurately to locations.
9. [**Google Maps** ](/complaints-management/deploy/configure/google-maps.md) **-** Configure Google Maps to pinpoint the exact location of the complaints.
10. [**WhatsApp Setup**](/complaints-management/deploy/configure/whatsapp-setup-guide.md) **-** Set up WhatsApp to enable users to raise or track complaints through this channel.
11. [**Common Configuration**](/complaints-management/deploy/configure/common-configuration-guidelines.md) **-** Configure your brand colours and logos as required.


---

# 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/deploy/configure.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.