visibility_offDon’t test
High — silent breaks can run for weeks; real inquiries may never reach you.
Feels free until a lost lead costs hours of firefighting and reputation repair.
Unknown — you’re assuming the form and mail path never drift.
Nobody who depends on inbound leads staying reliable.
event_availableTest occasionally
Medium — you may catch big outages, but failures between checks still lose leads.
Low day-to-day, but someone must remember to run a real end-to-end test each time.
Spotty — confidence depends on how often tests actually happen.
Rarely changing sites where “we’ll check when we remember” is acceptable.
calendar_monthTest on a schedule (manual)
Lower if the habit sticks — still vulnerable during busy weeks when checks slip.
High — repeated staff time, calendar discipline, and follow-through under pressure.
Good only when the process doesn’t slip; proof is often scattered across people and tools.
Teams with dedicated ops bandwidth and strong internal routines.
smart_toyFormReceipt (automated)
Lower ongoing risk — scheduled real-browser submits, saved proof, and inbox yes/no.
Minimal after setup — automation runs the test; your team answers one simple question.
Consistent cadence, artifacts on file, and alerts when something looks off.
Teams who want receipts and calm without babysitting every form.