Playbook 10one job, start to finish

Find where your web form loses leads with one test lead

"The form's broken" isn't a diagnosis. Send one labeled test lead through four stops and find exactly where it stopped.

By Eric Snyder, founder 2 min readUpdated Oct 6, 2026
Save this guidereceiptsgroup.com/guides/test-lead-four-stops
In this guide
  1. Start here: paste this into ChatGPT or Claude
  2. Why it matters
  3. The steps
  4. Copy this
  5. Example (made up)
  6. Mistakes to avoid

After this you'll be able to find exactly where your web form loses leads, using one labeled test lead and four stops.

Start here: paste this into ChatGPT or Claude

Not technical? Start here. Copy this prompt into ChatGPT or Claude (the free versions work) and it walks you through the whole guide, one step at a time, in plain English. It asks before it assumes anything and checks with you before anything that costs money, reaches a real customer or deletes something. The rest of the page is the same guide, written out, if you'd rather do it yourself.

PromptThe walkthrough prompt (copy all of it)
Hi! Please be my patient guide for this step-by-step guide from Receipts Group: "Find where your web form loses leads with one test lead"
The guide is here: https://receiptsgroup.com/guides/test-lead-four-stops (open it if you can; if you can't, everything you need is below).

About me: I run a small business and I'm not technical. Use plain words and short sentences.

My goal: Find exactly where my web form loses leads, using one labeled test lead and four stops.

How to help me:
1. One step at a time. For each step, tell me in a sentence what it's for and exactly what to do (where to click, what to type, who to ask). Then stop and wait until I say "done" or tell you what I see.
2. Ask before you assume anything about my business, my tools, my team or my numbers. One question at a time.
3. If you use a technical word, explain it in plain English the first time.
4. Stop and check with me before anything that costs money, sends anything to real customers, or deletes anything.
5. Use only what I tell you or show you. Never make up numbers, names, results or quotes. If something's missing, ask me.
6. If I get stuck, or something looks different from what you expected, slow down and try another way.

The steps, from the guide:
Step 1. Make a test lead nobody could mistake for real.
TEST in the name, a fake 555 number, an email at example.com. Tell the team it's coming so it doesn't turn into a real sales task.
Step 2. Stop 1: typing it in, on your phone.
Does every box load and work? Use a weird address on purpose, one the address lookup might not recognize: an apartment number, a brand-new street, a rural route.
Step 3. Stop 2: the "please fix this" warnings.
Leave a box empty. Mistype the phone number. Do the warnings show up, make sense and let you fix it? Then hit send.
Step 4. Stop 3: the saved record.
Find the lead where it's supposed to be stored. Is every answer there, including the address?
Step 5. Stop 4: the team getting it.
Check that the rep who should call it actually got the alert, not just that the record exists.
Step 6. Fix the first stop that failed, then run all four again.
Then close out the test record so it doesn't get counted.

My instinct? Rebuild the whole form. Tempting. Useless until I know where it broke. A completion rate can tell you something deserves attention. Seeing where the record stops tells you what to fix.

When we get to it, use the "Copy this" text from the guide (fill in the blanks and brackets with my details):
---
TEST LEAD (label it so nobody calls it)
Name:    TEST Form Check [today's date]
Phone:   555-0123
Email:   test@example.com
Address: an awkward one on purpose (apartment, new street, rural route)

ON YOUR PHONE, FOUR STOPS
[ ] 1. Typing it in: every box loads and works
[ ] 2. "Please fix this" warnings: they show, make sense, let you fix it
[ ] 3. Saved record: the lead is stored with every answer
[ ] 4. Team got it: the right rep was alerted

First stop that failed: ______________
Fix: ______________
Re-ran all four stops:  [ ]
Test record closed out: [ ]
---

Watch out for these (the guide's mistakes to avoid):
- Rebuilding the form before you know where it broke. You might rebuild the part that worked.
- Testing only on a desktop. Address lookups and warnings can act differently on a phone.
- Using a real-looking test lead. It can get called, booked or counted. Label it.
- Stopping at the thank-you screen. "Thank you" means the visitor finished. It doesn't mean your rep got anything.

When we're done, give me a short recap: what we did, what I decided, and the one thing to check again later.

Start by asking me a few quick questions about my business and what I already have, one at a time. Then begin with step 1.

Why it matters

"The form's broken" is like telling your mechanic, "The car did a thing." It covers two different problems: something stopping the visitor before they hit send, and something losing the lead after the thank-you screen. Same complaint, different fix. The customer saw "thank you." Your rep saw nothing.

The steps

  1. Make a test lead nobody could mistake for real. TEST in the name, a fake 555 number, an email at example.com. Tell the team it's coming so it doesn't turn into a real sales task.
  2. Stop 1: typing it in, on your phone. Does every box load and work? Use a weird address on purpose, one the address lookup might not recognize: an apartment number, a brand-new street, a rural route.
  3. Stop 2: the "please fix this" warnings. Leave a box empty. Mistype the phone number. Do the warnings show up, make sense and let you fix it? Then hit send.
  4. Stop 3: the saved record. Find the lead where it's supposed to be stored. Is every answer there, including the address?
  5. Stop 4: the team getting it. Check that the rep who should call it actually got the alert, not just that the record exists.
  6. Fix the first stop that failed, then run all four again. Then close out the test record so it doesn't get counted.

My instinct? Rebuild the whole form. Tempting. Useless until I know where it broke. A completion rate can tell you something deserves attention. Seeing where the record stops tells you what to fix.

Copy this

Use this test lead and checklist, word for word:

Copy this
TEST LEAD (label it so nobody calls it)
Name:    TEST Form Check [today's date]
Phone:   555-0123
Email:   test@example.com
Address: an awkward one on purpose (apartment, new street, rural route)

ON YOUR PHONE, FOUR STOPS
[ ] 1. Typing it in: every box loads and works
[ ] 2. "Please fix this" warnings: they show, make sense, let you fix it
[ ] 3. Saved record: the lead is stored with every answer
[ ] 4. Team got it: the right rep was alerted

First stop that failed: ______________
Fix: ______________
Re-ran all four stops:  [ ]
Test record closed out: [ ]

Example (made up)

Granite Roofing's office manager says the form's broken. Web leads dried up last week. The owner, Sam, sends "TEST Form Check" from his phone with an apartment address.

Stop 1: the address box suggests a match and fills it in. Fine. Stop 2: he leaves the phone blank and the warning shows. Fine. Stop 3: the record is saved with every answer. Fine. Stop 4: the rep who handles web leads got nothing. The alert was still going to a rep who'd moved to a different role.

It broke after "send." The fix is one setting, not a new form. He changes it, runs all four stops again, and this time the alert lands.

Mistakes to avoid

  • Rebuilding the form before you know where it broke. You might rebuild the part that worked.
  • Testing only on a desktop. Address lookups and warnings can act differently on a phone.
  • Using a real-looking test lead. It can get called, booked or counted. Label it.
  • Stopping at the thank-you screen. "Thank you" means the visitor finished. It doesn't mean your rep got anything.

The headline's probably fine. The lead's just stuck behind "thank you," wondering why nobody called.

Rather skip the setup?

Want help setting this up?

Receipts Group builds these systems. Thirty minutes with Eric tells you which piece is worth building first, or that none of them are. The guides stay free either way.

Keep going

more free guides