Use post-launch monitoring
Run a temporary handover window with per-notification heartbeats, reminders, and an optional full submission copy.
Written By Kelsey
Last updated About 1 month ago
Post-launch monitoring is a temporary handover workflow for the days or weeks after a site launches or a major form change goes live.
While active, Always Alert sends a separate metadata-only heartbeat for each eligible form notification and periodic operational reminders. The mode expires automatically after the configured duration.
Before enabling it
Confirm:
the normal form notifications and fallback copy have been tested;
the monitoring recipient expects the messages;
the mailbox can handle one heartbeat per eligible notification;
the duration and reminder cadence match the handover plan;
the full-submission-copy setting remains off unless its privacy requirements have been approved.
High-traffic sites can generate a significant number of heartbeat emails.
Configure post-launch monitoring
Go to Always Alert → Monitoring.
Enable Post-launch monitoring.
Enter the post-launch recipient, or leave it blank to use the fallback recipient.
Choose an active duration from 1 to 90 days.
Choose a reminder interval from 1 to 30 days.
Review the full submission copy setting carefully.
Select Save Monitoring Settings.
The active window begins when the setting is first enabled and saved. The dashboard shows its start, expiry, recipient, and recent activity.
What a heartbeat contains
Each heartbeat is a new operational email containing:
site name;
form name where it can be determined;
detected source;
timestamp;
dispatch status.
By default, a heartbeat does not include the original message subject, recipients, form fields, submission content, or attachments.
“Dispatched” means the site accepted the heartbeat for sending. It does not prove inbox delivery.
Operational reminders
Reminders prompt the recipient to check the dashboard. They send on the configured cadence regardless of activity.
When activity is flowing, use the reminder to check in with the client and confirm the expected enquiries are reaching their team. When the site is quiet, submit controlled form tests and investigate.
Optional full submission copy
The full submission copy option also adds the post-launch recipient to each eligible original notification using the configured BCC, CC, or To method.
It is off by default because it exposes submission content to another recipient. Enable it only when:
the recipient is authorised to access the client’s form content;
there is an appropriate lawful basis;
any required data processing agreement is in place;
the site’s privacy information accurately describes the transfer.
Always Alert does not store that content, but the site’s mail system sends it to the additional recipient.
End the handover
The mode turns itself off at expiry. You can also disable it earlier and save Monitoring Settings.
At handover completion:
Confirm the client’s normal recipients are correct.
Confirm recent real or controlled submissions arrived.
Disable full submission copy if it was enabled.
Review and export any operational records you need.
Keep routine fallback copies, no-activity alerts, and weekly digests configured as agreed.