First response to a client
Know whether WebWatch recently observed an outage before you reply to a client email or call.
Website downtime alerts
Website downtime alerts for client sites that need attention.
WebWatch keeps the first alert path simple: use account-email coverage, show which monitors are covered, and keep incident evidence nearby when a client site goes down.
Email alerts firstCoverage visibilityIncident contextAdvanced alerts gated
Agency overview
Client site status
18
Covered
1
Slow
0
Incidents
Retail client
client-site.example.au
Online219 ms48 sec ago
Bookings site
client-site.example.au
Slow1.6 s1 min ago
Agency site
client-site.example.au
Online184 ms2 min ago
Alert coverage
18 monitors covered by email alerts
Next review
Confirm one slow response threshold
What it helps with
Monitoring that fits client maintenance work.
Each page in this cluster maps back to the same launch promise: public website checks, clear alert coverage, and status evidence for agency-owned client work.
Coverage checks
See whether monitors have active alert coverage instead of assuming every site will notify you.
Safe advanced alerts later
Webhook controls are being built behind closed gates so public alerting does not outrun egress, signing, and support checks.
Workflow
From URL to coverage to evidence.
The launch path stays narrow enough for trust: add the site, know what will notify you, then read the latest observed state.
- 1
Create the monitor
Add the client website and confirm the monitored target before relying on recurring checks.
- 2
Confirm account-email coverage
Use the default email path first, then treat webhook-style destinations as gated advanced work.
- 3
Review incident evidence
Use latest status, timing, and incident context to decide whether to escalate, wait, or contact the host.
Practical answers
Do alerts include SMS or phone calls?
No launch claim is made for SMS, voice, or escalation policies. WebWatch starts with email-first alert coverage.
Are webhook alerts public today?
No. Webhook delivery controls exist behind closed gates, but public webhook creation waits for support, retention, and controlled smoke checks.
Can downtime alerts prove an SLA?
No. WebWatch launch copy avoids SLA promises. The alert and incident views are for practical client-site operations.
Start with one client site.
Create the monitor intent first, then finish account setup and alert coverage inside the dashboard.