Feature Ideas

I would love if there were a way to send a monthly report to clients about the uptime of their form. Something like the number of tests and the percentage of successful ones. This would be ideal to integrate with something like WPRemote or WPUmbrella that can feed CheckView data into the monthly reports we are already sending.

The more sites we add, the more effort we have to spend when we want to change the schedule of the test runs. It would be super handy if there is a bulk update feature where we can update all flows or just selected ones in bulk.

Currently, when creating or editing a test schedule, users can only select one day of the week (for weekly) or one day of the month (for monthly). It would be helpful to allow multiple selections for these options, for example, running a test every Monday and Thursday, or on the 1st and 15th of each month. It would be nice if we could: • Replace the existing single-select dropdown with a multi-select dropdown or checkbox list. • Support selecting multiple days in both “Weekly” and “Monthly” schedule types. • Display selected days clearly in the schedule summary for clarity.

When downgrading to a lower plan, it would be helpful to have a grace period before losing access to higher-tier features. This way we have time to adjust our test flows and settings rather than having everything change immediately.

When a test fails, I have to search through the documentation to find the relevant help article. It would be much faster if the error message pointed me directly to the right troubleshooting doc so I can resolve issues quickly.

Our form uses an image as the submit button instead of a regular button, and CheckView does not recognize it during step generation. It would be great if the step generator could detect and handle image-based submit buttons in forms.

Can CheckView test more than just forms and WooCommerce? We need to test login pages, search functionality, and our LMS platform too. It would be great if AI could automatically generate test steps for these different types of flows based on the page content.

After rebuilding or retrying a test flow, I have to manually unpause it every time. It would save a lot of time if test flows automatically unpaused when I rebuild, retry, or re-initialize WooCommerce for that flow.

When our tests fail because of a security plugin or firewall, the error messages are not always clear about what is blocking them. It would help to automatically detect exactly which security plugin is causing the issue and point us to the right whitelisting steps.

When a test fails, it is not always obvious why. It would be helpful to have an AI-powered analysis that explains what happened, identifies the likely cause, and suggests specific steps to fix it, ideally with links to relevant help documentation.

It would be amazing if CheckView could automatically audit our website pages for UX and conversion rate optimization issues. Something that takes screenshots of our pages and uses AI to identify usability problems, accessibility issues, and conversion blockers with actionable recommendations.

Summary Please add support for verifying database submissions that include country-coded phone numbers (e.g., +41, +49, +1). Currently, CheckView does not support database verification for these formats, requiring the verification step to be disabled. Context This request arises from troubleshooting a Gravity Flow form where database verification had to be disabled because CheckView could not validate the country-coded phone number stored in the submission. Problem When Gravity Forms submissions use phone fields with country codes, CheckView is unable to validate the phone number stored in the database. This limitation prevents end-to-end verification for forms that rely on international phone formatting, which is common for multilingual or multinational websites. As a workaround, the database verification step must be disabled, reducing the reliability of automated tests. Enable CheckView to: Correctly interpret and validate phone numbers that include country codes.Match database-stored phone numbers regardless of formatting variations (e.g., spaces, parentheses, prefix symbols).Allow the database verification step to remain active for forms using international phone fields. Benefits Full E2E verification for Gravity Forms and other form systems using international phone input fields. More robust and globally compatible automated testing.

It’d be great if I could pick a specific device to test on (like iPhone 15 Pro, Galaxy S24, or iPad) instead of only having the generic mobile or desktop options. This would help simulate real-world scenarios more accurately.

It’d be amazing if CheckView had an REST API so I could trigger tests or pull results automatically.

It would be helpful to have a button or link directly on each Test Flow page that allows users to open a support ticket related to that specific flow: • Add a visible “Open Support Ticket” button/link on the Test Flow detail page. • The button should link to the CheckView support/contact form. • Pass relevant query parameters (e.g., Flow ID, Flow Name, Org ID, etc.) in the URL so the ticket form is auto-filled with context from the specific test flow. • Include a subject prefix like “Issue with Test Flow: [Flow Name]” to streamline support intake.