Don’t test
- Lead risk
- High — silent failures can run for weeks.
- Time & effort
- Low effort now, high cost when leads are missed.
- Consistency
- Unknown.
- Best for
- Not a fit for teams that rely on inbound leads.
Does your contact form still work?
Is your contact form broken?Find out in minutes
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 problem
Uptime checks and thank-you pages do not prove delivery. These are the failures teams notice too late.
sentiment_dissatisfied
The thank-you page can show even when submit fails
Plugin updates, theme changes, and server errors can break submission while the page still says “thanks.”
verified_user
A green check is not proof of email delivery
Many forms show success before mail is sent. The visitor sees confirmation; your inbox stays empty.
account_balance
Missed leads are easy to miss
Nobody gets paged when a form quietly stops working. One lost inquiry can cost more than years of monitoring.
Four ways teams check their contact forms
Test occasionally
- Lead risk
- Medium — issues between checks can still lose leads.
- Time & effort
- Low, but depends on someone remembering to test.
- Consistency
- Inconsistent.
- Best for
- Low-change sites with low lead risk.
Test on a schedule (manual)
- Lead risk
- Lower, if checks stay consistent.
- Time & effort
- High — repeated manual work.
- Consistency
- Good when the process is followed closely.
- Best for
- Teams with dedicated ops time.
FormReceipt (automated)
- Lead risk
- Lower ongoing risk with scheduled real-browser tests.
- Time & effort
- Low after setup.
- Consistency
- Consistent cadence, saved proof, and alerts.
- Best for
- Teams that want reliable checks without manual overhead.
The full path, end to end
1touch_app
We submit like a visitor
We open your page, find the contact form, and send a labeled test submission.
2inventory_2
Proof is saved in your dashboard
Screenshots, timestamps, and run events are stored with every test ID.
3forward_to_inbox
Your team confirms delivery
We email a yes/no question. Your team answers in email or in the dashboard.
4shield_with_heart
Alerts when something breaks
Failed runs or missing confirmations trigger alerts with the details you need.
The inbox check
mark_email_readYes — I received the test email
We mark the run as received. Your dashboard shows a complete, confirmed loop.
notifications_activeNo / not sure
We flag the run, keep the proof, and alert you with a run ID you can share with IT or your host.
Every run leaves a clear record
See what happened, when it happened, and whether someone confirmed the lead email arrived.
Sample run timelineID: FR-99281-X
08:01 AMTest journey started
08:02 AMForm fields detected
08:02 AMSubmission finished in-browser
08:03 AMSuccess screen & network proof saved
08:03 AMConfirmation email queued to your teammate
08:18 AMTeammate confirmed inbox receipt
08:18 AMRun marked as received in dashboard history
08:19 AMWeekly reliability trend updated for this form
Example scenarios
Instead of guessing whether last week’s test worked, we open one timeline and see exactly what happened.
— Example: ops team with multiple sites
We used to hear about broken forms from customers. Now the run history shows the failure before anyone notices missing leads.
— Example: engineering team, B2B site
Every run already has screenshots and timestamps, so sharing proof with a client or host takes minutes—not a Slack scavenger hunt.
— Example: agency managing client forms
One yes/no in the inbox replaces the manual “did the test email arrive?” check support used to do every morning.
— Example: support team, daily checks
Pay for how many forms you monitor
Billing period for plan prices
30-day money-back guaranteeCancel anytimeSame verification workflow on every paid plan
Feature
Free
$0
Most teams start here
Paid
Monitored forms
$10/mo
$120 billed annually
- Monitored forms
- 1
- 1
- Checks / week
- 1
- 3
- Custom schedule
- Not included
- Included
- Browser + inbox proof
- Included
- Included
- Enhanced challenge recovery
- Not included
- Included
- Money-back guarantee
- —
- Included
Credit card required. Your account is created at checkout; new users get a set-password email. Cancel anytime.
FAQ
Common questions before you start
FormReceipt is for teams that rely on contact-form leads. If demos, quotes, or support requests come through your form, you need proof it submits and the notification reaches your inbox—not just a page that loads.
How do I know my contact form still works?
FormReceipt opens your page in a real browser, fills and submits the form, saves screenshots, then asks your team yes/no: did the lead notification arrive? That loop proves the form still delivers—not just that the page loads.
How is this different from pinging my form endpoint or using a basic uptime monitor?
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.
Is it acceptable to send automated tests to production forms?
Only monitor sites and recipients you own or are authorized to test. Test traffic is clearly labeled so it can be identified in logs.
What happens when a run fails or someone answers “no” to delivery?
We keep the evidence, send alerts based on your settings, and save a timeline your team can share with IT or your host to fix issues faster.
How do pricing plans map to real teams?
All paid plans include the same verification flow. Plans mainly differ by how many forms you need to monitor. Upgrade anytime from Pricing or your billing settings; the free plan stays available if you do not need daily checks yet.
Start with one form, free
Set up your first monitor in minutes: real browser runs, saved proof, and inbox confirmation on the free plan. Upgrade when you need daily checks on more forms.
Start free todayNo credit card required · Free plan always available