Never Reuse the Same Test Contact
Command note: the automation passed every test and failed on the first real lead. The test was the problem.
We checked a new intake sequence on the contact record we always use for testing. It ran clean. The first actual lead got nothing.
That record was carrying things a new lead never has:
• Tags left over from earlier tests, one of them an exit condition
• A previous enrollment in the same workflow, so re-entry rules applied
• DND switched on during a test months ago
• Fields already filled, so a "field updated" trigger never fired
• An assigned user, so the assignment step had nothing to do
None of that surfaces as an error. The workflow quietly skips a step, exits early, or takes a different branch, and still reports success.
Do this on the next test:
1) Create a brand new contact — never reuse an old one.
2) Give it a real address you can open (plus-addressing works fine).
3) Enter it through the actual door — submit the form, do not add the tag by hand.
4) Read the enrollment history, not just your inbox. Confirm which steps ran.
5) Delete it when you are done, so it never becomes next month's dirty test record.
A contact that has been through your account is not a new lead. It is a veteran, and veterans get treated differently.
0
0 comments
Jerry Relth
3
Never Reuse the Same Test Contact
powered by
GHL Command
skool.com/ghl-command-5986
The AI operator's room for GoHighLevel agencies.
Build your own community
Bring people together around your passion and get paid.
Powered by