> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v1.9/setup/8.-operational-support.md).

# 8. Operational Support

Ongoing management and maintenance of the solution is critical to ensure its continued successful operation.

Set up the following tiers of support, as relevant in the country of operation:

1. **Level 0: self-service options.** Develop appropriate self-service options for end-users. This might be a paper handbook, an online chatbot that answers simple questions or online support materials that users can look up themselves.\
   Update these generic User Support Materials with details of the country configuration for use in any of these channels.
2. **Level 1: first line support.** Define and operationalise a mechanism by which users can raise any issues or questions that they have not been able to resolve themselves, by consulting User Support Materials. This mechanism should be easy to use for the User i.e. Whatsapp, email, or another instant communication tool. By using a ticket tracking tool e.g. [GitHub](https://github.com/) you can easily track issues to resolution and also identify patterns in user issues that can inform follow-up training or an improvement in user-support materials.
3. **Level 2: technical support.** Your management and maintenance team will be required to make basic technical fixes that can not be resolved through level 1 support through the service desk.
4. **Level 3: expert support.** For issues that can't be resolved by level 2 support i.e. bug / technical fixes to the core product, these will be escalated to expert support to ensure that it can be fixed and an upgrade pushed to all instances.

If you require support with any level of operational support, please reach out to **<team@opencrvs.org>** to discuss how we can support you.


---

# 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://documentation.opencrvs.org/v1.9/setup/8.-operational-support.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.