Clients often enroll weeks or even months before their coverage starts; for example, during AEP, an application submitted in October may not be effective until January 1. The New Plan Submitted campaign closes that gap, so your client hears from you the same day you submit their application instead of waiting for the effective date.
As soon as an enrollment application is recorded for a contact in your Spark account, a two-email sequence is routed to the client in your branding:
Day of submission: Email 1 confirms the application was submitted and sets expectations for what arrives in the mail
14 days after submission: Email 2 checks in while the application is still pending
Both emails are agent-branded using your Spark marketing profile, and both are available in English and Spanish based on the contact's language preference.
How this works with New Plan Enrollment: New Plan Submitted covers the window between application submission and coverage start, setting expectations for what the client will receive in the mail. The New Plan Enrollment campaign picks up once coverage is live. The effective date is the handoff between the two campaigns, and agents can decide to opt into each individually.
Opting in
Activate this engagement under Client Retention in Back Office. Make sure your marketing profile is complete as your logo, branding, and agency info are pulled from it for every engagement.
Which clients receive these emails?
A contact is included when:
You've opted into the campaign
The contact has an application submitted through Sunfire that hasn't gone effective yet
The contact has a valid email address on file and hasn't opted out of emails
The contact's preferred language is supported (English or Spanish)
Clients can opt out of this campaign individually from their communication preferences, and global email opt-outs and bounces are always respected.
NOTE: this campaign will only be triggered for plans submitted through Sunfire integration to ensure communication is tied to an accurate submission date.
When the campaign stops
The campaign covers the window before coverage begins. Spark re-checks the plan's effective date before each send:
Email 1 always sends. It's the immediate confirmation that the application went in.
Email 2 only sends while the application is still pending. If coverage has already gone live, Email 2 is cancelled. In the case that you are also opted into the New Plan Enrollment campaign, a postcard and email communications will then be sent as a part of this campaign which is triggered on effective date.
This also handles effective dates that shift after submission the check happens at send time, not at submission.
Email Correspondence
Email 1: day of submission
Subject:
ENG: Your Medicare plan is submitted
SPA: Su plan de Medicare ha sido enviado
Body (ENG):
Hi {contact.preferred_name},
Thank you for trusting me with your Medicare enrollment, I've submitted your plan for {plan_name}!
Here's what happens next:
{carrier_name} will process your plan and confirm your enrollment.
You'll receive a confirmation letter, your member ID card, and a summary of your benefits in the mail.
Your coverage begins {effective_date}.
I'll be here throughout the process, so please don't hesitate to reach out if anything comes up.
Thank you again for letting me help with your coverage!
{agent.name}
Licensed Insurance Agent
{agent.office_phone}
{agent_license_number}
Email 2 — 14 days after submission
Subject:
ENG: Following up on your Medicare enrollment
SPA: Seguimiento a su inscripción de Medicare
Body (ENG):
Hi {contact.preferred_name},
I wanted to check in and thank you again for trusting me with your Medicare plan. Your plan for {plan_name} is with {carrier_name}, and they'll confirm your enrollment and send your member ID card and welcome materials in the mail.
If you have any questions about your plan, benefits, or what to expect next, please do not hesitate to reach out. I'm always happy to help. Just reply to this email or give me a call.
Have a great rest of your week!
{agent.name}
Licensed Insurance Agent
{agent.office_phone}
{agent_license_number}
