Pro Notification Types
5 min read
Pro adds 10 advanced notification types on top of the three core notifications. Each is a self-contained email notification with its own trigger conditions, frequency, and content template. They cover the most common alerting use cases without requiring you to build custom automation rules. This page documents each notification type and when to enable it.
The Ten Pro Notification Types #
| Notification | Triggers When |
|---|---|
| High-Risk Order Alert | Order placed by Risk or Critical customer |
| Segment Change Alert | Customer crosses a segment boundary |
| Daily Digest | Once daily, summary of past 24 hours |
| High-Value Order Alert | Order placed above a configured threshold |
| Repeat Refunder Alert | Customer’s return rate crosses a threshold |
| Velocity Alert | Unusual customer activity velocity |
| Score Recovery Alert | Risky customer’s score improves significantly |
| New Customer Risk Alert | New customer triggers early risk signals |
| Monthly Revenue Protection Report | 1st of each month — protection KPIs summary |
| Chargeback Filed Alert | Any chargeback recorded (auto or manual) |
High-Risk Order Alert #
Fires when a Risk or Critical customer places a new order. The alert contains order details and the customer’s signal breakdown so you can decide whether to hold, fulfill, or cancel quickly.
Settings: minimum trust score threshold (default: 30), filter by order value (optional).
Use case: “Don’t fulfill orders from risky customers without review.”
Segment Change Alert #
Fires on every segment transition. Useful for tracking customer movement — promotions to VIP, demotions to Critical.
Settings: select which transitions to alert on (e.g. only demotions, only critical entries).
Use case: “Tell me when any Trusted+ customer drops below Caution.”
Daily Digest #
Single daily summary email covering the past 24 hours of TrustLens activity. Reduces noise vs per-event alerts.
Contents:
- Yesterday’s high-risk orders
- Recent segment changes
- Disputes filed
- Card-testing events
- Customers requiring attention
Settings: delivery time (default 9 AM store timezone).
Use case: “I want one email each morning that tells me everything I need to know.”
High-Value Order Alert #
Fires when an order exceeds a configured value threshold — regardless of customer risk. Catches high-value customers whose orders might warrant individual attention.
Settings: threshold (default $1,000), filter by customer segment (optional).
Use case: “Tell me about every $5,000+ order so I can personally review fulfillment.”
Repeat Refunder Alert #
Fires when a customer’s return rate crosses a configured threshold. Catches the pattern as it develops, rather than after months of refunds.
Settings: rate threshold (default 40%), minimum total orders (default 5).
Use case: “Alert me as soon as anyone hits 40% return rate so I can intervene.”
Velocity Alert #
Fires on unusual customer activity velocity — placing many orders in a short window, rapid refund requests, repeated coupon usage.
Settings: velocity threshold per activity type, lookback window.
Use case: “Alert on 5+ orders from same customer within 24 hours” (could be order manipulation or a coupon-stacking attempt).
Score Recovery Alert #
The positive-direction alert. Fires when a previously Risky customer’s score recovers significantly — suggesting they’ve returned to good behavior or signals are aging out.
Settings: magnitude of improvement (default +20 points), segment transition required (default yes).
Use case: “Tell me when a Risk-segment customer recovers to Trusted — they might be ready to remove from manual review.”
New Customer Risk Alert #
Fires when a new customer (sub-minimum-orders threshold) triggers early signals — first-order coupon abuse, linked-account detection, country mismatch.
Settings: which signals to alert on.
Use case: “Catch new-customer fraud rings before they accumulate enough orders to score normally.”
Monthly Revenue Protection Report #
Sent on the 1st of each month. Summarizes the prior month’s TrustLens activity in financial terms.
Contents:
- Money protected: held orders, blocked customers, prevented disputes
- Customer growth: VIPs added, customers in each segment
- Detection volume by module
- Chargeback ratio trend
- Top events of the month
Use case: Internal reporting, board updates, justifying the Pro license.
Chargeback Filed Alert #
Fires on every new dispute. Includes brand, amount, reason, and customer context.
Settings: filter by brand, minimum dispute amount.
Use case: “Tell me about every dispute immediately so I can start preparing the response.”
Configuration #
Each notification has its own toggle, recipient list, and settings. Settings: TrustLens → Notifications → Pro Notifications.
Recipients can be customized per-notification — useful for routing different alerts to different teams:
- Operations: High-Risk Order, Daily Digest
- Fraud team: Chargeback Filed, Score Recovery
- Owner: Monthly Revenue Protection
Frequency Controls #
Most per-event notifications have rate-limit settings:
- Cooldown per customer: Don’t alert on the same customer more than once per X hours
- Daily cap: Maximum total alerts per day
- Quiet hours: Don’t send between configured hours (alerts queue and send at quiet-hours-end)
These prevent any single noisy day from flooding your inbox.
HTML Templates #
Pro notifications use richer HTML templates than core notifications — color-coded segment badges, embedded score sparklines, action buttons. Templates render in most clients but degrade gracefully to plain text where HTML isn’t supported.
Templates can be customized via the WordPress filter trustlens/notification_template if you need branding or layout changes.
When to Use Pro Notifications vs Automation #
Pro notifications are pre-built for the most common alerting needs. The automation engine is for everything else.
Use Pro notifications when:
- The notification you want is on the list
- Default behavior is close to what you need
- You want low-config setup
Use the automation engine when:
- You want non-email actions (Slack, webhook to internal system)
- You want conditions beyond what the built-in notification settings support
- You want multiple actions in response to one trigger
- You want custom recipient routing based on event details
Updated on June 4, 2026
