A thank-you message does not prove your team received a lead. This walkthrough checks the complete route: the homeowner’s request, the confirmation, delivery, and the person responsible for responding.
You will need a phone, a desktop browser, a test email address you control, and access to the receiving inbox or lead system. Tell your team that a labeled test is coming. Use test details, not a real customer’s information.
Record the form you are testing
List the page address, expected recipient, any lead system, expected confirmation, and response owner. If service pages use different forms, test each distinct configuration. One working homepage form does not prove the others work.
Use a recognizable identifier such as “Website test ; October 30, 10:15” in the name or message field. Record the time and device so the team can trace it.
Complete the form on a phone
Open the live page and follow the same path a homeowner would. Read the offer first: is this a callback request, a booking, or an estimate request?
- Check that every field has a visible, understandable label.
- Try submitting with a required field empty. The page should explain what needs correcting.
- Enter an invalid email format, then correct it. Check that other information is preserved.
- Complete the form with your test details. Confirm the keyboard and buttons do not hide essential controls.
- If an upload is offered, test an allowed file and the guidance for a rejected file type.
Repeat on desktop and navigate the form with the keyboard. If focus disappears or errors are only shown through color, record the problem for the developer.
W3C recommends clear submission feedback and error messages that explain how to correct problems. See its form-notification guidance.
Check what the confirmation actually promises
After a successful test, read the confirmation. It should match what happened. A request received is not an appointment booked unless the system genuinely reserved one.
Example confirmation“Thanks. We’ve received your request about [service]. Our team will contact you during [actual business hours] to discuss the work and next steps. An appointment has not been scheduled yet.”
Use placeholders only while drafting. Replace them with the business’s real process before publishing. A confirmation should not promise a response time your team cannot reliably meet.
Trace the request to a person
Find the same test identifier in the receiving inbox and lead system, if used. Confirm the service, location, contact details, and message arrived intact. Check spam folders and forwarding rules if it is missing.
Ask the assigned person to reply to your test address. Confirm the reply arrives and uses the correct business identity. Test any after-hours routing separately with the team’s agreement.
| Symptom | Investigate |
|---|---|
| Success message, no notification | Saved submissions, mail delivery, recipient settings, spam, or a disconnected integration. |
| Notification, no assigned owner | Routing rules and who monitors the destination. |
| Fields missing from the lead record | Field mapping between the form and receiving system. |
| Two records for one request | Repeated submissions, automation, or duplicate integration triggers. |
Verify tracking without treating the test as a sale
If conversion tracking is installed, ask the person responsible to verify the intended event fires once for the successful request. A button click should not silently stand in for successful delivery. Keep test leads identified so they can be excluded from operational reporting where supported.
Tap the phone link as a separate check. Confirm the correct number opens; coordinate any test call so the team knows it is yours. This verifies the contact path, not your call-tracking configuration.
Keep a short test log
Record the date, page, device, test identifier, confirmation result, destination, owner, and any fix required. After a fix, repeat the failed path and confirm delivery again. Retest after form, email-routing, or integration changes, and include it in your routine website review.
You are finished when the visitor receives accurate feedback, the request reaches the correct place, and a named person can respond.
