Detail
What we watch, and what happens when it breaks
Monitoring is only worth paying for if you know exactly what it covers. This is the whole list, including the parts it does not cover.
1. Endpoint probes, every 5 minutes
Your form posts to some endpoint — a serverless function, an API route, a form service. We call it on a five-minute cycle and check the response it gives back, not merely that something answered.
This is what catches a deploy that dropped the function bundle, a route that started
returning 404, a handler that began rejecting valid submissions, and a
config change that broke the endpoint while leaving the page it lives on perfectly fine.
A single failed probe does not page you. Connection-level failures get re-checked after a short settle, because a resolver hiccup on our side is not an outage on yours. Only a failure that survives that gate becomes an alert.
2. A real browser submits a real test lead
Once a day, a headless browser loads your form the way a customer would, fills it in, submits it, and we confirm the submission actually landed where it is supposed to land.
This is the check that finds the failures a status probe structurally cannot: JavaScript
that throws before the submit fires, a spam filter that started eating legitimate
messages, a notification integration whose credential expired, a required field that a
redesign made impossible to fill. The endpoint answers 200 through every one
of those.
Test submissions are tagged so they are obvious in your inbox and never get mistaken for real business.
3. Route health
The URLs that matter — your landing pages, the destinations in your ads and directory listings, your redirects and canonical host — get verified on the live domain and on any deployment-preview URL you provide. A campaign pointing at a page that quietly started redirecting to your homepage is expensive and easy to miss.
4. Alerts you can afford to trust
We agree on an alert path during onboarding and confirm it before the monitoring term starts. The gating above matters more than the channel: monitoring that cries wolf gets muted, and muted monitoring is the same as no monitoring. We would rather tell you about one real failure than ten maybes.
During each 30-day term you get a short summary of what was checked and what happened, including a term with no incidents. A quiet term should still produce evidence that the checks ran.
What this does not do
- It does not fix your site. We tell you it broke, and what we saw. Repair is a separate conversation.
- It is not uptime hosting or a status page. We watch the lead path, not your whole stack.
- It does not generate leads. Nothing here brings you traffic or customers. It protects the ones you already earn.
- It cannot watch what it cannot reach. If your form sits behind a login, a hard bot challenge, or a third-party widget that blocks automation, we will tell you that up front rather than sell you a check that silently does nothing.
Getting set up
| Step | What happens |
|---|---|
| You send the URL | The page your leads come through, plus how you want to be alerted. |
| We check it is watchable | The checkout first confirms that the public page loads and exposes a form or lead endpoint. If that automatic check cannot see one, no payment link is created. |
| We wire it up | Probes, the browser test, route health, and your alert channel. |
| You get the activation record | We email the enrolled checks and alert route after the Square payment is confirmed. If the deeper setup cannot be completed, the payment is refunded. |