# Launching SunFire from a Contact Record

{% hint style="success" %}
**Audience:** Admins, Developers, <code class="expression">space.vars.automation</code> Builders, Support & Operation teams, and Solution Architects

**Purpose:** Explains how to launch SunFire from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> in <code class="expression">space.vars.Kizen\_company\_name</code> to begin a Medicare quote or enrollment.
{% endhint %}

## Overview

{% hint style="warning" %}
**Caution:** This setup reflects <code class="expression">space.vars.Kizen\_company\_name</code>'s default configuration. Your administrator may have customized your layout, so columns or navigation may appear differently. Trial accounts may have limited features.
{% endhint %}

You can launch SunFire directly from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> in <code class="expression">space.vars.Kizen\_company\_name</code> to start a Medicare quote or enrollment. Launching SunFire from the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> ensures <code class="expression">space.vars.contact</code> information is passed automatically, reducing duplicate entry and keeping enrollment data in sync.

***

## Before You Begin

Before launching SunFire from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>, make sure the following are in place:

* You have access to <code class="expression">space.vars.contacts</code> in <code class="expression">space.vars.Kizen\_company\_name</code>
* 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 <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> includes the required information:
  * First name
  * Last name
  * Date of birth
  * Address

***

{% stepper %}
{% step %}

#### Navigate to **Data** > **Contacts**

{% endstep %}

{% step %}

#### Select a **Contact Record** or create a new one

{% endstep %}

{% step %}

#### Validate **Contact Record** Information

Confirm the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> includes First Name, Last Name, DOB, Address/Zip and Medicare ID\* (recommended).

{% hint style="warning" %}
**Caution:** Medicare ID isn't required to launch SunFire from <code class="expression">space.vars.Kizen\_company\_name</code>, but it is required during the enrollment process.
{% endhint %}
{% endstep %}

{% step %}

#### Select Launch SunFire on the Contact Record

{% endstep %}

{% step %}

#### **Choose to Resume or Start a New Session**

When launching SunFire from a <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code> that has prior session data, <code class="expression">space.vars.Kizen\_company\_name</code> 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 <code class="expression">space.vars.contact</code>'s drugs, providers, and pharmacy to SunFire, replacing the prior session's data with the latest information from the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>. This data is only sent if the CRM Partner ID is filled out; otherwise, SunFire opens an empty session with just the <code class="expression">space.vars.contact</code>'s demographic information.
  {% endstep %}

{% step %}

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

{% endstep %}

{% step %}

#### Run the Medicare quote and complete the enrollment in SunFire.

{% endstep %}

{% step %}

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

{% endstep %}
{% endstepper %}

The completed enrollment appears under SunFire Enrollments on the <code class="expression">space.vars.contact</code> <code class="expression">space.vars.entity</code>.

***

## **Important Things to Know**

* Only completed enrollments are returned to <code class="expression">space.vars.Kizen\_company\_name</code> as Enrollment <code class="expression">space.vars.entities</code>.
* Sessions are captured only when the quote was launched from <code class="expression">space.vars.Kizen\_company\_name</code>.
* 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, <code class="expression">space.vars.Kizen\_company\_name</code> sends the <code class="expression">space.vars.contact</code>'s drugs, providers, and most recent pharmacy to SunFire. If any of these <code class="expression">space.vars.entities</code> cannot be found in SunFire's system, a warning message appears identifying which <code class="expression">space.vars.entities</code> were not matched.
* Provider addresses are filtered before being sent to SunFire. When a doctor has more than one office, <code class="expression">space.vars.Kizen\_company\_name</code> only sends one address to SunFire. <code class="expression">space.vars.Kizen\_company\_name</code> 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, <code class="expression">space.vars.Kizen\_company\_name</code> sends the most recent address instead.
* The first provider address matching the <code class="expression">space.vars.contact</code>'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 <code class="expression">space.vars.Kizen\_company\_name</code>, drugs, providers, and pharmacies are added to the <code class="expression">space.vars.contact</code> but existing values are not removed. A new feature allows users to remove these values directly from the <code class="expression">space.vars.contact</code> page.

***

## What's Next

Next, review [SunFire Integration Data Mapping](/docs/integrations-and-plugins/integrations/sunfire/sunfire-integration-data-mapping.md) to understand what data is shared between <code class="expression">space.vars.Kizen\_company\_name</code> and SunFire. You can also review [SunFire Contact Matching Rules](/docs/integrations-and-plugins/integrations/sunfire/sunfire-contact-matching-rules.md) to see how <code class="expression">space.vars.contacts</code> are matched and how duplicate <code class="expression">space.vars.entities</code> are avoided when enrollment data is returned.

<details>

<summary>Related Topics</summary>

* [SunFire](/docs/integrations-and-plugins/integrations/sunfire.md)
* [SunFire Integration Data Mapping](/docs/integrations-and-plugins/integrations/sunfire/sunfire-integration-data-mapping.md)
* [SunFire Contact Matching Rules](/docs/integrations-and-plugins/integrations/sunfire/sunfire-contact-matching-rules.md)

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.kizen.com/docs/integrations-and-plugins/integrations/sunfire/launching-sunfire-from-a-contact-record.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.