When an hour of downtime costs more than a year of care.
On the three lower plans we detect and notify, and your team takes action. Enterprise is the only tier where the response is our obligation, written into the contract.
You start the plan straight away and we agree the terms in parallel.
What the plan starts with, before the terms are agreed
- 1
We start with a conversation, not a button
You fill in a short description of the service: critical hours, maintenance windows, the paths that must work, contacts and the order of escalation. On that basis we agree response times and the scope of on-call duty.
- 2
Monitoring runs from day one
We start the plan immediately with provisional settings: checks every 30 seconds, content review every six hours, all notification channels, a year of history. Until the terms are agreed we say plainly that the targets are provisional, and we keep them out of the report.
- 3
Tests you cannot buy off the shelf
We walk through a purchase step by step on a test account and check a form all the way to the inbox. Every shop has a different scenario, so we agree it together instead of promising an automation.
- 4
Reviews on demand and after a release
You run a review of the whole service with one click, and your deployment system can report to us by itself, so the check starts right after the change rather than in the next cycle.
- 5
Server care
Once agreed, we take over access and part of the administrative work. We describe the scope in the contract, because no two cases here are the same.
What we do not promise before the conversation
We do not put response times we have not agreed into the offer, and we do not call them an SLA until a contract stands behind them. Until then the panel states that the values are provisional. That is inconvenient when selling, and that is exactly why we do it.
Arrange a conversation
Tell us what you do and what needs watching. We will come back with a proposed scope and response times, and you can start monitoring before the terms are settled.