SunFire
Audience: Admins, Developers, Agentic Workflow Builders, Support & Operation teams, and Solution Architects
Purpose: Explains the SunFire integration in Kizen and how it supports Medicare quoting and enrollment workflows.`
Overview
SunFire integrates with Kizen to connect Medicare quoting and enrollment workflows directly to Contact Records. This integration allows agents to launch quotes and enrollments from within Kizen, with Contact information passed automatically between systems.
By keeping Contact and enrollment data aligned, the integration reduces duplicate entry, supports accurate Record matching, and helps agents work more efficiently without switching between platforms.
What is SunFire?
SunFire is a Medicare quoting and enrollment platform used by health insurance agents to compare plans, generate quotes, and submit enrollments across multiple carriers. It serves as a centralized solution for evaluating coverage options and managing the Medicare enrollment process.
SunFire is widely used in the Medicare industry to support accurate plan comparisons and streamlined enrollment Workflows.
How does the SunFire Integration Work?
The SunFire integration allows health insurance agents (HIAs) to start a Medicare quote directly from a Contact Record in Kizen. Kizen automatically passes the Contact’s basic demographic details to SunFire, reducing manual data entry and ensuring data consistency between platforms.
Once SunFire receives the Contact details, the remainder of the quoting and enrollment process takes place inside the SunFire application. When the HIA completes the enrollment, SunFire sends the completed enrollment data back to Kizen and matches it with the original Contact Record.
Integration Workflow Overview
Launch SunFire from a Contact Record in Kizen
Kizen → SunFire
Kizen opens SunFire in a new browser tab and passes the Contact’s basic demographic information (name, date of birth, and address). This eliminates duplicate entry and prevents typos.
Complete the enrollment in SunFire
SunFire → Kizen
When the enrollment is submitted, SunFire sends the enrollment details back to Kizen. Kizen creates a SunFire Enrollment Record and links it automatically to the Contact.
Resume an existing or incomplete SunFire session
Kizen ↔ SunFire
Kizen retrieves prior SunFire session data (providers/drugs/pharmacy) if the session was originally started from Kizen. This enables the HIA to pick up where they left off without losing progress.
Send session data to SunFire
Kizen → SunFire
When starting a new session, Kizen sends the Contact's drugs, providers, and pharmacy to SunFire. This ensures SunFire has the most current Contact data for accurate plan matching and quoting.
Caution: Kizen only retrieves full SunFire session data when the quote or session was started from Kizen. If the HIA starts a quote directly in SunFire, Kizen retrieves only the completed enrollment, not the full session history.
SunFire Requirements
To Enable SunFire on your Platform, contact Kizen Customer Support.
To view plans and run quotes inside SunFire, the agent must launch the Kizen session with a ZIP Code. SunFire uses the ZIP code to determine available plans.
CRM Partner ID Configuration
Certain SunFire customers require a crm_partner_id to be configured in the SunFire business plugin. This ID enables the token-based authentication flow used to send drug, doctor, and pharmacy data between Kizen and SunFire on behalf of the agent.
The crm_partner_id is typically provisioned automatically when SunFire is enabled on your Platform.
Token-Based Authentication (Required for Certain Customers)
For customers configured with a crm_partner_id, SunFire uses a multi-step token exchange to authenticate the agent. This allows Kizen to act on behalf of the agent when sending or retrieving session data.
Agents must complete a one-time setup to generate their authentication code. A modal will automatically pop up the first time you launch SunFire if you have a crm_partner_id and are missing the CRM connect code:
From the Kizen modal, follow the link to your SunFire profile page and log in if prompted.
Navigate to your SunFire profile and copy the authentication code.
In Kizen, paste the code into the CRM Connect Code field on your employee Records and select SAVE.
Note: Without a valid authentication code, agents cannot send session data (drugs, providers, pharmacy) to SunFire.
Enrollments in SunFire
SunFire requires the following fields before an enrollment can be submitted:
Address
Gender
Date of Birth
Medicare Number (MBI)
If any of these are missing, the agent cannot complete and submit the enrollment.
SunFire Contact Matching
SunFire uses the Medicare Number (MBI) as the primary matching field. For more information on Contact matching, See Sunfire Contact Matching Rules.
What's Next
Next, continue to Launching SunFire from a Contact Record to learn how to start a Medicare quote or enrollment directly from a Contact and pass Contact data into SunFire automatically.
Last updated
Was this helpful?