Get instant alerts when admissions or donations hit an unusual reading
Every hour, WebRun checks Blackbaud Altru for admissions counts, donation totals, and membership signups against the thresholds you set, and sends an immediate Telegram alert to the operations team if any reading is significantly above or below expectations so issues can be addressed in real time.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get real-time alerts when museum admissions or donations hit unusual levels?
Every hour during operating hours, WebRun checks Blackbaud Altru and compares admissions counts, donation totals, and membership signups against the thresholds you set. When any metric deviates by more than 30 percent, it posts an immediate Telegram alert with the metric name, current value, and expected value so your team can respond before the anomaly compounds.
- Admissions and revenue anomalies are caught within an hour instead of at the end-of-day report
- The operations team can investigate and respond to low-admissions events before the venue closes
- Repeated alerts for the same sustained deviation are suppressed so Telegram stays actionable
Built for museum operations managers · cultural attraction directors · visitor services teams · nonprofit finance officers
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
app.blackbaud.comin a real browser with your saved login - no setup, no API keys. -
1
Blackbaud Altru - check metrics against thresholds
WebRun opens Blackbaud Altru to check metrics against thresholds. - Open Altru and navigate to the Daily Sales or Revenue Summary view
- Read the current-hour admissions count and compare it to the expected hourly average for this day of the week
- Read the cumulative donation total for the day and compare it to the daily donation threshold
- Read the count of membership signups for the day and compare it to the daily signup target
- Flag any metric that is more than 30 percent above or below the expected value as an exception
Done when All three metrics are read and compared against thresholds. Exceptions are identified.
-
2
Telegram - alert the team on any exception
WebRun opens Telegram to alert the team on any exception. - If no metric triggers an exception, skip posting and wait until the next hourly check
- If one or more exceptions are found, post an alert to the operations Telegram channel immediately
- Include the metric name, current value, expected value, and the percentage deviation in the alert
- Note the time of the reading so the team knows exactly when the anomaly was detected
Done when An alert is posted to Telegram for every exception, or no post is made if all metrics are within tolerance.
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
Will it take any action when an exception is detected, or just alert?
It only alerts. WebRun posts the exception details to Telegram so a human can investigate and respond. It never modifies any record or contacts a visitor or donor as a result of an exception.
How do I set the thresholds for what counts as unusual?
You set the expected daily and hourly targets for each metric during setup. WebRun compares live Altru readings against those targets each hour and flags anything that deviates by more than the tolerance percentage you choose.
Will it flood Telegram with alerts if admissions stay low all day?
No. Once an exception is flagged for a metric, WebRun waits for that metric to return to within tolerance before it can trigger a new alert for the same deviation. This prevents repeated alerts for the same sustained anomaly.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.