Form notifications go to people, and people leave. When the form's recipient or the fallback recipient moves on, email keeps flowing to whoever is left, so nothing looks broken, no alert fires, and your two-recipient safety net quietly becomes one. Nobody finds out until the second mailbox goes stale, and by then enquiries are missing. What we're planning: On a cadence you choose (quarterly by default), Always Alert emails your fallback recipient a short review of every notification recipient it knows about: the form's own recipients where we can read them, plus your fallback, emergency, and monitoring addresses. One link opens a review screen in wp-admin: confirm the list is still right, or fix it on the spot. If the review goes unanswered after a generous window and one reminder, your monitoring address gets a nudge to check in with the client. Being straight with you, as always: a confirmed review is a human saying "this list is still correct": it doesn't prove inbox delivery, and software can't know someone resigned. What it does is put the recipient list in front of a human a few times a year, which is how turnover gaps actually get caught. This builds on per-form recipient discovery, which is coming first.

Kelsey about 1 month ago

Always Alert ships with a metadata-only operational log designed for notification assurance without storing full submissions. The shipped controls include: configurable retention from 1 to 365 days; status, reason, source, subject, short recipient summary, method, and timestamps; no stored email body, message HTML, attachment, raw header, or form-field content; CSV export with spreadsheet-formula hardening; manual log clearing; WordPress personal-data export and erasure integration; suggested WordPress privacy-policy text; complete settings, log, monitoring-state, and scheduled-event cleanup on uninstall. The optional post-launch full submission copy is separate from the log and remains off by default.

Kelsey about 1 month ago

Always Alert includes two temporary oversight workflows for agencies and site maintainers. Post-launch monitoring provides a time-boxed handover window with one metadata-only heartbeat per eligible notification, periodic operational reminders, and automatic expiry. An optional full submission copy is available only when the monitoring recipient is authorised to receive that content. Emergency oversight temporarily adds a separate authorised recipient while a missing-enquiry or mailbox-access problem is being investigated. It also expires automatically. These workflows provide visibility and additional recipient paths. They do not automatically detect inbox failure, recover messages sent before activation, or guarantee delivery.

Kelsey about 1 month ago

lways Alert can email an operational warning when no eligible notification activity has been observed for a configured period. It also provides a weekly digest summarising observed activity, fallback-copy events, sources, and monitoring state. Recipients can use the main fallback inbox or dedicated alert and reporting addresses. A no-activity alert is deliberately worded as an investigation prompt. It does not prove that a form is broken, that somebody attempted a submission, or that a mailbox rejected a message.

Kelsey about 1 month ago

Always Alert now provides an at-a-glance health dashboard for WordPress form-notification assurance. The shipped dashboard shows: eligible notifications observed; fallback copies added; excluded or system emails; last-seen activity; monitoring and temporary oversight status; source breakdowns for supported plugins and page builders; WordPress scheduled-event health. The overall health signal also appears in the WordPress admin bar and the main WordPress dashboard widget. Current source attribution includes common signals from Contact Form 7, Gravity Forms, Fluent Forms, WPForms, Ninja Forms, Formidable Forms, Bricks, Breakdance custom forms, WooCommerce, WordPress System, and Generic wp_mail.

Kelsey about 1 month ago

Always Alert adds a configured fallback recipient to eligible WordPress form notifications before the site’s existing mail transport takes over. The shipped capability includes: targeted Form Notification Mode; broader Universal wp_mail Mode; BCC, CC, or To copy methods; duplicate prevention across recipient lists; common WordPress system and WooCommerce exclusions; a Mail Handoff Test for the configured fallback inbox. Always Alert does not send mail independently or replace an SMTP or transactional provider. A successful WordPress handoff does not guarantee final inbox delivery.

Kelsey about 1 month ago

We plan to explore an agency-friendly presentation mode for client care plans. Potential options include: agency identity on selected client-facing reports; simpler client-facing status summaries; configurable support or handover links; controlled visibility of technical settings; terminology suited to an agency’s maintenance service. The purpose is to help agencies demonstrate proactive care without obscuring what Always Alert actually does. Core safety warnings, privacy disclosures, licence state, and the distinction between WordPress handoff and inbox delivery will remain clear.

Kelsey about 1 month ago

We plan to investigate first-class WordPress Multisite support for organisations managing notification assurance across a network. Areas to address include: network activation behaviour; site-level versus network-level fallback settings; permissions and visibility for site administrators; per-site monitoring health; scheduled events and reports across the network; safe uninstall and data-retention behaviour. Multisite environments vary significantly, so the final scope will be based on real customer configurations rather than treating network activation as a simple checkbox.

Kelsey about 1 month ago

Agencies often deploy the same monitoring baseline across many WordPress sites. We plan to add a safe way to export and import Always Alert configuration. This should make it easier to standardise settings such as: notification coverage mode; copy method and exclusions; activity-log retention; no-activity thresholds; digest preferences; approved monitoring defaults. Sensitive or site-specific values will require special handling. Imported settings should never silently enable emergency oversight, restart an expired post-launch window, or expose a client’s notifications to an unintended recipient.

Kelsey about 1 month ago

We plan to add a concise handover report for agencies and freelancers completing a launch or major form change. The report could summarise: the monitoring window and configured oversight recipient; eligible notifications observed during the window; fallback copies added; the most recent activity by supported source or form; any quiet periods or operational warnings; the date temporary post-launch oversight ended; an honest explanation of what WordPress-side monitoring can and cannot prove. The goal is to turn the existing post-launch workflow into a useful client-care artefact without exposing submission content.

Kelsey about 1 month ago

We plan to make Always Alert’s operational reporting easier to tailor and investigate. The work under consideration for this planned area includes: choosing the day and time for weekly digests; better filtering and searching of activity logs; clearer source and reason breakdowns; exportable monitoring summaries; optional hourly or daily heartbeat summaries for high-volume post-launch windows; more useful reporting without storing form bodies or attachments. The objective is to reduce inbox noise and make it faster to answer practical questions such as “what changed?”, “which source went quiet?”, and “was a fallback copy added?” Reporting will retain Always Alert’s current language boundaries: observed activity and successful WordPress handoff do not prove final inbox delivery.

Kelsey about 1 month ago

We plan to extend the current single fallback address into more flexible assurance routing. Possible capabilities include: multiple fallback recipients; different recipients for operations, reporting, or departments; recipient and domain-based rules; clearer duplicate-prevention reporting; safe defaults that keep BCC as the normal private-copy method. The goal is to support agencies and larger organisations without turning Always Alert into a CRM or general email automation tool. Additional recipients can expose form content to more people, so routing controls will be designed with explicit access, privacy, and volume warnings. Always Alert will continue to operate before the existing WordPress mail transport and will not replace SMTP or determine final inbox delivery.

Kelsey about 1 month ago

We plan to expand reliable detection, source attribution, form naming, and Form Intelligence coverage across more of the WordPress form ecosystem. Always Alert already recognises common signals from Contact Form 7, Gravity Forms, Fluent Forms, WPForms, Ninja Forms, Formidable Forms, Bricks, and Breakdance custom forms. The next stage is deeper, tested support where each product exposes suitable hooks or configuration APIs. Coverage work may include: more reliable form names and identifiers; direct links to form settings; notification recipient inspection; clearer compatibility and confidence labels; support for additional builders and custom-form workflows. We’ll prioritise integrations based on customer usage and votes. Protection can still work through WordPress’s general mail layer even when a message is labelled Generic wp_mail, but deeper integrations make monitoring and diagnosis more useful.

Kelsey about 1 month ago

Today, Always Alert can tell when eligible notification activity was last observed across the site. We plan to make that monitoring more specific for forms that can be identified reliably. The proposed per-form view will show: the last observed notification for each supported form; recent activity counts; the notification source and form name; an optional quiet-period threshold for important forms; a clear distinction between “no activity observed” and “form failure confirmed.” This will help agencies notice that one high-value enquiry form has gone quiet even while other forms on the same site continue generating notifications. Per-form alerts will be opt-in and configurable so low-volume or seasonal forms do not generate misleading noise.

Kelsey about 1 month ago

Always Alert currently protects notifications once WordPress attempts to send them. A form with no active email notification configured produces no message for that protection layer to observe. We plan to inspect notification settings where supported and surface useful warnings such as: no active email notification is configured; a notification action is disabled; no recipient can be found; the recipient is dynamic or uses placeholders; the configuration cannot be inspected safely and needs manual review. This work is intended to expose a particularly dangerous silent failure: a published form can accept a submission while sending no notification at all. Because form plugins model notifications differently, results will include clear confidence labels and links for manual verification. A warning will be an investigation prompt, not a claim that a lead has been lost.

Kelsey about 1 month ago

We plan to add a Form Intelligence view that shows the forms Always Alert can discover on the current WordPress site. The aim is to give agencies and site maintainers a practical inventory showing: the form name; the plugin or builder that owns it; where the form can be edited; whether Always Alert can inspect its notification configuration; when activity from that form was last observed, where reliable identification is available. Direct edit links will reduce the time spent hunting through several form plugins and page builders during maintenance or an incident. Coverage will be introduced progressively because each form product stores and exposes its configuration differently. Always Alert will show honest confidence and support labels rather than pretending every form can be inspected perfectly.

Kelsey about 1 month ago

We’re preparing the first stable commercial release of Always Alert: form notification assurance for WordPress. The release brings together the complete protection and monitoring workflow already proven through the release-candidate programme: fallback copies for eligible form notifications; targeted Form Notification Mode and broader Universal wp_mail Mode; BCC, CC, and To options with duplicate prevention; notification source attribution; no-activity alerts and weekly digests; post-launch heartbeats and temporary emergency oversight; a health dashboard, admin-bar status, and WordPress dashboard widget; metadata-only logging, privacy controls, and WordPress personal-data tools; paid licence activation and update delivery through Freemius. The remaining work is focused on final release validation, customer-facing documentation, packaging, and ensuring the upgrade path is dependable. Always Alert observes and modifies email inside WordPress before the existing mail transport takes over. It does not replace SMTP or guarantee final inbox delivery.

Kelsey about 1 month ago