Anu Agency
PlaybookWork with Anu
07.08 Test the whole chain with one fictional lead

07.08

Test the whole chain with one fictional lead

Walk a test lead from form to weekly report, record the result at every hop, and fix the first break before anything else.

50 minFramework and examplesChecked 2026-10-20

Video walkthrough

Coming soonFollowing Jordan Testlead through the entire system
It will cover
  1. Why you test the chain, not the pieces
  2. Set up the test lead and the tracking table
  3. Hop by hop: what you should see and where
  4. Use the simulator to find the first break
  5. Clean up, then repeat after every change and once a month
This chapter is complete without it. Every step is written out on this page.

What you're building

A repeatable end-to-end test: one fictional lead, eleven hops, an expected result at each hop, and a tracking table you fill as you go. You also get the lead journey simulator, which shows where the chain breaks and what is cut off downstream from your answers.

Why it matters

Each connection can pass on its own while the chain fails, for example when the form works and routing works, but routing never sees the form's leads because the workflow filters a different form. Only a single lead walked end to end proves the system works.

Integrations also break silently: a form gets replaced, a Google connection expires, a provider changes its email format. A monthly run of the same test catches that before real leads are lost.

What you need

  • Chapters 1 to 6 of this part set up (or the parts you use)
  • Your test lead: Jordan Testlead, an email alias such as you+test0001@yourdomain.com, your own mobile number
  • The downloadable checklist below, printed or open on a second screen
  • About 50 minutes, plus a check the next day for reminders

Time and cost

Time
50 minutes, then 20 minutes monthly
Cost
$0 (a few cents of texting)

Text messages to your own phone are billed at your normal per-message rate.

Step by step

  1. Prepare the test lead and the tracking table

    Download the checklist. Use a fresh email alias number each run (+test0001, +test0002) so you can tell runs apart. Note the date and who is running the test.

    Check: The checklist header has the date, the tester, and the alias used.

  2. Hops 1 to 3: capture, source and consent

    Submit your website form in a private window with consent ticked. Start a timer. Expected: the contact exists within 2 minutes, the source reads exactly as planned, and SMS consent = Yes is on the record.

    Check: Write the minutes, the source text and the consent value in the table. Any mismatch is a fail.

  3. Hops 4 to 6: assignment, alert and first follow-up

    Expected: the contact is assigned by your rule within a minute, the agent receives the alert within 5 minutes, and the first follow-up reaches your phone. Then repeat hop 1 with a new alias and consent unticked: expected result is no text message at all.

    Check: Two rows: consent Yes received a text; consent No received none. If the consent-No lead got a text, stop and fix it before any live traffic.

  4. Hops 7 to 9: booking, confirmation and calendar

    Book through the link in the follow-up, using the same email and phone. Expected: the appointment attaches to the same contact, a confirmation arrives right away, the reminder arrives at your set time, and the appointment shows on the agent's Google or Outlook calendar at the right time.

    Check: One contact (not two), one appointment, confirmation time and reminder time written in the table.

  5. Hop 10: the weekly numbers

    Open your sheet or report. Expected: one lead and one booked appointment, under the right source. After the appointment time passes, mark it Showed (or set the outcome) and confirm the held count changes.

    Check: The sheet shows the test lead under its source, and the held count rose by one after you set the status.

  6. Hop 11: clean up and record the run

    Cancel the appointment, tag the contact test-lead, and archive or delete it according to your CRM's practice. Make sure your report filters exclude the tag. Save the filled checklist with the date.

    If any hop failed, enter your answers in the simulator above the template, fix the first break it names, and run the whole test again. Fixing a later break first wastes time, because the lead may never reach it.

    Check: The test contact is tagged and excluded from reports, and the dated checklist is saved.

What success looks like

  • All eleven hops pass in one run, with times recorded.
  • The consent-No lead received no text.
  • The run is saved, and a monthly repeat is on your calendar.

Copyable templates

CSVEnd-to-end test checklistEleven hops with what to do, the expected result, and where to look in HighLevel and Follow Up Boss. Open in Google Sheets or Excel and fill Pass/Fail and times.
csvTest run log (one line per run)
Date,Tester,Alias used,Hops passed (of 11),First failed hop,Fix applied,Re-test date,Re-test result

Try it

Lead journey simulator

Answer from what you saw in your own test. Fictional test lead: Jordan Testlead.

Your CRM
1. Form to CRMWhen you submit your own website form, does a new contact appear in the CRM within 2 minutes?
2. Lead sourceDoes that contact show the exact lead source you expect (for example 'Website - Home value form')?
3. Consent recordedDoes the contact record show the lead's answer to your text-message consent checkbox?
4. Assigned to an agentIs the contact assigned to the right agent automatically, with no one touching it?
5. Agent alertedDoes the assigned agent get an alert (text, app push or email) within 5 minutes?
6. First follow-upDoes the first follow-up message go out, and only by text when consent was recorded?
7. Appointment bookedCan the test lead book through your calendar link, and does the appointment attach to the same contact (no duplicate)?
8. Confirmation and reminderDoes the lead receive a booking confirmation and a reminder before the appointment?
9. Agent calendarDoes the appointment appear on the agent's Google or Outlook calendar?
10. Shows in the weekly numbersDo the lead and the appointment show up in your weekly report or tracking sheet under the right source?
Hops passed0/10
Breaks0
Never reached0

No breaks reported yet, but some hops are untested. A hop you have not tested is not working until you see it work.

HopResultWhat it means
Form to CRMNot testedNot tested yet. Run this hop with your test lead and answer again.
Lead sourceNot testedNot tested yet. Run this hop with your test lead and answer again.
Consent recordedNot testedNot tested yet. Run this hop with your test lead and answer again.
Assigned to an agentNot testedNot tested yet. Run this hop with your test lead and answer again.
Agent alertedNot testedNot tested yet. Run this hop with your test lead and answer again.
First follow-upNot testedNot tested yet. Run this hop with your test lead and answer again.
Appointment bookedNot testedNot tested yet. Run this hop with your test lead and answer again.
Confirmation and reminderNot testedNot tested yet. Run this hop with your test lead and answer again.
Agent calendarNot testedNot tested yet. Run this hop with your test lead and answer again.
Shows in the weekly numbersNot testedNot tested yet. Run this hop with your test lead and answer again.

Answer from what you saw in your own test. The simulator shows the first break and every hop the lead can no longer reach.

1 Form to CRM
2-3 Source + consent
4 Assigned
5 Agent alerted
6 First follow-up
7 Booked
8-9 Confirmed + synced
10 In the numbers
  • 1 Form to CRMto2-3 Source + consent
  • 2-3 Source + consentto4 Assigned
  • 4 Assignedto5 Agent alerted
  • 4 Assignedto6 First follow-up
  • 6 First follow-upto7 Booked
  • 7 Bookedto8-9 Confirmed + synced
  • 8-9 Confirmed + syncedto10 In the numbers
The eleven hops

How to test it

This chapter is the test. To test the test, deliberately break one hop (for example, unpublish the routing workflow or remove the agent from the round robin), run the checklist, and confirm the failure shows up at that hop. Then restore it and run once more.

Troubleshooting

Everything passed, but real leads still go missing.

Real leads come from more sources than your test used. Run the test once per source (website, Meta testing tool, each portal) and compare.

The reminder never arrived, but everything else passed.

Reminders depend on timing settings and on the appointment still being active. Check the Reminder timing in the calendar's notifications, and that you did not cancel the test appointment before the reminder time.

The test lead keeps appearing in weekly numbers.

Your report does not filter the test-lead tag. Add the filter to every report and sheet formula, or use a dedicated test source name and exclude it.

Advanced technical details

Optional. You can follow every step above without these.

Technical detailsAutomating the monthly test

Technical teams can script hop 1 (a POST to the form endpoint, the HighLevel Inbound Webhook, or Follow Up Boss /v1/events with a test tag) and read back hops 2 to 4 by API. Keep the human checks for hops 5, 6, 8 and 9, because they test what a person and a phone actually receive.

For Follow Up Boss, test events should use an occurredAt of now: events older than a day are treated as historical and do not trigger automations. For Meta, use the Lead Ads Testing Tool or POST /{FORM_ID}/test_leads, deleting the previous test lead first.

Sources

A method with illustrative numbers. Replace the examples with your own. Last checked 2026-10-20.