Automations are now Agentic Workflows! Same setup, smarter execution. Multi-step processes handled automatically, end to end.
See our Release Notes
Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Launching SunFire from a Contact Record

Audience: Admins, Developers, Agentic Workflow Builders, Support & Operation teams, and Solution Architects

Purpose: Explains how to launch SunFire from a Contact Record in Kizen to begin a Medicare quote or enrollment.

Overview

Caution: This setup reflects Kizen's default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.

You can launch SunFire directly from a Contact Record in Kizen to start a Medicare quote or enrollment. Launching SunFire from the Contact Record ensures Contact information is passed automatically, reducing duplicate entry and keeping enrollment data in sync.

Before You Begin

Before launching SunFire from a Contact Record, make sure the following are in place:

  • You have access to Contacts in Kizen

  • The SunFire integration is enabled and configured, including the required partner_id and partner_app_id

  • For customers using token-based authentication, the crm_partner_id must be configured on the SunFire business plugin

  • The agent must have generated their SunFire authentication code and saved it to their employee record (applies to token-auth customers only)

  • The Contact Record includes the required information:

    • First name

    • Last name

    • Date of birth

    • Address

1

Navigate to Data > Contacts

2

Select a Contact Record or create a new one

3

Validate Contact Record Information

Confirm the Contact Record includes First Name, Last Name, DOB, Address/Zip and Medicare ID* (recommended).

Caution: Medicare ID isn't required to launch SunFire from Kizen, but it is required during the enrollment process.

4

Select Launch SunFire on the Contact Record

5

Choose to Resume or Start a New Session

When launching SunFire from a Contact Record that has prior session data, Kizen displays a modal with two options:

  • Resume prior session: Continues the existing SunFire session using data previously saved in the session. Use this option to pick up where you left off without overwriting any changes made in SunFire.

  • Create new session: Sends the current Contact's drugs, providers, and pharmacy to SunFire, replacing the prior session's data with the latest information from the Contact Record. This data is only sent if the CRM Partner ID is filled out; otherwise, SunFire opens an empty session with just the Contact's demographic information.

6

In the new browser tab, sign in to SunFire with your credentials.

7

Run the Medicare quote and complete the enrollment in SunFire.

8

Close the SunFire tab and return to the Contact Record in Kizen.

The completed enrollment appears under SunFire Enrollments on the Contact Record.

Important Things to Know

  • Only completed enrollments are returned to Kizen as Enrollment Records.

  • Sessions are captured only when the quote was launched from Kizen.

  • If you don’t see an enrollment, confirm that you completed the SunFire enrollment (not just a quote) and that your SunFire integration is enabled and configured correctly.

  • When creating a new session, Kizen sends the Contact's drugs, providers, and most recent pharmacy to SunFire. If any of these Records cannot be found in SunFire's system, a warning message appears identifying which Records were not matched.

  • Provider addresses are filtered before being sent to SunFire. When a doctor has more than one office, Kizen only sends one address to SunFire. Kizen picks the first address that matches the client's ZIP code. This stops the same doctor from showing up twice, but it might not always be the office the client actually goes to. Pharmacies work differently; for those, Kizen sends the most recent address instead.

  • The first provider address matching the Contact's ZIP code is sent, which prevents duplicate doctor entries but may not always send the preferred address if a provider has multiple locations in the same ZIP.

  • Session data (drugs, providers, pharmacy) is only sent to SunFire for customers configured with token-based authentication. If your integration does not support this, only demographic data is passed on launch.

  • When an enrollment is returned to Kizen, drugs, providers, and pharmacies are added to the Contact but existing values are not removed. A new feature allows users to remove these values directly from the Contact page.

What's Next

Next, review SunFire Integration Data Mapping to understand what data is shared between Kizen and SunFire. You can also review SunFire Contact Matching Rules to see how Contacts are matched and how duplicate Records are avoided when enrollment data is returned.

Related Topics
PreviousSunFireNextSunfire Integration Data Mapping

Last updated

Was this helpful?