Sample deliverable
Contact Funnel QA Report
Fictional example for an AI automation agency contact form. This is the shape of the USD 75 deliverable: one public funnel, evidence, lost-lead risk and exact retest steps.
Verdict
Fail before paid traffic. The visible page says the form submitted, but the backend returns a server error, so the buyer-facing success state is not reliable evidence that a lead reached the agency.
Evidence table
| Check | Observed evidence | Result |
|---|---|---|
| Public URL | https://example-ai-agency.test/contact loaded a contact form with name, email and message fields. |
Pass |
| Required fields | Email and message were required. Phone was optional and left blank. | Pass |
| Backend endpoint | POST to /api/contact returned HTTP 500 with Internal Server Error. |
Fail |
| Visible page state | The page still displayed Thanks, we will contact you soon after the failed backend response. |
Fail |
| Analytics signal | A tracker request returned HTTP 202, but this was not a lead-delivery endpoint. | Warning |
Lost-lead risk
- High: the agency may believe inquiries are arriving when the backend is failing.
- High: paid traffic and cold outreach could produce invisible lost leads.
- Medium: analytics events can create a false positive in reports.
First fix
Change the submit handler so the success state only appears after the real backend endpoint returns a 2xx response. On non-2xx responses, show a visible error, log the response body server-side and keep the form data in the browser so the visitor can retry.
Retest steps
- Submit a test lead with phone blank if phone is optional.
- Confirm the contact endpoint returns HTTP 200 or HTTP 201.
- Confirm the success message appears only after that 2xx response.
- Confirm the lead arrives in the expected destination: email, CRM, Slack, Sheet, Airtable, Notion or webhook log.
- Submit one intentionally invalid email and confirm validation blocks it before any backend send.
Client-safe note
We found and fixed a form-delivery issue before launch. The contact funnel now waits for backend confirmation before showing success, and failed submissions produce a retryable error instead of a false positive. This reduces the risk of silent lost leads during launch.
Buy this check
The real USD 75 check covers one public funnel and includes one retest pass after the first fix within 7 days.