Convert
Perimenopause symptom-screen to eligibility
A woman who's been told her broken sleep, low mood, and brain fog are "just stress" lands on a menopause program and has no idea she's exactly who it's for.
What it does
Perimenopause is widely under-recognized: symptoms get dismissed as stress or aging, and primary care often misses them because menopause care is thinly covered in standard medical training. So a woman arrives at a hormone program with the very symptoms it treats and bounces, because nothing told her this was a real, treatable thing rather than something to push through. The agent meets her with a structured symptom screen that names the pattern she's been living with, validates that it has a name and a path, and converts that recognition into the intake and baseline-eligibility step. It never diagnoses — it frames what she's describing and routes her to the clinical assessment that can.
How it works
- 1Trigger. a visitor lands on the menopause or hormone program and engages with educational content or a "could this be perimenopause?" prompt without entering intake.
- 2Decision. the agent runs a structured symptom screen — sleep, mood, cycle changes, brain fog, hot flashes — recognizes the perimenopause pattern, and frames it as common and treatable, carefully staying on the side of recognition rather than diagnosis.
- 3Action. it reflects the pattern back ("what you're describing is something this program treats"), answers the "is this normal / is this me?" doubts in place, and invites her into the conversational intake and the baseline-eligibility step.
- 4Follow-through. an engaged prospect flows into intake with her screen answers carried forward so nothing is re-asked; anything that reads as a medical red flag rather than typical perimenopause is routed to a clinician, and the eligibility and prescribing decision always stay clinician-side.
Configuration
How the agent is wired for this use case.
screen_started behavioral signal.- Messaging channel · run the structured symptom screen as a conversation and validate the pattern in plain language.
- Knowledge base · sequence the validated perimenopause screening questions and the recognition-not-diagnosis framing.
- App backend · carry the screen answers into the conversational intake so nothing is re-asked, and start the baseline-eligibility step.
- CRM · record the screen outcome and engagement so the prospect can be followed up on consented channels.
What you need
The inputs this use case runs on. Your channels stay yours; the agent supplies the judgment.
Signals
screen_started and per-answer events, content-engagement events on menopause material, screen-to-intake transition.
Data
the validated perimenopause screening logic and red-flag rules, the program's eligibility criteria, consent state, anything already known about the prospect.
Guardrails
detect-and-escalate clinical policy — recognition and framing only, no diagnosis, no condition stated as fact; judge review on outbound messages; explicit consent before follow-up; the screening logic is clinician-owned; every screen outcome logged for audit.
Metrics it moves
- conversion-rateup, by turning an undertreated "I didn't know this was a thing" visitor into a started intake instead of a bounce.
- intake-completionup, because a prospect who arrives already recognizing herself as a candidate carries that intent through the eligibility step.
- revenue-per-conversationup, as a single recognition conversation opens a program enrollment that would otherwise never have begun.
Related use cases
Conversational hormone intake with baseline-lab gate
the intake and lab step this screen feeds into
Conversational intake and eligibility check
the general intake pattern, here preceded by symptom recognition
Free-to-paid nudge in the care chat
the adjacent motion of converting an unrouted health question into care
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