Who we enroll, and who we leave out
Reactivation is for people who already raised a hand and then went quiet. Everyone else is left out on purpose, so the message fits the person reading it.
- In: contacts with a recorded opt-in, shown in our builds by a previous opt-in tag.
- In: contacts with no activity for 90 days or more.
- Out: anyone in a closed stage, won or lost.
- Out: anyone still in the opt-in nurture, so nobody gets two sequences at once.
- Out: anyone who never opted in, however long ago they reached you.
Quiet for 90 days is not permission. The opt-in is what puts a contact on the list.
Two different clocks
HighLevel's Stale Opportunities trigger measures how long a deal has gone without progress or updates in one stage. You set it with Duration in Days, In Pipeline and Pipeline Stage. It answers the question of which deals are stuck.
That isn't the same as a quiet contact. A deal can sit in one stage while the contact is replying to texts every week. Our own design counts quiet across the whole contact, not time in a stage. Pick the clock that matches what you mean, because the two will enroll different people.
Building the list and the workflow
For a contact-wide rule, start from a Smart List. Contact Smart Lists add and drop records on their own as filter matches change, and the filters can combine tags, custom fields and engagement activity.
- Create a contact Smart List and join the eligibility filters with AND: the opt-in tag, no closed stage, not in the opt-in nurture, and quiet for your chosen period.
- Go to Automation > Workflows, click + Create Workflow, then Start from scratch.
- If you mean deals stuck in a stage instead, choose the Stale Opportunities trigger, use Add Filters for the duration, pipeline and stage, and click Save Trigger.
- Turn on Stop on Response in the workflow settings if a reply should end the sequence.
- Before anyone real enrolls, check how your account treats a contact who qualifies a second time.
Before the first text goes out
When reactivation goes out as a bulk text wave, we turn Conversation AI off first. People who answer a message about something from months ago deserve a person reading their reply, not an assistant answering on the business's behalf.
We don't treat a tag on its own as proof of consent. This guide isn't legal advice, and what your contacts agreed to, and for which messages, is a question for your own counsel before the wave goes out.
Rather have it set up for you?
We'll agree who qualifies, build the list and the workflow that reaches them, and route replies to a person, all planned on a 30-minute 1:1 with Rob first.