Website monitoring for agencies: all client sites

You look after a book of client sites, and you want to hear about a problem before the client does and show them you're on it. OctoPing watches every site from one workspace, tells you what broke, and gives each client a page and a monthly summary of their own.

One workspace for the whole agency

Your agency is one workspace, and every client site lives in it. Create a group for each client and move their sites into it, so the websites list reads the way your book of business does. You can move several sites at once, reorder the groups, and rename them when a client does. Groups are for organizing. They don't hide a site from anyone in the workspace, so treat access as a workspace question and not a group question.

A site is one URL, so example.com and example.com/checkout are two sites, and so are the www and apex versions. Your plan sets how many sites and seats the workspace has:

One price per site, every check included

Each site gets uptime, SSL, domain expiry and the other checks, and no plan limits which checks a site can use. Agencies tend to get burned by the things nobody was watching, like a certificate or a domain that sits in a client's name, so the checks that catch them aren't an upgrade. Read about uptime monitoring, SSL certificate expiry and domain expiry. Checks run from a primary checker and from the US, Europe and Asia, and a failure that only the primary sees shows as partial instead of a false outage.

A white-label status page for each client

Your client gets a page they can bookmark, with their logo, colours and the sites you choose to show, and 90 days of history for each. When something breaks, you post an incident and move it through investigating, identified, monitoring and resolved, and the client reads the timeline instead of writing to ask. Every plan includes as many pages as you need.

On a paid plan you can serve the page at the client's own hostname, such as status.client.com, with the certificate included. You add one DNS record that OctoPing shows you, and it verifies the record and issues the certificate. The page then carries no OctoPing name. A trial account can't set a custom domain. See status pages for subscribers, feeds and the rest.

Clients who hear about problems from you

Client contacts are the people you add to a client's status page by email. A Member or above adds the address and confirms the client agreed to receive it. From then on the client gets two things:

• Each kind of alert for the page's sites and heartbeats. Down and recovery, slow responses, certificate and domain expiry, DNS, content, robots.txt and hosting changes, and missed heartbeats. A contact gets the first alert of an outage and its recovery, not the reminders, and an expiry warning at most once every three days. Planned work you've silenced stays silent for them too.
• A monthly summary of the page's sites. Uptime, downtime and outages, response times and expiry dates. Heartbeats aren't in the summary.

A contact isn't a user. They don't take a seat, they have no login, and every email links to their status page and names your agency as the one monitoring the sites. They can unsubscribe from alerts, from the summary or from both. A contact hears about every site on the page, because you can't pick sites for each one, so put a client's sites on that client's page. Contacts count against the same allowance as status page subscribers:

Your team and your clients' logins

Admins and Members take a seat. Viewers are free and unlimited, and they're meant for your own people, such as a support rep who needs to look but not change anything. A Viewer sees every site in the workspace, including the ones that belong to your other clients, so don't give a client a Viewer login. The client's view is their status page and the mail you send them as a contact.

Members create and edit sites, alert rules, status pages and maintenance windows. Admins and Owners manage the team, and the Owner holds billing.

Planned work stays out of the numbers

When you take a client's site down for a deploy or a migration, schedule a maintenance window for it, once or weekly, in the time zone you pick. The window pauses up and down alerts for the sites it covers, keeps that time out of uptime and outage totals, and shows the site as in maintenance. Published status pages list a window that's running or starts in the next 7 days, under the window's name, so write the name for your client. Certificate and domain expiry alerts and change alerts still send during a window. Members can schedule windows up to 24 hours and Admins and Owners up to 7 days. Maintenance windows aren't sent to subscribers or contacts as notices.

Alerts where your team works

Each site has its own alert rules, and a site can have as many as you need, such as an email to the account manager and a Slack message to the on-call channel. Choose email, Slack, Discord, a signed webhook or browser push, and set how many failures it takes before an alert goes out. See alerts for the details.

How it fits the price

The plan you pick sets how many sites, seats and contacts the workspace has, and every plan includes all the checks, unlimited status pages, groups for each client and maintenance windows. Plans start at $19 a month for 20 sites. See pricing for the full list.

Every account starts with a 14-day free trial. No card required. Start your 14-day trial and add a client's site to see it working.