the lead automation launch checklist.

Thirty checks for the journey from enquiry to CRM, follow-up and booking. Use this with your team or provider before a new system goes live.

Tick a check after you have evidence of the expected result. Use controlled test contacts and test environments where possible. Do not send test messages to real customers or deliberately disrupt production integrations.

This is a practical starting point, not certification or a substitute for your project’s own acceptance criteria. A checked box means you reviewed an item, not that this page tested your system.

download test log CSV

0 of 30 checks reviewed

Selections last for this page visit. Use the CSV or printout to keep your evidence.

Capture

Test: Submit a controlled test through each live source.

Expected: The enquiry is saved once with the right fields and source.

Test: Replay the same submission reference.

Expected: No duplicate contact, message sequence or sales task is created.

Test: Submit a new request using an existing test contact.

Expected: The history stays connected and the new request gets the correct next action.

Test: Submit with optional fields empty.

Expected: The enquiry is accepted and the missing values do not overwrite good data.

Test: Enter invalid required contact details.

Expected: Useful validation appears; the workflow does not invent missing information.

Test: Simulate failed storage in a safe test environment.

Expected: No false success is shown; an alternate contact route is available.

CRM

Test: Compare every agreed field at source and destination.

Expected: Name, phone, email, request and source land in the intended fields.

Test: Test the agreed matching rules with controlled records.

Expected: Ambiguous cases go to review instead of merging the wrong people.

Test: Test each routing branch and the unmatched case.

Expected: Every actionable lead has an owner or an explicit fallback queue.

Test: Trigger each agreed stage-changing event.

Expected: The stage reflects the real event and does not skip required human decisions.

Test: Open the record as a team member.

Expected: The last event, responsible person and next task are understandable.

Test: Create a lead through the team’s manual process.

Expected: The right workflow runs without relying on a website-only trigger.

Messaging

Test: Submit during and outside normal availability.

Expected: The receipt explains the next step and makes no false callback promise.

Test: Use a controlled invalid destination or test failure.

Expected: A failure is visible to the responsible person and is not counted as a reply.

Test: Test the agreed timezone and permitted sending window.

Expected: Messages respect the specified schedule for the intended recipient.

Test: Review source consent and a controlled opt-out event.

Expected: The message eligibility and suppression rules behave as agreed.

Test: Reply at each relevant step using a test contact.

Expected: The correct sequence stops or hands over; irrelevant reminders do not continue.

Test: Have a team member take over the test conversation.

Expected: The agreed automation pauses or stops and the team can see its state.

Booking

Test: Book through each connected calendar route.

Expected: The CRM and follow-up state reflect the booking once.

Test: Move a test booking to a different time.

Expected: Old reminders are removed or updated and the new time is correct.

Test: Cancel a test booking.

Expected: The stage and follow-up reflect the agreed cancellation process.

Test: Trigger two eligible sequences for one test contact.

Expected: The contact does not receive contradictory messages.

Reliability

Test: Simulate a temporary integration failure safely.

Expected: The error is recorded, assigned and recoverable.

Test: Retry a failed event after restoring the connection.

Expected: It completes without duplicating customer-facing effects.

Test: Check the renewal and failure-alert process for connections.

Expected: Someone knows when access needs attention and how to restore it.

Test: Walk through an outage with the team.

Expected: They can find waiting enquiries and continue manually.

Handover

Test: List the accounts, owners and access roles.

Expected: The business understands who controls data, subscriptions and configuration.

Test: Review a sample workflow change and reversal.

Expected: The previous behaviour can be restored using documented steps.

Test: Read the maintenance agreement with the workflow map.

Expected: Covered systems, support channel and small-change limits are explicit.

Test: Review the completed test log with the owner.

Expected: Failures have owners; accepted limitations and launch decisions are recorded.

how to record the result

In the CSV, record Pass, Fail or Not applicable, the evidence location, an owner and a date. Explain every Not applicable decision. A failure needs a fix or an explicitly accepted limitation before launch.

Keep personal customer data out of shared test logs. Use references to controlled test records rather than copying private conversations into a document.

what to do with a failed check

Start with the earliest point where the observed result differs from the expected result. Confirm whether the event was received, the record was saved and the next action was attempted. Fixing the original handoff is more useful than adding another notification at the end.

For platform-specific behaviour, check HighLevel’s workflow settings documentation. For Australian commercial messaging requirements, refer to ACMA’s guidance.

use it with your next project

You are welcome to share this page with your team or link to it in a project brief. Read our lead automation guide for the reasoning behind the workflow, or talk to ByNoon about the system you need.