FormHeartbeat
Real FormHeartbeat self-test

Both sides of one real form journey, verified.

A browser submitted a uniquely tagged request through formheartbeat.com. The monitor then found the same marker in the destination inbox and recorded one matching message.

View sanitized JSON
What this is

Operational evidence—not a mock-up and not a customer claim.

This evidence came from FormHeartbeat monitoring its own public request flow. It is a self-test, not a customer case study.

The record proves that this configured journey completed at the recorded time. It does not promise continuous uptime, prove compatibility with every form, or guarantee that no future lead can be lost.

Run FH · 16:14 UTC

One marker carried through four evidence stages.

Started 14 July 2026, 16:14:28 UTC; finished 14 July 2026, 16:14:48 UTC.

  1. 01
    Public page opened

    The monitor opened formheartbeat.com in a real browser and exposed the request form.

    Passed
  2. 02
    Tagged request submitted

    A synthetic agency name carried the unique marker shown above.

    Passed
  3. 03
    Browser success confirmed

    The expected receipt state appeared after 5.05s.

    Passed
  4. 04
    Same marker matched in inbox

    An IMAP search found 1 matching destination message before timeout.

    Passed
Captured browser evidence

Before submission and after receipt.

The long-form screenshots are unedited browser captures from the same run. Select either image to inspect the full capture.

FormHeartbeat request form before the monitored self-test submission
01 · Ready to submitUnique marker placed in the synthetic agency field.
FormHeartbeat request receipt after the monitored self-test submission
02 · Browser receiptThe website returned the expected request-received state.

Why there is no public inbox screenshot: mailbox contents are deliberately excluded. The sanitized run record reports the IMAP result—one message matched the exact synthetic marker—without publishing unrelated email data.

Fail closed, not falsely green

The monitor also recorded a real setup mismatch.

Three minutes earlier, the browser could not find the configured form selector. The run was classified as FORM_CHANGED, inbox matching was skipped, and an email alert was sent.

This was a monitor setup mismatch, not a customer outage. Its value is diagnostic: FormHeartbeat did not turn an incomplete test into a healthy result.

  • Browser stage failed during setup
  • Inbox stage was explicitly skipped
  • No healthy result was reported
  • Founder alert was delivered
Browser evidence from a FormHeartbeat self-test classified as FORM_CHANGED
Captured run · 14 July 2026, 16:11 UTC
Proven in this run

The configured public form returned success and the same synthetic marker reached the configured inbox.

Not proven

Universal compatibility, continuous availability, lead recovery, or results on any client website.

Next safe step

A read-only public-page review. No submission, login, or inbox access is needed.

Start without access

Is inbox delivery actually covered in your care plan?

Review our security boundaries