# What can an MSP promise clients about after-hours security monitoring?

Promise only what you staff. If software watches at night and a technician reads alerts in the morning, say exactly that: detection runs around the clock, review happens on working days, and urgent alerts reach an on-call person within an agreed time, if you have one. Do not write monitoring 24/7 when nobody responds at 03:00: insurers, auditors and courts read such words literally, and the gap can void a claim or start a dispute. State response times, what counts as urgent, and what the client must do themselves. An honest, smaller promise you keep is worth more than a large one you cannot. NetSenX detects at all hours; it is not a staffed service.

FAQ: [MSPs and MSSPs](https://netsenx.com/en/faq/msp) · https://netsenx.com/en/faq/what-can-an-msp-promise-about-after-hours-monitoring

## Read next

- https://netsenx.com/en/problems-we-solve
- https://netsenx.com/en/partners

## Related questions

- [How should an MSP describe security monitoring in a contract without promising a SOC?](https://netsenx.com/en/faq/how-to-describe-security-monitoring-in-an-msp-contract)
- [Who is liable if a monitored client is breached?](https://netsenx.com/en/faq/who-is-liable-if-a-monitored-client-is-breached)
- [What should an MSP do if a client refuses to pay for security?](https://netsenx.com/en/faq/what-if-a-client-refuses-to-pay-for-security)
- [When my customer falls under NIS2, does the MSP fall under it too?](https://netsenx.com/en/faq/when-my-customer-falls-under-nis2-does-the-msp-too)
- [What is in a NIS2 supplier questionnaire, and how do I answer it?](https://netsenx.com/en/faq/what-is-in-a-nis2-supplier-questionnaire)