Where did that lead go? Test the whole handoff.

What is a lead-handoff test?

A lead-handoff test follows one controlled inquiry from the public form to the person responsible for responding. It checks whether the right information arrives, whether someone owns the next action, and whether failures are visible. A successful form submission alone does not establish any of those things.

This is a reference procedure to adapt to your own systems, not a report of a workflow we tested in your account.

Write down what should happen before you click

Choose an internal test address you control and mark the submission as a test. Record the expected destination, required fields, owner, response deadline, and notification channel. Tell the receiving team what you are testing. Use a test environment where available; a production test should have an agreed cleanup plan and must not trigger outreach to real customers.

1. Submit the form once and record its confirmation and timestamp.
2. Find the saved record. Check the name, contact details, source page, consent choice, and creation time.
3. Confirm the assigned owner and the task or queue they actually use.
4. Check the notification provider result, then check delivery in the intended inbox. Provider acceptance and inbox delivery are different observations.
5. Have the owner find the record and identify the next action without your help.

Test the cases a polished demo misses

In a safe test environment, try a repeated submission, missing required information, an unavailable destination, and a notification failure. A repeated event should not create two follow-up tasks. A missing field should produce a useful correction. A failed destination should leave a recoverable record and a visible issue for an owner.

For example, an illustrative agency inquiry might be saved correctly but remain unassigned because its service choice does not match a routing rule. Fix the rule and replay that record after checking whether any downstream steps already ran.

Keep a compact evidence log

For each step record: expected result, actual result, timestamp, record ID, evidence location, and owner. Keep personal information out of screenshots and shared notes. Automately’s Lead Journey Monitor helps you record manual observations; it does not automatically test your inbox or run scheduled checks.

Download the workflow acceptance workbook and use the same checkpoints after changing a form, integration, or routing rule.

When is the handoff ready?

Ready means your agreed normal and failure cases pass, the owner can recover a failed record, and you know where to inspect the next failure. Record the date and systems tested. One passing sample is evidence about that sample, not a guarantee that every future lead will arrive.

Need help defining or repairing the process? Bring the evidence log to a One Workflow Sprint discussion.