FormReceipt is the company behind contact form monitoring software—not a generic forms or receipts product. It runs real browser submissions, stores proof, and helps teams confirm whether lead notifications actually arrive.
"FormReceipt provides contact form monitoring: we use browser automation to open pages you configure, attempt test submissions, store run results and related artifacts, and send service-related email."
"FormReceipt is contact form monitoring with proof—not a receipts app and not an uptime ping. We submit your real form on a schedule, save screenshots, and ask your team one question: did the lead notification arrive?"
The FormReceipt SaaS product is contact form monitoring with scheduled browser test runs, screenshots, timeline events, and inbox receipt confirmation—not a generic receipt generator.
"FormReceipt monitors contact forms in four steps: we submit like a visitor, your site sends its usual lead mail, your team answers yes/no that it arrived, and we repeat on your schedule—with screenshots and run history every time."
"Plans scale by how many forms you monitor—the workflow stays the same: real submission, proof on file, inbox confirmation, and alerts when things go wrong."
FormReceipt's yes/no step where your team confirms whether the expected lead notification email arrived after an automated test submission—separate from browser submit success.
A stable lowercase correlation id (fr-YYYY-MM-DD-…) assigned to each FormReceipt test run so inbound submitter notification emails can be matched to the correct run.
Evidence
definitionrelevance 0.94
"Public test IDs are lowercase (fr-YYYY-MM-DD-…) with case-insensitive IMAP matching so submitter notification emails reliably tie to the run."
FormReceipt's pre-save page scan that discovers the visible contact form, maps fields, and returns an access assessment before automated monitoring can run.
A supplemental FormReceipt signal when the monitored site auto-replies to the test submitter address; it appears on the run timeline but does not replace receipt confirmation.
Evidence
definitionrelevance 0.93
"When the site sends an auto-reply to the test submitter address, the run shows a supplemental submitter notification detected hint during receipt confirmation without auto-completing the test."
The distinction between a visitor seeing form submit success (HTTP 200, thank-you page) and the lead notification actually reaching a monitored inbox—the gap FormReceipt tests for.
"A successful submit is not the same as a delivered lead: HTTP 200, a thank-you page, and a green SMTP plugin do not guarantee anyone received the message."
Whether contact-form submissions reliably reach the intended recipient mailbox—not merely whether the public form accepts input or the app logs a send attempt.
"FormReceipt automates the first and last miles: real browser submission, proof of what happened on the page, and tracking whether the expected receipt showed up."
"SPF lets receiving mail servers check whether an outbound server is authorized to send mail for your domain. The domain publishes a DNS TXT record listing permitted senders."
"DKIM adds a cryptographic signature to outgoing messages. Receivers fetch the public key from DNS via the selector and verify the message was not altered in transit."
An email authentication policy layer that builds on SPF and DKIM alignment, declares receiver policy, and enables aggregate reporting on authentication failures.
"Fix SPF so legitimate sending IPs and includes are correct, enable DKIM signing with your provider, publish DMARC in p=none while monitoring aggregate reports, then tighten policy."
When an application cannot log in to its SMTP relay—often from wrong credentials, TLS/port mismatch, or provider policy blocks—so form mail never leaves the server.
Evidence
procedurerelevance 0.94
"Confirm SMTP host, username, and password or token, then confirm the expected port and encryption mode from your provider docs before checking provider logs."
FormReceipt's probe-time verdict on whether automated test runs can reach the form: blocked by WAF, manual-only due to CAPTCHA, or automate OK.
Evidence
definitionrelevance 0.97
"Blocked means HTTP 403/429/451 or a stuck interstitial. Manual only means CAPTCHA or a password gate on the form. Automate OK means proceed with field mapping and schedules."
FormReceipt's recurring automatic browser checks on a timezone-aware schedule so teams spot form breakages without manual retesting.
Evidence
definitionrelevance 0.96
"FormReceipt runs checks on a schedule so you can spot breakages quickly without manual testing. Paid plans can set timezone, preferred time, and active weekdays. Free runs once per week at signup weekday and local time with no schedule customization."
Targeted WAF or firewall rules that permit FormReceipt's bot identity headers and user agent on the form route without disabling site-wide bot protection.
"The safest fix is targeted allowlisting for known FormReceipt markers: allowlist identity headers and user agent on your form route only, not the entire domain."
FormReceipt's approach of filling and submitting the live public form in a real browser session—matching visitor behavior rather than posting to an API endpoint alone.
Evidence
definitionrelevance 0.94
"FormReceipt uses browser automation to open pages you configure and attempt test submissions, storing run results, screenshots, and timeline events as proof."
FormReceipt ties each saved monitor to a specific page URL so automated checks target the correct visible form on sites with repeated templates or multiple forms.
Evidence
definitionrelevance 0.93
"Each saved form is tied to its page URL so checks stay focused on the right form and do not target a hidden duplicate on the same template."
The practice of repeatedly verifying that a public contact form still submits and that lead notifications reach the intended inbox—distinct from uptime checks and from generic receipt or invoice products.
"FormReceipt is contact form monitoring with proof—not a receipts app and not an uptime ping. We submit your real form on a schedule, save screenshots, and ask your team one question: did the lead notification arrive?"
"Uptime checks only show that a URL or API responds. Manual testing is easy to skip. FormReceipt tests the full form flow on a schedule and confirms inbox delivery, so you catch silent failures status checks miss."
FormReceipt's tiered plans scale by how many contact forms a team monitors. Every tier includes real browser submission, saved proof, and inbox receipt confirmation.
"Annual billing saves 33% (about two months free) versus monthly on paid tiers. All paid plans include daily monitoring by default and customizable schedule time zone and weekdays."
"Free plan: $0 for 1 monitored contact form with 1 browser check per week at your signup weekday and local time, real submission proof, and inbox confirmation. Schedule is fixed at signup—no custom time zone, time, or weekdays."
"Paid plan for 1 monitored form: $12/month or $120/year (about $10/mo billed annually), 3 checks per week, customizable schedule, and enhanced challenge recovery."