Engage / Lifecycle
Phase-aware proactive hero card on a cycle log
She logs that her period started and opens the app to a card that already knows what her next phase will feel like — and what to do about it.
What it does
A cycle tracker that only stores logs is a passive utility, and passive utilities get forgotten. The highest-engagement surface in a femtech app is the home screen right after the user logs something, but most apps answer a log with a static chart. This replaces that dead end with a phase-aware hero card: the moment a user logs a period start, a symptom, or crosses into a new cycle phase, a fresh card appears that speaks to where she is in her cycle and taps straight into an advisor conversation. It makes the tracker feel like a knowledgeable companion that is always one step ahead — the post-log home screen is the category's highest-engagement moment, and a phase-aware card is the proven way to own it.
How it works
- 1Trigger. a cycle-log or phase event from the app backend — a logged period start, a symptom or mood entry, or a transition into a new predicted phase.
- 2Decision. the agent reads the user's cycle context and remembered preferences, drafts a short phase-aware card for the moment, and a quality judge scores relevance, timing, and tone, dropping anything that does not clear the bar.
- 3Action. the card renders on the home screen ("you're in your luteal phase — here's why energy dips this week and what tends to help"), and a tap opens straight into the advisor chat rather than a static screen.
- 4Follow-through. if the moment passes or the user has already seen this phase's card, the surface is suppressed rather than repeated; taps and follow-on conversations write back to analytics, and lift is measured against the templated baseline.
Configuration
How the agent is wired for this use case.
period_logged, a symptom or mood entry, or a phase_changed transition.- App backend · ingest the triggering log and phase events and receive taps and conversations back for measurement
- Memory store · read cycle context, current and predicted phase, and remembered preferences to ground the card
- In-app hero-card surface · render the phase-aware card at the home-screen moment and open it into live advisor chat
- Knowledge base · ground the phase-specific guidance the card and the chat draw on
- Messaging channel · deliver an optional phase-aware push to bring the user back to the card
What you need
The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.
Signals
cycle-log and phase events (period_logged, symptom/mood entries, phase_changed), plus app-open and quiet-hour signals
Data
current and predicted cycle phase, per-user log history, remembered preferences, notification consent and device tokens
Guardrails
judge review of every card and push with "don't show" as a first-class outcome; trends-and-wellness framing only, never diagnosis or medication; frequency caps and quiet hours; suppression of stale or already-seen cards
Metrics it moves
- dau-mauup, as each phase event becomes a session that starts in conversation instead of a glance
- click-through-rateup, because a card written for her current phase beats any templated banner
- churndown, as a tracker that anticipates her cycle becomes a companion she keeps rather than abandons
Related use cases
Cycle-phase prediction push
the prediction-timed sibling that fires before a log, not after
Hormone-result interpretation grounded in trend history
the results-moment surface the advisor chat leads into
Proactive bubbles and personalized push
the generic recent-activity pattern this specializes for cycle phases
See it on your own customer journey
Bring one drop-off, one churn cliff, or one silent segment. We will show you what a proactive agent with memory and judgment does with it.
Book a demo