Active channels
Email and Telegram are active according to plan in this fictitious scenario. No customer email is displayed; destinations are masked to avoid exposing an address, identifier or token.
Fictitious screen
WooCommerce incident alert by Telegram and email.
This page shows how a client reads WooCommerce incident alert channels: state, last delivery, anti-duplicate rule, manual test and history. All data is fictitious.
WooCommerce alert screen capture
The alerts screen should show what the team receives for a WooCommerce incident alert, broken checkout email alert, Telegram notification or agency escalation, without revealing secrets.
Email received — [CashFlowCanary] Checkout incident needs action
CashFlowCanary — Checkout incident needs action. Each channel shows the latest useful state: sent, suspended, failed or unavailable, with wording the team can read.
Incident anti-duplicate rule
After an automatic report: no automatic duplicate, no identical automatic report is sent again while the same incident has not returned to green.
Manual trigger
The client can request a test or manual report from their area without bypassing the automatic rule or creating a fake incident.
WooCommerce Telegram alert received
The WooCommerce Telegram alert repeats the same fictitious incident, with masked destination and no customer email.
Filtered history
The list shows timestamp, channel, result and related incident without raw content, sensitive identifier or customer data.
Useful actions
If a channel fails, the screen explains what to check: configuration, plan rights, masked destination or account SMTP.
Notification rule
The screen separates automatic alerts from actions explicitly requested by the client.
1. Incident detected
A prioritized signal is sent to active channels for the plan.
2. Incident still open
No identical automatic report is sent again until the check is green.
3. Manual test requested
An explicit client test remains possible to verify channel configuration.
4. Back to green
Resolution can trigger a closure message and update history.
Security reading
Alerts should inform without exposing.
The right alert screen gives enough context to act while masking sensitive destinations and avoiding useless repetition during an open incident.
- Masked destinations
- Filtered history
- Manual test
- Anti-duplicate rule
