> For the complete documentation index, see [llms.txt](https://docs.threatdefence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.threatdefence.com/service-providers-msp-and-mssp/servicing-customers.md).

# Servicing Customers

As an MSP/MSSP, you must deliver the following minimum services to ensure value for your customers:

* Ensure at least 80% of critical customer systems are onboarded to the platform.
* Perform ongoing alert triage (when the SOC service is enabled).
* Conduct regular threat hunting sessions at least once per week.
* Hold monthly or quarterly technical security posture review calls. Please refer to our guide on [best practices for these calls](https://docs.threatdefence.com/security-operations/regular-review-calls#best-practice-the-security-review-call).
* Ensure email alerts are being sent to the customer. Approximately 95% of organizations require these alerts for operational awareness, even if they are false positives (e.g., from an internal network scan).
* Ensure you are comfortable responding to an incident by validating that the relevant data has been onboarded. Note, our analysts are always available to assist with IR or take a lead role.

**ThreatDefence Support:** Our personnel are available to assist with all the above services. For the review calls, we can help train your team or facilitate the first few calls to establish an effective routine.


---

# 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.threatdefence.com/service-providers-msp-and-mssp/servicing-customers.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.