How to activate and configure the agency-level SunFire integration in AMS+ (Admin only)

This article explains how to activate and configure the agency-level SunFire integration in AMS+.

The SunFire integration must be activated in your agency’s AMS+ account before users can configure their user-level SunFire settings or start quotes.

Requirements

• You must be the Account Owner of your agency’s AMS+ account to activate the integration.
• You must be logged into AMS+ as an Agency User.
• You must be assigned to a Security Group with the Manage Users permission to access, edit, and deactivate the SunFire integration.

About SunFire

SunFire offers two platforms: Blaze Connect and Blaze. This integration supports Blaze Connect only. If you have questions about your platform or access, contact your SunFire representative.

With this integration, users can securely transfer Individual Records and Sales Records from AMS+ to SunFire for quoting and enrollment. After an enrollment is completed in SunFire, the Individual, Carrier Product, and Policy data is sent back to AMS+.

There is no additional cost to your AMS+ subscription to use this integration.

Once activated:

• Users can configure their SunFire integration settings to assign Servicing Agents to Policy Records created from SunFire enrollments.
• Users can start quotes for Sales Records and Individual Records in AMS+.

Activate the integration

You must be the Account Owner in AMS+ to activate this integration.

Go to My Agency Settings > Third Party Integrations > SunFire.

Select Add to AgencyBloc...

Set up the enrollment sync.

Save.

Deactivate the integration

Go to My Agency Settings > Third Party Integrations > SunFire.

Select Deactivate in the top-right corner.

Review and confirm the confirmation message.

Deactivating the integration prevents users from sending records to SunFire. Existing synced data in AMS+ is not removed.

Set up the enrollment sync

Recommended preparation

For a smooth and optimal setup:

• Review Carrier Records and Carrier Products in AMS+ and compare them to your carriers and plans in SunFire.
  • Carrier names and plan names must match.
  • If they do not match, duplicate Carrier Records or Carrier Products may be created.
  • It is recommended to update names in AMS+ to match SunFire.
• Some SunFire data can be stored in Policy Custom Fields. Consider creating Policy Custom Fields for:
  • Enrollment Confirmation Number
  • Plan ID

SunFire to AMS+ terminology mapping

In SunFire, an enrollment includes a beneficiary and Medicare plan. In AMS+, a beneficiary is the equivalent of an Individual Record and a plan is the same as a Policy Record.

How enrollment data sync works

When SunFire sends enrollment data to AMS+, AMS+ places the data based on your integration settings.

Individual Records

• By default:
  • AMS+ attempts to match SunFire beneficiaries to existing Sales Records first.
    • If a match is found, the Sales Record is converted into an Individual Record.
    • If the Sales Record is linked to an existing Individual Record, it is merged into that Individual.
• If no Sales Record is found, AMS+ attempts to match an existing Individual Record.
  • First by unique AMS+ identifier in the URL.
  • Then by First Name, Last Name, and Date of Birth.
• If no match is found, a new Individual Record is created.

Depending on your integration settings:

• You may update all Individual fields, or
• Update only address fields.

See what Individual fields are updated.

Note: You can’t start a profile in SunFire and send it to AMS+. The profile must originate in AMS+.

Carrier Products

If Carrier Product sync is enabled:

• AMS+ attempts to match SunFire plans to existing Carrier Products by Carrier Product Name.
• If no match is found, a new Carrier Product may be created depending on your Carrier Product Sync settings.

See what Carrier Product fields are updated.

Carrier names received from SunFire can’t be remapped. The Carrier name is used exactly as received from the API.

Policy Records

By default:

• AMS+ creates a new Policy Record for each SunFire plan.
• AMS+ attempts to match the carrier by Carrier name.
  • If no match is found, a new Carrier Record is created using the SunFire carrier name.
  • If a match is found, the existing Carrier Record is associated with the new Policy Record.

Policy Custom Fields and optional settings determine whether:

• Enrollment Confirmation Number populates a Policy Custom Field and/or Policy Number.
• Plan ID populates a specified Policy Custom Field.
• Carrier Products are matched by Plan Name or Plan Name + Plan ID.
• Pay Frequency is populated.

Attachments and files are not included in the sync.

See what Policy fields are populated.

Technical data mapping from SunFire to AMS+

Data syncs after an enrollment is completed in SunFire.

Note: Prescription and provider data sync one-way from AMS+ to SunFire and are available only on Accelerate and Elevate subscription packages. Before completing enrollment in SunFire, update prescriptions and providers in AMS+. See How to start quotes using the SunFire integration in AMS+ for more information.

Individual Records

*If we don’t find the home phone, we’ll try the cell phone. If we don’t find the cell phone, we’ll try the business phone.
**When creating/updating an Individual, we’ll use the Address Type specified in the integration settings.
***If creating a new Individual, the default will be Yes, is Primary. If adding a new address to an existing Individual, the default will be Yes, is Primary.
****If updating an existing Individual, we’ll try to match with an existing address. We will match on Zip Code and house number (house number will be defined as the first set of characters before the first space). If the address matches, we will not update anything. If the address does not match, we will add an additional address to the Individual Record. If creating a new Individual, we will add a new address to the Individual Record.
*****For new Individual Records only. See this article for more on assigning the Servicing Agent.
******Prescription and provider data sync one-way: from AMS+ to SunFire. Before completing a lead profile’s enrollment in SunFire, update its linked AMS+ record’s prescriptions and providers to keep these details current in both systems.

Only address fields:

*When creating/updating an Individual, we’ll use the Address Type specified in the integration settings.
**If creating a new Individual, the default will be Yes, is Primary. If adding a new address to an existing Individual, the default will be Yes, is Primary.
***If updating an existing Individual, we’ll attempt to match with an existing address. We will match on Zip Code and house number (house number will be defined as the first set of characters before the first space). If the address matches, we will not update anything. If the address does not match, we will add an additional address to the Individual Record. If creating a new Individual, we will add a new address to the Individual Record.

Carrier Products

*We’ll look up the corresponding Coverage Type that you’ve mapped the given Plan Type to. If the specified Coverage Type field option has been deleted or inactivated, we will automatically create that field option and/or make it active in your AMS+ account.
**We’ll look up the field "Match SunFire Plans to Carrier Products by" from the Carrier Products section of SunFire’s integration settings. If you have selected “PlanName", then Product Name will be equal to Plan Name.

Note: Does not include attachments or files.

Policy Records

*If Carrier Name does not exist in AMS+, we’ll create a new Carrier Record where the Carrier Name = SunFire Carrier Name.
**This integration setting is optional. Depending on your settings, we’ll attempt to populate the SunFire Enrollment Confirmation Number in a Policy Custom Field and/or the Policy Number field.
***See this article for more on assigning the Servicing Agent.
****This integration setting is optional. Depending on your settings, we’ll attempt to populate the SunFire Plan ID in the specified Policy Custom Field. If no Policy Custom Field is selected, we will not populate the SunFire Plan ID.
*****This integration setting is optional. Depending on your settings, we’ll attempt to match SunFire Plans to Carrier Products in AMS+ by the “Plan Name” or “Plan Name + Plan ID”. If a match is found, we will associate the Carrier Product with the Policy. If a matching Carrier Product is not found, we can create a new Carrier Product and associate it with the Policy depending on your settings.
******This integration setting is optional. We’ll populate the Policy’s Pay Frequency with the value as specified in your settings.

Access and approval questions

How do I know if my upline has approved the integration?

Log into your SunFire account and go to your Profile page.

• If you have a CRM Connect Code, you are approved.
• If you do not have a CRM Connect Code, contact your upline.

What if I have access to more than one SunFire account through different uplines?

Each upline must provide approval. Your CRM Connect Code is unique to you and does not change.

When starting a quote and entering your CRM Connect Code, you will see a list of approved uplines and can select the appropriate one.

Can I activate the integration in my own AMS+ account?

Yes. You can activate the integration in your own AMS+ account. You do not need to be a user in your upline’s AMS+ account.

You must either:

• Own your own SunFire site, or
• Receive approval from your upline if using their site.