Medicare and Retirement Pipelines
When you mark someone as "Attended Meeting" in Eventfull, the system automatically sends a follow-up sequence. This targets attendees who did NOT fill out a contact card at the event — people who showed up but left without booking a next step.
Each pipeline has its own copy. The compliance disclaimer populates automatically based on the pipeline — no manual action needed.
How It Works
Pipeline | Emails | Timing |
Medicare | 1 email | 3 hours after marked "Attended Meeting" (business hours) |
Retirement | 3 emails | 3 hours, 24 hours, 50 hours |
Important: If someone filled out a contact card at the event, move them to "Appointment Booked" instead. That stops this sequence from firing.
Medicare Pipeline
Email 1 — 3 Hours After Status Update (Business Hours)
Hi [Registrant Name],
It was a pleasure having you at our recent Medicare seminar — thank you for taking the time to attend. I hope the information we shared was helpful and gave you a bit more clarity around your Medicare options.
If any questions have come up since the seminar, or if you'd like to talk through your situation one-on-one, I'm happy to help. Simply reply with a quick "Yes" or "No," and we can take it from there — no pressure at all.
My goal is to make this process as clear and comfortable as possible for you.
I look forward to hearing from you.
Warm regards,
[your name & location]
[your email signature]
[your Medicare email and website disclaimer]
Retirement Pipeline (F1.0)
Email 1 — 3 Hours After Status Update (Business Hours)
Hi [Registrant Name],
It was great having you at our recent retirement seminar! I hope you found the information helpful.
If you have any questions or want to chat more about your retirement options, just reply with a quick "Yes" or "No."
I'd love to help make things as easy as possible for you.
Looking forward to hearing from you,
[your name & location]
[your email signature]
[your Medicare email and website disclaimer]
Email 2 — 24 Hours After Email 1
Hi [Registrant Name],
I wanted to follow up in case you missed my last email. I know how overwhelming retirement decisions can be, and I'd love to help simplify the process for you.
If you're open to chatting, just reply with a quick "Yes" or "No," and we can go from there.
Looking forward to hearing from you,
[your name & location]
[your email signature]
[your Medicare email and website disclaimer]
Email 3 — 50 Hours After Email 2
Hi [Registrant Name],
I just wanted to check in one final time to see if there's anything I can do to help with your retirement planning questions or decisions. I know it can be a lot to navigate, but you don't have to do it alone — I'm here if you need guidance or support.
If you'd like to chat, just reply with a simple "Yes" or "No," and we can take it from there. No pressure, just here to help when you're ready.
Take care,
[your name & location]
[your email signature]
[your Medicare email and website disclaimer]
What You Need to Do
Update your pipeline the same day. The 3-hour window is intentional — the event is still fresh. Every hour you wait, the lead gets colder.
When You Update | Result |
Same day | 3x more appointments |
2–3 days later | Response rates drop significantly |
Never | Nothing triggers — no follow-up happens |
When someone replies "Yes" — respond the same day. Get them on the calendar.
When someone replies "No" — the system closes the loop and stops messaging them. No action needed.
No reply after all 3 emails — move them to Long-Term Nurture. They attended, which means they had a reason for being there. The nurture sequence keeps you top of mind until they're ready.
Pipeline Stage Reference
Stage | Who Goes Here | What Triggers |
Attended Meeting | Everyone on your sign-in sheet | Post-event sequence fires in 3 hours |
Appointment Booked | Anyone who filled out a card at the event | Stops appointment request sequence |
Did Not Attend | Registered but didn't show | Separate re-engagement sequence fires immediately |
For questions about your pipeline setup or sequence status, submit a support ticket.
