Engagement Intelligence Score (EIS)
The EIS is Bliply's proprietary member engagement metric. It predicts retention risk by analysing multiple behavioural signals, giving you a single score from 0 (high risk) to 100 (highly engaged) for every member.
What EIS Measures
The score is calculated from a weighted combination of:
- Attendance frequency — How often the member attends classes relative to their membership credits
- Attendance consistency — Regular weekly patterns vs. sporadic visits
- No-shows — bookings where the member was never checked in before the check-in window closed
- Booking behaviour — Advance bookings (positive signal) vs. last-minute or frequent cancellations
- Membership tenure — Longer-tenured members typically have higher engagement
- App interaction — Usage of the member app (viewing workouts, checking schedule, tracking progress)
- Payment history — Consistent payments vs. failed or late payments
EIS Recalculation
Scores are recalculated automatically on a daily schedule (03:00 UTC). Changes appear the following day.
Retention Dashboard
The retention dashboard (Retention / EIS) provides:
- Risk Segments — Members grouped into four categories:
- At Risk (0–25) — High churn probability. Immediate intervention recommended.
- Declining (26–50) — Engagement trending downward. Monitor closely.
- Stable (51–75) — Consistent engagement. Low risk.
- Thriving (76–100) — Highly engaged. Strong retention signal.
- Trend Charts — EIS distribution over time, showing whether your gym's overall engagement is improving or declining.
- Member List — Sortable list of all members with their current EIS, trend direction, and last visit date.
Using EIS with Automations
Create automation flows triggered by EIS thresholds. For example:
- "When EIS drops below 30 → Send re-engagement email → Wait 5 days → If no attendance → Send coach outreach task"
- "When EIS rises above 80 → Send congratulations message"
Milestone & Expiry Notifications
The system also sends automated notifications for membership milestones (e.g. 1-year anniversary) and upcoming expiry dates, which are configured separately from EIS-triggered automations.