When your product breaks, your inbox fills with the same message. Connecting Better Stack means customers see the outage before they write in, and the AI that answers them knows about it.
Add Better Stack from Integrations, paste a Better Stack API key, and pick which status page to use. Gleap loads your status pages once the key is accepted, so if the list is empty the key is wrong.
Pick the page your customers would look at, not an internal one. Everything below is driven by what that page reports.
Your status appears in the messenger — the overall state and the individual services from that page. Customers see it as they open the widget, which is exactly when they were about to ask whether it's just them.
This is the part worth setting up for. When your status page is anything other than operational, the current incident is passed to Kai: which services are affected, and what's ongoing.
So during an outage, someone asking “why can't I log in?” is told there's an incident affecting logins, rather than being walked through resetting their password.
While everything is operational, nothing is added — no status noise in normal conversations.
The reverse is just as true: an incident left open after it's resolved keeps being mentioned. Closing it in Better Stack is what stops that.
Gleap refreshes the status periodically rather than watching it live, so there's a short lag between a change on the status page and what customers see. Minutes, not hours — if it's longer than that, re-check the API key, since an expired one leaves the last known status in place.
