Tests 10+ critical systems
Loading alerts...
Loading registry...
| Severity | SMS | Auto-Purge | Action Required? | |
|---|---|---|---|---|
|
🔴 CRITICAL
System down, DB offline, payment failures
|
✅ Yes | ✅ Yes |
90 days
after you resolve
|
YES
Acknowledge & Resolve
|
|
⚠️ WARNING
Degraded performance, non-critical failures
|
❌ No | ✅ Yes |
90 days
after you resolve
|
YES
Acknowledge & Resolve
|
|
ℹ️ INFO
Successful operations, health checks passing
|
❌ No | ❌ No |
60 days
auto (even if not resolved!)
|
NO
Just logs, auto-cleans
|
Loading logs...
If you see "Invalid" in the Alert Registry, click this button to initialize the Notification Center:
This creates the Notification Center company in the database. Run once, then configure Twilio and contacts below.
Your Twilio Account SID (starts with AC)
Your Twilio Auth Token (keep this secret)
Your Twilio phone number.
Important: After saving, configure your Twilio webhooks:
SMS Webhook: https://clientsvia-backend.onrender.com/api/twilio/sms
Voice Webhook: https://clientsvia-backend.onrender.com/api/twilio/voice
Note: If no company is configured for the called number, the system automatically plays the test greeting below.
Method: POST (for both)
Turn ON to activate test call system
Your Twilio phone number.
This message will be spoken when you call your Twilio number to test the system.
🎯 To Test: Call your Twilio number: +1 (888) 522-2241
You'll hear this message played back by Twilio's text-to-speech engine (Alice voice).
Enter the area code and phone number.
Loading contacts...
Manage where new submissions and daily review summaries reach you from the dashboard settings menu.
Open notification settingsControl which alerts generate SMS/Email notifications vs. log-only. Prevents notification spam while ensuring critical issues reach you immediately.
System down, database offline, payment failures
Degraded performance, non-critical failures
Successful operations, health checks passing
Get ONE daily email with system health, stats, and warnings. Know everything is running without being spammed.
During these hours, WARNING alerts are queued for morning. CRITICAL alerts still send immediately (configurable).
Group repeated errors into ONE alert. Example: 5 SMS failures → "🚨 5 SMS_DELIVERY_FAILURE errors in 15 minutes"
Configure when system health alerts are triggered. Adjust these values to reduce false positives.
Current: Alert if hit rate drops below 60%
💡 Tip: Lower this after server restarts to avoid false alerts during cache warm-up (typically 1-2 hours).
Current: Alert if memory usage exceeds 85%
Current: Alert if response time exceeds 100ms
💡 Recommended After Server Restart:
Hit Rate: 50% | Memory: 85% | Latency: 150ms
Configure how often unacknowledged alerts are resent. Use comma-separated minutes.
Example: "30, 30, 30, 15, 15" = Resend every 30min (3x), then every 15min (2x)
Example: "60, 60, 60" = Resend every 1 hour (3x), then stop
Example: "120" = Resend once after 2 hours (low priority)
Processing...