To keep your standard pipelines clean, we created a Long Term Nurture pipeline to monitor and maintain communication with recruits who are in a holding pattern or who aren’t ready to take the next step in their licensing journey or with Keller Williams.
Long-Term Nurture Pipeline: Not In School (NS), In School (IS), Licensed Agent (EX) #
These three stages provide a centralized system for long-term follow-up with recruits, allowing leaders to maintain engagement based on recruit type while tracking progress with automated cadence reminders and auto-expire settings. While in this stage, recruits are added to a follow-up cadence based on the setting in their recruit card (Weekly, Bi-Weekly, Monthly, or Quarterly), and it lasts according to the Auto-Expire setting within the recruit card (3, 6, or 12 months). The leader will receive reminders according to the assigned cadence to maintain follow-up. Once Auto-Expire reaches 30 days, the Opportunity is moved to the Expired Nurture stage and the assigned leader is prompted to determine next steps.
Click here to learn more about these three stages.
Expired Nurture (Last 30 Days) (3.0) #
This stage serves as a final 30-day window for long-term nurture recruits who have reached the end of their Auto-Expire period, giving leaders the opportunity to take action before the recruit is automatically dropped from the pipeline. At this stage, the leader should review the Cadence and Auto-Expire values, adjust them if necessary, and move them back to the appropriate NS, IS, or EX stage if they wish to continue outreach. Otherwise, the recruit is automatically dropped from the pipeline and no further communication will take place.
Click here to learn more about this stage.
Exit Pipeline #
This is a holding stage that a recruit enters briefly when moving between pipelines but starting in the Long Term Nurture Pipeline. Make sure to use the Exit Pipeline process to make sure a recruit doesn’t end up in the Holding Stage. Use this process to move a recruit from the LTN pipeline to the related applicable pipeline.
Click here to learn more about this stage.
Holding Stage #
If a recruit ends up here, it’s typically due to an error when moving the recruit between pipelines. When this happens, an internal notification will be sent to the assigned user with details pertaining to the why the recruit landed here, along with pertinent information pertaining to the recruit, where they were coming from, and where they were headed.
Click here to learn more about this stage.
