Currently, inactivity notifications can only be triggered once based on a single timeframe (e.g., after 5 days of inactivity). Once that notification has been sent, it is not possible to trigger additional inactivity communications at later milestones (e.g., 10 days, 21 days).

From a learner engagement perspective, this creates a limitation.

In practice, re-engagement typically requires a staged approach:

• An initial light reminder (e.g., 5 days inactive)

• A stronger nudge (e.g., 10-14 days inactive)

• A final escalation (e.g., 21+ days inactive)

Without the ability to sequence these notifications, we are unable to implement a structured re-engagement strategy directly within the platform. This forces us to rely on manual tracking or external automation tools, which introduces operational inefficiency and increases the risk of inconsistent learner communication.

Having the ability to configure multiple inactivity triggers for the same enrollment, each tied to different time thresholds, would significantly improve:

• Learner engagement and completion rates

• Retention and course progression

• Operational efficiency

• Communication consistency

This enhancement would align strongly with platforms that support lifecycle-based communication logic and would materially strengthen Cypher’s learner engagement capabilities.