Operanse
Sign inSign up

Features · Stay informed

Alerts & incidents

One message per incident, not forty.

Related problems on a site within half an hour become one incident with one message. Critical problems always send; warnings wait for the morning digest unless someone asked for them. Each person gets it on their own channel, at the severity they chose.

Start a 14-day trialNo card needed.

On every plan, Watch (free) includedEmail on every plan; Slack, SMS and WhatsApp from Monitor.

Four signals, one incident (example store)Example data
  • Orders below usual09:30
  • Payments failing09:31
  • PHP warnings up09:34
  • Checkout slower09:40
One incident, one messageExample data
CRITICALopened Tue 10:00
Orders stopped: Stripe payments failing
grouped
4 signals within 30 minutes
sent to
email · Slack · SMS
01

An alert storm hides the one message that matters

A gateway breaks at half past nine. Orders drop, payments fail, PHP logs warnings and checkout slows, and a simple monitor sends a message for each, every few minutes, to everyone. By ten people are muting the channel the real alert arrives in.

  • Ten alerts for one cause, each with a different name.
  • Everyone woken for something only the developer can fix.
  • Warnings so frequent that criticals are ignored.
02

What you can see

Related signals, one incident

Problems detected on the same site within 30 minutes of each other are grouped into one incident. If the site is down, that leads it. Every open problem in it carries an estimate of the money affected, or says which figure is missing to price it.

An incident (example store)Example data
CRITICALopened Sat 02:14
Site down, with checkout errors
leads
Site down: public address and plugin probe failing
also
Checkout errors · scheduled actions past due

estimate about $420 of orders not taken so far, from this store’s usual Saturday 02:00–03:00

The channel each person reads

Email on every plan. From Monitor, Slack, SMS (US numbers) and WhatsApp (any country). SMS and WhatsApp carry critical alerts only.

Every destination confirms by double opt-in before it receives anything.

ChannelsExample data
  • Email
  • Slack
  • SMS
  • WhatsApp
channelcarriesplanstatus
Emailcritical, warnings by choiceAll plansconfirmed
Slackcritical, warnings by choiceMonitorconfirmed
SMS · WhatsAppcritical onlyMonitorawaiting code

Who gets what

A rule sets the organisation’s policy: which sites, which kinds of problem, which hours. Each recipient has their own minimum severity, so “everything by email, critical by SMS” is two recipients, not two rules. Quiet hours hold warnings; a critical goes out anyway.

Recipients on one ruleExample data
recipientchannelminimumstatus
OwnerSMScriticalcritical
DeveloperSlackwarningwarning
Agencyemailwarningwarning
03

What arrives

What changed, against what normal, what it is worth, and on Insight, the likely cause.

An alert mail, as sent (example store)packages/alerts · renderAlertMail
Operanse alert · Northwind Supply · northwindsupply.example
[Operanse] Northwind Supply: orders paid but not moved — critical

CRITICAL open since Tue 14:21 (store time)

What changed

9 orders carrying a Stripe transaction id have been pending for more than 15 minutes, totalling $1,180. Completed payments in the last hour: 2, against this store’s usual 11–17 for a Tuesday afternoon.

Comparison

This store’s own normal for Tuesday 14:00–15:00, learned from 6 weeks of history: usually 14 completed payments and no paid-but-pending orders. Both readings are outside this store’s normal range.

What this is worth

Priced from this store’s hourly takings: a shortfall of about $1,240 over 3 hours, carried as an estimate. Renewals due in the window are included; retries are not counted twice.

AI review (evidence-cited)

The orders were paid at Stripe and the store did not complete them. The site’s own calls to api.stripe.com answered normally through the hour [E3], so the outbound side is healthy; what stopped is the inbound completion. A recorded change at 13:58 updated WooCommerce Stripe Gateway 9.4.1 → 9.5.0 [E5], 23 minutes before the first stuck order [E1]. Likely cause: the gateway’s webhook handler is no longer completing payment on this store since the update. Confidence: moderate.

What Operanse did not verify

Whether Stripe’s side reports the webhook deliveries as failed, and whether the update changed the webhook signing secret. Both are visible in the Stripe dashboard, not from the store.

Every message states the observed numbers, the store’s usual for that hour, and the estimate. On Insight, the AI review is in the same message when it is ready in time.

The example is illustrative. Operanse reports; it never applies a fix.

04

Coverage and limits

What it covers

  • Incidents, not alert storms. Related problems within 30 minutes of each other become one incident; downtime leads it.
    All plans
  • Email, Slack, SMS and WhatsApp. Email on every plan; Slack, SMS and WhatsApp from Monitor. Every destination confirms before it receives anything.
    All plans
  • Who gets what. Rules for which sites, kinds of problem and hours alert, and each recipient’s own minimum severity.
    Monitor
  • Teams and client access. Unlimited users from Monitor, and any user limited to certain sites. Watch: you and one helper.
    All plans

Limits

  • SMS and WhatsApp share a daily allowance per organisation: 20 on Monitor, 50 on Insight, to up to 5 numbers. An SMS uses more of it than a WhatsApp message.
  • Watch sends email to two addresses; Slack, SMS and WhatsApp need a paid plan.
  • Grouping is per site, over 30 minutes. Problems on two sites are two incidents.
  • An estimate of money affected is an estimate, from the store’s own hourly sales.
05

Start using it

  1. Install the plugin from wordpress.org. It is read-only: it cannot change the site.
  2. Pair the site with the token from your dashboard. Setup, step by step
  3. Alerts go to your account’s email from the start: critical problems at once, the rest in the report your plan includes. Add people and channels when you are ready.

All plans On every plan, Watch (free) included. Email on every plan; Slack, SMS and WhatsApp from Monitor. Compare plans

06

Questions

Will I get a message for every warning?

Not by default. Critical problems always send. Warnings go into the next morning’s digest (on Watch, the weekly report) unless a recipient sets their minimum to warning.

Can I keep my phone quiet at night?

Quiet hours hold warnings until morning. A critical problem is sent anyway: a store that has stopped taking orders is worth waking for.

Can an agency get alerts for only some sites?

Yes. Members can be limited to certain sites, and a rule can cover only some sites. Unlimited members from Monitor; Watch is you and one helper.

What does an SMS cost me?

Nothing per message. Texts come out of the plan’s daily allowance.

Related features

Start a 14-day trialNo card. Every feature, on Insight, for 14 days. Or see all features.