Sunfire Contact Matching Rules

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

Purpose: Explains the rules Kizen uses to match Contact data returned from Sunfire to existing Contact records.

Overview

When Sunfire returns session or enrollment data, Kizen applies a defined set of contact matching rules to determine whether the incoming data should update an existing Contact or create a new one. These rules are evaluated in priority order to ensure the most accurate match and reduce the risk of duplicate records.

If none of the matching rules result in a match, Kizen creates a new Contact record using the returned data.

Note: These matching rules apply only to Contact data received through the Sunfire integration. Other integrations may use different matching logic.

Why Matching Matters

Accurate contact matching ensures enrollment and session data is applied to the correct Contact record, helping prevent duplicate Contacts and keeping customer data consistent across Kizen and Sunfire.

Contact Matching Rules

Priority	Matching Rule	Behavior
1	Exact Contact ID match	Update the existing contact record.
2	Email match	If the date of birth, Medicare ID, and first name match also match, update the existing contact. Otherwise, if there is is a mismatch on a secondary field, then exclude the email field from future contact updates or creations.
3	Medicare ID match	Update existing contact record. Updates the existing contact email if the email is present, but no match was found in the last step.
4	Phone Number + First Name match	Compare the phone number to both the mobile and home phone number in Kizen. If multiple matches are found, the first record is used.
5	Last Name + Carrier match	If email, medicare, and phone are all blank, then we use Last Name + Carrier as a fallback due to the absence of secondary identifiers.
6	Create New Contact	Update the existing contact or create a new contact using LastName + Carrier (if all secondary identifiers are missing).

Note: These rules apply only to contact data received through the Sunfire integration. Other integrations may follow different matching logic.

---

What's Next

If you need additional context, you can review other Sunfire documentation to better understand the full integration, including launching Sunfire from Contact records and how data is exchanged between Kizen and Sunfire during quoting and enrollment workflows.

Related Topics

• Sunfire

• Launching Sunfire from a Contact Record

• Sunfire Integration Data Mapping