> 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/design/architecture/solution-architecture.md).

# Solution Architecture

## Architecture Overview

Below is a high-level architecture diagram of the complaints management:

<figure><img src="/files/YVJ19umSunZ4SO5QuIS8" alt=""><figcaption></figcaption></figure>

The diagram below shows a detailed component breakdown:

<figure><img src="/files/MJJOh3DIcLRyW8ooYTQ5" alt=""><figcaption></figcaption></figure>

### Workbench UI

The workbench provides a UI interface to create, search and edit master data for all services on the DIGIT platform. It works with MDMS v2. For more information on the workbench, please [refer here](https://docs.digit.org/workbench).&#x20;

### Employee Service & UI (HRMS)

Used to create, edit, search & map employees to roles. Roles are defined as master data. The GRO, CSR & LME roles in CCRS are assigned to employees. For more information, please see the employee service.

### Inbox Service (v2)

The complaints management utilises the inbox service to populate employee inboxes with the correct action items that require their immediate attention regarding complaints. Inbox (v2) works against ElasticSearch indexes, which are populated by the Complaints service. The query is written as a configuration and stored as master data.


---

# 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/design/architecture/solution-architecture.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.