FOR SITE OWNERS
“It’s been unusually quiet.”
A quote request, consultation enquiry or project brief is how your next customer gets in touch.
Run a known test before assuming that a quiet inbox means no demand.
EPIC CHECKS IN THE MAKING
Your site is live.
Does it still
work?
The page loads. The form looks fine. But is the enquiry actually reaching you?
We’re exploring a WordPress tool that tests the journey from contact form to inbox — so a quiet inbox doesn’t hide a broken form.
Concept stage. No payment. Help shape what we build.
Epic ChecksCONCEPT PREVIEW
EXAMPLE SITEStudio & Co.
Website onlineOnline isn’t the whole story.
The form accepted our test. Delivery wasn’t confirmed.
Contact page openedThe page responded successfully
PassedTest enquiry submittedThe form showed a success message
PassedNotification receivedNo confirmation in the test window
UnconfirmedTHE USEFUL BIT
See which step needs attention.
Not just another green uptime light.
Illustrative results · No real website is being monitored
STARTING WITH ONE IMPORTANT JOURNEYContact page → Form submission → Notification delivery
THE GAP BETWEEN “UP” AND “WORKING”
A broken form doesn’t
always look broken.
You shouldn’t have to wait for a customer to tell you they couldn’t get in touch.
01 / THE FALSE GREEN LIGHT
The site is responding.
That tells you a page is available. It doesn’t tell you whether someone can send an enquiry.
02 / THE MISSING MESSAGE
“Sent” isn’t “received”.
A success message and a delivered notification are two different things. We want to check both.
03 / THE MANUAL ROUTINE
Another site to check.
Testing forms by hand takes attention — especially when you’re looking after client websites.
WHAT YOU’D ACTUALLY GET
“Something broke” isn’t enough.
Show me where to look.
The proposed report turns a failed check into a useful starting point for you or the person maintaining your site.
ILLUSTRATIVE REPORT / EC–0042
Needs investigationContact form · Request a quote
Studio & Co. / contact page / authorised test
OBSERVED IN THIS EXAMPLE
The form accepted the enquiry.
Delivery is unconfirmed.
A success message appeared after the test submission. No matching notification was observed at the configured test destination within five minutes.
StepEvidenceResult
01 · OpenContact page loaded; form foundPassed
02 · Submit“Thanks for your enquiry” displayedPassed
03 · VerifyNo matching test notification observedUnconfirmed
What this does — and doesn’t — tell you
The form submission worked in this example. The missing confirmation needs investigation: delivery may have failed, been delayed, or the verification setup may be wrong. This is not proof that every customer email is lost.
PROPOSED ALERT / SAMPLE COPY
The useful details. Before you open WordPress.
The alert should identify the site, form, last completed step and a link to the evidence. Delivery would use a separately configured channel, not rely on the site’s own mail function.
Studio & Co. needs a look.The quote form accepted a test, but notification delivery wasn’t confirmed. Start with notification settings and mail logs.
Check EC–0042 · Sample alert, not a real incident
THE PROPOSED WORKFLOW
Don’t just ping it.
Put it through
its paces.
A focused check of what a visitor actually needs to do. Here’s the experience we want to build.
Help us get the first version right →01
Choose a form. Approve the test.
Connect a supported form and explicitly authorise a clearly marked test enquiry. Safe handling of test submissions is a launch requirement.
02
Follow the journey.
Check submission and notification delivery separately. Delivery verification needs its own setup; a success message alone won’t count.
03
Get evidence, not guesswork.
See where the check stopped and get an alert through a separately configured channel. Recent changes can offer context — not proof of the cause.
WHERE THIS EARNS ITS PLACE
For the sites where
an enquiry matters.
Not another dashboard to watch. A way to make an important maintenance check repeatable.
FOR FREELANCERS
“The update is done. Is the form okay?”
You’ve changed a theme, updated a plugin or adjusted mail settings. Loading the homepage is only part of the handover.
Use a repeatable form check as one part of your post-change checklist.
FOR AGENCIES
“Which client site needs attention?”
Across several sites, manually sending and tracking test enquiries becomes a recurring job.
Our longer-term direction: scheduled checks and a shared view of results. First, make one site’s check dependable.
THE PRODUCT PLAN
A specific first version.
A reason to keep using it.
The value isn’t a one-off test script. It’s a maintained check, understandable evidence and a routine you can repeat as your site changes.
One site. One form.
An end-to-end check.
- Select a supported form and explicitly approve testing.
- Check required fields and the submission result.
- Verify a matching notification at a configured test destination.
- Separate failed, passed and unconfirmed steps in a readable report.
- Rerun the same check after you’ve investigated.
Initial form integrations are not chosen yet. Tell us which tool you use when you join.
Make it a routine,
not a reminder.
- Scheduled checks with a visible last-run time.
- Alerts and recovery notices through a separate channel.
- Run history to compare before and after changes.
- A multi-site view for people maintaining client sites.
Exploration, not a committed roadmap. Frequency, alert channels and pricing are still open.
What we won’t pretend to solve.
Not universal compatibility. Custom forms, CAPTCHA, payment forms and complex automations need explicit support. Unsupported journeys should be flagged, not silently “passed”.
Not a guarantee about every inbox. A verified test destination doesn’t prove delivery to every recipient or every spam folder.
Not automatic repair. A report should help you investigate. It shouldn’t change settings, roll back plugins or claim a recent update caused the problem.
Not permission to create real leads. Test marking and exclusion from sales, CRM and customer automations must be validated before a form is eligible.
“COULDN’T I BUILD THIS WITH AI?”
You could build a test. Would you want to maintain it?
If you have a reliable script and someone owns its upkeep, you may not need us. Epic Checks is for people who want supported integrations, clear failure evidence and a testing routine maintained for them. That’s the standard this product has to meet — not simply wrapping an AI prompt in a plugin.
Tell us if that’s worth building →HELP SHAPE EPIC CHECKS
Would you trust
a quiet inbox?
If this is a problem you’d like solved, join the list. We’ll share progress and invite people to early testing when there’s something ready to try.
Managing client sites?
Tell us how many, and which form tool you use. That will help us choose what to support first.
No launch date yet. No payment details. No plugin to install today.
A FEW STRAIGHT ANSWERS
Before you join.
Can I install Epic Checks now?
Not yet. This is a concept landing page to find out whether the problem matters enough to build for. The dashboard above is a mockup, not a working product.
Which form plugins will it support?
We haven’t chosen the initial integrations. Your answers on the waiting list will help us prioritise. We won’t claim support until we’ve tested the actual submission and delivery journey.
Will test submissions create real leads?
They must be clearly identified and kept out of real customer workflows. Safe setup and explicit permission are requirements for the proposed product, not something this mockup already does.
How much will it cost?
Pricing isn’t set. Joining is free and doesn’t commit you to buying anything. We’ll explain any proposed paid plans before asking you to try them.
Looking for an existing download or article? Plugin collection →WordPress journal →