> 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/services.md). # Services ## Overview This section covers the core platform services used by DIGIT Complaint Management. These services handle configuration, notification preferences, and event-driven notification delivery. Use this section to understand each service's role, APIs, data model, and setup requirements. ## Services List Select a service to explore its architecture, APIs, data model, and setup.

Service	Link
Config Service Tenant-scoped configuration with schema validation, unique constraints, and secure handling of sensitive fields.	Config Service
User Preferences Service Manages user consent and preferred language for WhatsApp, SMS, and email notifications.	User Preferences Service
Novu Bridge Service Consumes domain events, resolves templates and providers, checks consent, and triggers notifications through Novu.	Novu Bridge Service

--- # 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/design/architecture/services.md?ask=&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.