Automated Quantum Metric Experience Anomaly Alerts
Every few minutes, WebRun opens Quantum Metric, checks for a spike in checkout errors, rage clicks, or JavaScript errors against your normal baseline, posts the anomaly to Slack naming the page and how far it moved from normal, and pings the on-call engineer on Telegram, so a broken checkout or a frustrating page gets fixed before it costs more conversions.
How do I get alerted immediately to a digital experience anomaly in Quantum Metric?
WebRun checks Quantum Metric every few minutes for a spike in checkout errors, rage clicks, or JavaScript errors against your normal baseline. The moment one appears, it posts the page and the numbers to Slack, and pings the on-call engineer on Telegram, so a broken checkout or frustrating page gets fixed before it costs more conversions.
- Checkout and experience anomalies get caught within minutes of appearing
- The on-call engineer gets pinged on Telegram instead of waiting on Slack
- Every alert names the exact page and metric, not a vague warning
Built for E-commerce teams · Site reliability teams · Product teams · On-call engineers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
quantummetric.comin a real browser with your saved login - no setup, no API keys. -
1
Quantum Metric - check for experience anomalies
quantummetric.com
WebRun opens Quantum Metric to check for experience anomalies. - Open Quantum Metric and check checkout error rate, rage clicks, and JavaScript error rate
- Compare each against your normal baseline
- Capture the page and the size of the spike
Done when Every monitored experience metric has been checked against its baseline.
-
2
Slack - post the anomaly
slack.com
WebRun opens Slack to post the anomaly. - Post the page, the metric, and the size of the spike to the engineering channel
- Group multiple anomalies on the same page into one message
- Link to the session replay in Quantum Metric if possible
Done when The engineering channel has a post for every new anomaly.
-
3
Telegram - ping the on-call engineer
telegram.org
WebRun opens Telegram to ping the on-call engineer. - Message the on-call engineer with the affected page and metric
- Send only while the anomaly is still active
- Keep the message short and specific
Done when The on-call engineer has been pinged about the anomaly.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun fix the checkout or page issue itself?
No. It only detects and reports the anomaly. Fixing the underlying issue stays with your engineering team.
What counts as an anomaly worth alerting on?
A meaningful spike above your normal baseline in checkout errors, rage clicks, or JavaScript errors, not everyday fluctuation.
Why does it post to both Slack and Telegram?
Slack keeps a shared record for the engineering channel, while Telegram makes sure the on-call engineer sees it right away.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.