Connect your first website
- Add your website. Use the public WordPress URL and the client name you want to see in your workspace.
- Install the companion plugin. Download the LensShift WordPress plugin, then upload it under Plugins → Add new in WordPress.
- Pair the website. Copy the Site ID and monitoring address shown in LensShift. Generate a unique shared secret, save the same secret on both sides, and enable the forms you authorize LensShift to test.
- Configure a monitor. Select a discovered form, enter its public page URL, map synthetic values, and set its success message and schedule.
- Run a check. Use “Run check now” and review the browser and email results. Verify that test notifications reach your normal recipient as expected.
The monitoring address must be configured by the LensShift operator before delivery checks can work. If setup reports that email verification is unavailable, contact support instead of entering a made-up address.
Supported forms and boundaries
The companion plugin discovers Contact Form 7, WPForms, and Gravity Forms. Start with a standard single-page enquiry form using text, email, telephone, textarea, select, checkbox, and radio controls supported by the monitor.
CAPTCHA, payment, file-upload, conditional, password-protected, and multi-step forms may be excluded or require additional validation. Discovery is not proof of compatibility: complete an on-demand check before relying on a schedule.
A monitor covers one selected form on one page. Multiple forms should be configured as separate monitors. Forms must belong to a website you own or are explicitly authorized to test.
Choose safe synthetic data
Use a clear name such as “LensShift monitoring test” and a message explaining that no reply is needed. Avoid real customer information, phone numbers that belong to another person, and addresses that could trigger unrelated communications.
Tests follow the ordinary notification path. They can create CRM entries, fire automations, affect analytics, or produce client notifications. Review those integrations and agree on test handling with the client before enabling a schedule.
Do not bypass anti-abuse controls on unrelated websites. If an authorized form cannot be tested safely, pause its monitor and use another verification process.
Read browser and email results separately
- Passed: the browser confirmed submission and a matching monitoring email was received.
- Submission failed: the form gave an actionable rejection or failure response.
- Delivery missing: submission succeeded, but no monitoring email matched within the delivery window.
- Inconclusive: a browser, network, provider, or configuration issue prevented a reliable result.
- Pending: the check is queued, running, or waiting for email.
A passing receipt verifies the monitoring mailbox. It does not prove delivery to the client’s normal inbox, validate every possible visitor input, or guarantee continuous uptime between checks.
Investigate a failed or delayed check
WordPress cannot connect
Confirm the plugin is active, the Site ID is exact, the shared secrets match, and the public WordPress REST API is reachable. Security plugins may need an explicit rule for the LensShift status route.
The form cannot be submitted
Open the page manually. Check that the configured form still exists, fields and select options have not changed, and the success message matches the current form response. Review the available screenshot on the monitor.
Submission passed, email is missing
Check the ordinary recipient inbox, WordPress mail settings, SMTP credentials, provider logs, and filtering rules. Confirm the plugin’s monitoring recipient matches the configured inbound mailbox. WordPress reporting a send does not establish receipt.
Monitoring is delayed
Check the monitor is active and your subscription permits monitoring. Review service readiness. A delayed check is not evidence that the client’s form failed.
An incident remains open
An incident resolves after a complete passing check. Fix the underlying form or mail configuration, then run a new check. Contact support with the incident reference if you need help.
Alerts and client reports
In Settings, choose your alert email and optionally add Slack, Discord, or an approved webhook URL. Send a test notification before relying on incident alerts. Incident and recovery preferences can be enabled separately.
Actionable failures receive a confirmation run before opening an incident. A complete pass records recovery. In Reports, choose a client and month to create a browser-readable report or PDF. Reports describe observed checks and incident intervals, not guaranteed uptime. Starter reports retain LensShift branding. Agency and Studio can enable white-label reports in Settings.
Plan limits and billing changes
Starter includes 3 websites and 3 monitors, Agency includes 10 of each, and Studio includes 20 of each. Additional monitors cost $5 per month each and can only be used on websites within your plan’s fixed website limit.
In Billing, upgrades start after successful payment. Downgrades and monitor reductions are scheduled for the next billing period. Cancel renewal to stop future recurring charges while keeping access until the current period ends. Trials have an explicit cancellation action and do not charge automatically unless you complete a paid checkout.
Keep monitoring data minimal
Use synthetic data only. Monitoring copies include a unique correlation reference. LensShift stores check and delivery metadata rather than retaining full enquiry bodies. Failure screenshots may capture visible page content; treat them as private operational evidence.
Pairing secrets are stored encrypted in the application. Never include credentials in form values, support messages, or screenshots. Read the Privacy Policy and Acceptable Use Policy.
Need a hand? Contact LensShift support.