Set up no-activity alerts and weekly digests

Choose a quiet-site threshold, notification recipients, and a practical review process for monitoring emails.

Written By Kelsey

Last updated About 1 month ago

Always Alert can warn when no eligible notification activity has been observed for a chosen period and send a weekly summary of observed activity.

Both features depend on WordPress scheduled events and the site’s existing mail transport.

Configure no-activity alerts

  1. Go to Always Alert → Monitoring.

  2. Enable No-activity alerts.

  3. Set Alert after to the number of quiet days that should prompt investigation.

  4. Enter an alert recipient, or leave it blank to use the fallback recipient.

  5. Select Save Monitoring Settings.

Choose a useful threshold

The right threshold depends on normal site behaviour:

  • A busy lead-generation site may warrant 1–3 days.

  • A steady business site may suit the default 7 days.

  • A low-volume or seasonal site may need 14–30 days or a documented seasonal adjustment.

Avoid a threshold so short that normal quiet periods create alert fatigue. Use historical enquiry volume and business expectations rather than guesswork.

What a no-activity alert means

It means Always Alert has not observed an eligible WordPress notification within the configured window.

It does not prove:

  • a form is broken;

  • users attempted to submit a form;

  • the website had traffic;

  • a mailbox rejected mail;

  • email delivery failed.

Treat it as a prompt to check recent business activity, submit controlled tests, review logs, and inspect the mail provider.

Configure the weekly digest

  1. Enable Weekly digest report.

  2. Enter a digest recipient, or leave it blank to use the fallback recipient.

  3. Save Monitoring Settings.

The digest summarises observed notification and fallback-copy activity. Give the inbox an owner and a simple review rule; otherwise the report becomes background noise.

Recommended response process

When an alert or unexpected digest arrives:

  1. Open Always Alert → Dashboard and check the last eligible notification and last fallback copy.

  2. Review Always Alert → Logs for recent injected, excluded, duplicate, or skipped events.

  3. Submit each critical public form.

  4. Confirm the normal recipient and fallback recipient receive the expected messages.

  5. Review SMTP or transactional-provider logs if WordPress accepted the messages but they do not arrive.

  6. Record the cause and corrective action in the site’s maintenance notes.

Related articles