For agencies

The client forwarded a flake. You still have to explain it.

Agencies get blamed for probe-path “downtime.” Tallwatch confirms across regions before anyone is paged, and puts a status page on the client’s domain, not yours. Commercial use is allowed on Free.

Start monitoring free

23:04, a client Slack

They already forwarded it. Your status URL was still green.

One probe path failed on their UptimeRobot. Tallwatch saw disagreement and opened nothing. You paste status.client.com. The argument ends before you are on a call with their CEO.

client.comHover a region for check detail

Frankfurt (fra1) HTTP 503 · edge timeout

1 of 3 regions disagreed. No incident. Pager stayed quiet.

Your on-call. Their domain.

Select a row. Noise stays quiet. Real outages page.

The 11pm forward, written down

They will keep using the noisy tool. Your job is a URL that was green the whole time, and a real page when the contact form is actually down.

Watch the ladder, or select a step

The sausage stays in your Slack

Agency on-call sees the incident. The client sees operational or degraded on their domain. Their intern does not ack. Branding off is Business; the domain is Free.

Three clients, or one estate. Ten total.

Free is ten monitors, not ten per client. Apex, www, the form they sell. Staging and wp-admin are how you blow the cap and the pager.

All systems operational100%

status.client.com, not status.youragency.com

When it is real, the same incident flips their page. You stop explaining UptimeRobot. They stop forwarding it.

FAQ

For agencies, answered

Client count on Free, white-label branding, and whether staging should page anyone.

Start free. Client production is allowed.

Ten monitors for client sites, a quiet pager, status on their domain. No credit card.

Start monitoring free

Agent

Page as markdown

Raw agent-readable copy for this route. Copy it into a model, or browse the site-wide agent index at /llms.txt.

---
title: "Uptime Monitoring for Agencies & Client Sites"
description: "Client site monitoring with a 10-monitor budget, staging that never pages the client, and a status URL on their domain. Commercial use is allowed on Free."
canonical: https://tallwatch.com/for/agencies
url: https://tallwatch.com/for/agencies
llms_url: https://tallwatch.com/llms.txt
updated: 2026-09-04
---
For agencies

# The client forwarded a flake. You still have to explain it.

Agencies get blamed for probe-path “downtime.” Tallwatch confirms across regions before anyone is paged — and can put a status page on the client’s domain, not yours.

[Start free](https://app.tallwatch.com/sign-in) · [Free plan details](https://tallwatch.com/free-uptime-monitoring)

23:04, a client Slack
## They already forwarded it. Your status URL was still green.

One probe path failed on their UptimeRobot. Tallwatch saw disagreement and opened nothing. You paste status.client.com. The argument ends before you are on a call with their CEO.

## Your on-call. Their domain.

## The 11pm forward, written down

They will keep using the noisy tool. Your job is a URL that was green the whole time, and a real page when the contact form is actually down.

## The sausage stays in your Slack

Agency on-call sees the incident. The client sees operational or degraded on their domain. Their intern does not ack. Branding off is Business; the domain is Free.

## Three clients, or one estate. Ten total.

Free is ten monitors, not ten per client. Apex, www, the form they sell. Staging and wp-admin are how you blow the cap and the pager.

## status.client.com, not status.youragency.com

When it is real, the same incident flips their page. You stop explaining UptimeRobot. They stop forwarding it.

## Tallwatch status page on a custom domain

Client domain. Your incidents. Staging never appears here.

## 11pm Slack from a client who uses UptimeRobot

They already forwarded it to their CEO. Your job is to have a status URL that was green the whole time.

- **23:04** · client.com (their UptimeRobot) · One probe path failed — They forwarded the email. You did not get a Tallwatch page.
- **23:04** · client.com (Tallwatch) · FRA down · IAD up · SIN up — Disagreement. No incident. Status stayed operational.
- **23:07** · status.client.com · — — You paste the client-domain status URL. It was green.
- **08:40** · client.com/contact · FRA down · IAD down · SIN down — Incident to agency Slack. Client status went degraded. Staging stayed silent.

What to actually add
## Ten monitors is a client budget, not a feature list

Free is ten total, not ten per client. Three clients with apex + www + a form, or one larger estate. Staging is how you blow the cap and the pager.

| Target | Check | Why this one |
| --- | --- | --- |
| client.com | HTTP | Production apex. This is what they think “the site” is. |
| www.client.com | HTTP | www and apex diverge more often than agencies admit. |
| client.com/contact | HTTP | The form or API they actually sell against. |
| status.client.com | Status page | Their domain. Your incident. They stop forwarding UptimeRobot. |
| Skip staging.client.com | — | Never page the client for staging. Mute it or do not add it. |
| Skip client.com/wp-admin | — | Not a customer path. Auth walls look like downtime. |

Who gets the page
## Your on-call. Their status page.

The client’s intern does not ack. Your ops channel sees the sausage. They see operational / degraded on their domain.

1. **Agency on-call** — Production apex/www after regions agree. Not the client’s #general. (Internal Slack or email)
2. **Backup at the agency** — If the primary is on a shoot / in a workshop / asleep. (Email)
3. **The client** — They see state, not your incident thread. Branding removal is Business. (Status page on their domain)

## First client production, then the status URL

Commercial use is allowed on Free. Confirm that before you put a paying client on a hobby tool that forbids it.

1. Add client one’s production apex + www.
2. Do not monitor staging.
3. Internal Slack or email for your ops channel.
4. Status page on the client domain. Decide who acks (you).
5. Add the form or API they sell.
6. Count monitors. Ten total.
7. Pro when a fourth client does not fit.

## For agencies, answered

Client count on Free, white-label branding, and whether staging should page anyone.

### How many clients fit on Free?

Ten monitors total. Three clients with a few URLs each, or one larger estate. Pro raises the cap.

### Can clients see status without Tallwatch chrome?

Custom domains are on Free. Removing Tallwatch branding is on Business.

### Should staging page the client?

No. Production only. Keep staging silent, or route it internally without escalation.

In the product
## Open these next

- [Free production monitoring](https://tallwatch.com/free-uptime-monitoring): Commercial use is allowed. That is the agency question.
- [Status pages](https://tallwatch.com/services/status-pages): Custom domain on Free. Branding off on Business.
- [vs Hyperping](https://tallwatch.com/compare/tallwatch-vs-hyperping): The email they forwarded at 11pm.

## Start free. Client production is allowed.

Ten monitors for client sites, a quiet pager, status on their domain. No credit card.

[Start monitoring free](https://app.tallwatch.com/sign-in) · [Compare plans](https://tallwatch.com/pricing)