Automation · Operations and reporting

Tell customers on your status page that the store is down, asking on WhatsApp with Better Stack

An AI agent checks in Better Stack why your store went down, acknowledges the incident and posts the notice on your status page from WhatsApp.

Show me this with my own operation See every automation

How do I tell my customers my online store is down without opening Better Stack?

You write to your Met on WhatsApp that the store is not loading. The Met looks up the open incidents in Better Stack, opens the one for the failing monitor and tells you since when and which error it returned. It checks the monitor's availability per region to know whether the outage is total or regional, acknowledges the incident so escalations stop and posts a report on your status page, so your customers see you already know and do not flood the chat asking. When the monitor recovers and you confirm everything works, the Met marks the incident resolved.

What starts it

When someone asks for it

It starts when the owner, someone on the team or the agency writes to the Met on WhatsApp that the store or the site is not loading. There is no trigger to configure: the request arrives in the conversation.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Operations Met that watches the site

This is not a named, seeded Met. It is the internal Met of the business or its agency, with Better Stack connected. Its work ends when the owner knows what failed, the incident has an owner and customers see the notice on the status page.

Run by the data analyst Met

Channels: WhatsApp

What you need connected

Better Stack Automate and collaborate

6 steps · 6 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Look up the open incidents

The Met looks up ongoing or acknowledged incidents in Better Stack and keeps the one for the store's monitor. If none is open, it tells you so: the problem may not be about availability.
- incidents Better Stack
2
Read what failed

The Met opens the incident and reads the error message and the screenshot Better Stack saved, so it can tell you in the chat since when it fails and what the site returned.
- incident Better Stack
3
See whether the outage is total or regional

The Met checks the monitor's availability per region. That tells it whether the store is down everywhere or only in one area, and it says so in the notice.
- monitor_availability Better Stack
4
Acknowledge the incident

If the admin left the action on, the Met acknowledges the incident for the connected account. That stops the escalations while someone handles it.
- acknowledge_incident Better Stack
5
Post the notice on the status page

The Met creates an incident report on the status page named in the skill, with the short text you wrote in the skill or dictate in the chat. Your customers see that report as soon as Better Stack publishes it.
- create_status_page_report Better Stack
6
Close the incident once it recovers

When the monitor recovers and you confirm the store loads, the Met marks the incident as resolved in Better Stack and tells you how long the outage lasted.
- resolve_incident Better Stack

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

A monitor for the store in Better Stack

The Better Stack account with a monitor that watches the store or the site. Without a monitor there is no incident to review: the Met only reads what Better Stack already recorded.
A status page set up

The Better Stack status page your customers see, with its ID written in the skill so the Met knows where to post.
Better Stack connected with the needed actions

In Met, open Connections → Better Stack → Connect and sign in. The admin leaves acknowledging and resolving incidents and creating status page reports switched on.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not fix the outage. It tells you what failed and informs your customers; fixing the server, the domain or the store platform is still the job of whoever runs it.
It does not ask for confirmation in the chat before acknowledging or resolving the incident: if the action is on, it runs it. The admin decides in Connections which actions stay on.
It does not message each customer on WhatsApp. The notice lives on the status page; a mass message is a separate process, with templates approved by Meta.
It does not change the monitor. If the alert was a false alarm because the monitor watches the wrong URL, that is adjusted in Better Stack: the server has no tool to edit it.

FAQ

Questions about this automation

The Met tells you. The site may load while something inside fails, such as checkout; an availability monitor does not see that, and it has to be checked on the store platform.

You do. Leave a template text in the skill or dictate it to the Met in the chat. If the action is on, the Met posts without a separate confirmation, so agree on the text in advance.

Yes, if the clients' monitors are in the same Better Stack account. The Met finds the incident by the monitor of the client you name in the chat.

Keep going