> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/managed-monitoring/monitoramento-gerenciado/horas-de-atuacao.md).

# Remediation hours model

How the Managed Monitoring team's action hours for fixing problems work.

Each Managed Monitoring plan includes a **monthly package of action hours** for fixing problems. When the volume of support requests exceeds what is included, the additional hours are billed separately, with full transparency.

### Price per additional hour

At the current hourly rate provided by Power Tuning (reference: **R$ 260,00/hour**):

* minimum billing time of **30 minutes per request**;
* complex fixes are billed according to the time actually used;
* every hour worked is **recorded and reported** with a breakdown of the activity.

### Control and flexibility

* **Prior approval:** no hours are used without prior communication with and approval from the customer;
* **Monthly limit:** the customer can set a maximum number of action hours per month, keeping control of the budget;
* **Tailored criticality:** the customer and Power Tuning define which alert types require proactive action from the team;
* **Monthly summary:** monthly report of hours consumed, for accountability and internal audit.

### Hours bank

The hours included in the plan work as an **hours bank**: hours not used in one month can be accumulated, according to the terms of the commercial proposal (reference: up to 6 months). This way, a quiet month does not mean lost hours.

### Scope of the monitored environment

The customer defines what the team follows:

* **The entire tenant:** all monitored workspaces;
* **Only critical workspaces:** only the most important production environments.

This allows you to tailor the service to what really matters to the business.

### Full transparency

* Every hour worked is recorded with a description of the activity.
* Hour consumption is presented in the **monthly report** and can be checked with the team at any time.
* There are no surprise charges: any action that consumes hours is communicated before it is performed.

To see how many hours are included in each plan, see [Available plans](/en/managed-monitoring/monitoramento-gerenciado/planos.md).


---

# 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.powermonitor.com.br/en/managed-monitoring/monitoramento-gerenciado/horas-de-atuacao.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.