01Inventory the actual lead paths.
List each public page, form plugin, form identifier and recipient. Two pages that look similar may use different forms or notification rules. Record required fields, consent controls, conditional branches and the mobile layout. Identify which paths are covered by monitoring and which still require manual testing.
02Agree synthetic data and routing.
Use clearly labelled test values and a mailbox your team controls. Agree how test enquiries will be identified and handled by the client. Avoid using real lead content in screenshots or logs. Decide whether a CRM or autoresponder will run before sending the test.
03Exercise the configured fields.
Enter ordinary valid values in every required field. Check text, email, telephone, textarea, select, checkbox and radio inputs when present. Record the selected options and conditional route. A passing default route does not qualify file uploads, CAPTCHA, payment steps or another branch that was never exercised.
04Record each result separately.
Capture the visible confirmation, matching WordPress processing result and any separately checked inbox message. If tracking or CRM checks are included, give each its own expected result. Link the evidence to one test reference so the client can understand what the check established.
05Repeat after meaningful changes.
Repeat the baseline after changes to the theme, form fields, mail routing, caching or consent setup. Compare with the previous record and update selectors or expectations when the intended form changed. Monitoring should be requalified when its configuration no longer describes the page.
06Hand over an actionable report.
Include the URL, configuration, test time, stages checked, observed result, unresolved items and responsible person. Show missing evidence as unconfirmed. Schedule checks according to the agreed service and review who receives alerts. LeadUptime provides scheduled checks and private expiring reports; each customer configuration still needs qualification.