Operations
When should generator lead follow-up stop?
Check what happens when a buyer replies, books or asks to stop. Make sure the right person takes over the next step.
Pause the old follow-up when a buyer replies or a person takes over. Stop requests to book a step once it is booked. A stop request must reach the owner of contact choices.
Check both parts: did the old message stop, and did the right person get the next task? Use your current system owner. This does not grant new contact rights.
On this page
Map the four exit points
Write down which set of messages handles each lead. Then name what should pause or end that set.
A reply is one event. A booking is another. A request to stop has its own meaning. Pass it to the person who handles contact choices.
- Buyer replies with a question.
- Buyer books the next step.
- Buyer asks to stop contact.
- A named person takes over the conversation.
Check the human handoff too
Messages may stop while the reply sits unread. These are two checks. Ask who sees the reply and who answers it.
Give the owner a backup when away. Keep the buyer’s words, last promise and contact choice with the handoff. Do not start a second sequence to fill a gap in staff cover.
Use safe made-up cases
Walk through the rules in a test area with fictional records. Keep tests away from real leads, sales totals and ad events. Do not message real people to see what happens.
If there is no safe test area, review the rules on paper first. Let the system owner decide how to check them.
Check that old follow-up stays off
A later record edit should not undo a saved stop choice. Ask the owner what happens when a lead is moved, imported or given to new staff.
Add a human takeover case to the test sheet. The old flow pauses. The named person gets the latest note. Neither change proves the buyer has been reached.
Save what actually happened
For each case, write what should happen. Then write what did happen and who checked it. A setting switched on is not the same as a passed test.
If something fails, fix the narrow rule with the owner. Recheck that case before relying on it. This is a workflow check, not a claim that a tool alone makes every message appropriate.
Watch and learn
Stop the old flow when a person replies
This older demo shows a reply moving to a human owner. Test the stop and the human handoff separately in your own approved setup.
Selected section: 5:31–6:16.
This is a clip from an older lesson. Use the steps on this page for the current task. The full video may include old offers or advice. The tool shown does not prove the same settings or consent apply in your account.
Loading this video connects to YouTube. The player stays off until you choose to load it.
Sources and further reading
Sources checked .
