How the At-Risk Workflow Works (Simple Overview)
There are three parts working together:
Tracking check-ins
Flagging members who stop checking in
Keeping track of how long they’ve been inactive
You don’t need to manage these steps manually — they run automatically.
Enabling At-Risk Workflows
To enable the At-Risk workflows in PushPress Grow:
Access the Content Library:
Go to Upgrades and open the Content Library.
Select “Member Workflows” in the category bar at the top of the page. The page scrolls to that section.
Locate and Install the Workflow:
Find the “At Risk” card and click “Install” on the card.
Once installed, the corresponding At-Risk pipeline will also be added to Opportunities.
If the pipeline doesn’t appear immediately, refresh your screen a few times.
Configuring Prebuilt At-Risk Workflows
To configure a prebuilt workflow, such as "At Risk Date Arrives | Alert Staff & Send Message to Client v1.0":
Open the Workflow:
Go to Automation → Workflows and locate the desired workflow.
Set the Trigger:
Configure the trigger to activate when the at-risk tag is applied or when the at-risk date field is reached.
Customize Actions:
Add staff recipients for notifications (email and/or SMS).
Customize the email/SMS content for client messaging.
Verify Sync:
Ensure the Core-to-Grow sync is active so at-risk status and tags populate correctly.
Publish the Workflow:
Click “Publish” to activate the workflow.
Step 1: When a Member Checks In
Any time a member checks in (classes, open gym, or personal training):
The system updates their last activity
Their At-Risk Date is reset
The system adds time (usually 10 days) to that date
If they were marked as at risk, they are removed from the at-risk list
What this means:
If a member checks in, they are considered active and not at risk.
Step 2: When a Member Stops Checking In
If a member does not check in again before their At-Risk Date:
The system flags them as at risk
Your team gets an internal notification
The member is added to an At-Risk pipeline so they can be followed up with
This check runs automatically each morning.
What this means:
Your team is alerted when a member may need attention — without having to watch attendance manually.
Step 3: Tracking How Long They’ve Been At Risk
Once a member is marked at risk, the system continues tracking their inactivity.
Over time, they move through stages such as:
10 days at risk
11 days at risk
12 days at risk
15 days at risk
20 days at risk
30+ days at risk
These stages update automatically as time passes.
What this means:
You can quickly see how long someone has been inactive and prioritize outreach.
What Happens If the Member Checks In Again?
As soon as the member checks in:
They are removed from the at-risk pipeline
Their At-Risk Date is reset
The process starts over if they become inactive again later
What this means:
You’ll never keep chasing someone who has already returned.
Who Does This Apply To?
This workflow applies to members only
Leads or non-members are ignored unless you choose otherwise
Filter by Membership Plans:
Create a Smart List in Contacts with filters for the at-risk indicator and specific membership plans.
Use this Smart List as the entry segment for a workflow.
Exclude Specific Members:
Add an If/Else condition in the workflow builder to filter out members based on plan type (e.g., Open Gym members).
Route these members down a branch that excludes them from the At-Risk list.
Why This Is Helpful
No manual attendance tracking
Automatic alerts for disengaged members
Clear visibility into how long someone has been inactive
Helps your team reach out at the right time
Consolidate Workflows:
Merge messaging and notification steps into a single workflow to streamline logic and avoid conflicts.
Automatic Enrollment:
Once configured, eligible members will be automatically enrolled in the At-Risk workflow based on the criteria set.
Troubleshooting Common Issues
Missing At-Risk Workflow or Pipeline:
Ensure the workflow is installed via the Content Library. If the pipeline doesn’t appear, refresh your screen.
Members Not Appearing in Workflows:
Consolidate member-facing messaging steps into the notification workflow to avoid duplicative automations.

