Note for accounts using Sales Records: This article includes a Legacy components section with additional information that applies to your account.
SunFire is a Medicare quoting and enrollment platform agents use to quote and enroll beneficiaries in Medicare plans.
With this integration, users can securely transfer Individual Records from AMS+ to SunFire for quoting and enrollment. Individual Records must originate in AMS+; you can't start a profile in SunFire and send it to AMS+. After an enrollment is completed in SunFire, the enrollment's Individual, Carrier Product, and Policy data is sent back to AMS+.
Note: Rx Collect prescription and provider data is included in the integration only for AMS+ accounts on the Accelerate or Elevate package. Quoting and enrollment sync are available on all AMS+ packages.
Requirements
For AMS+
Activating the integration
- You must be the Account Owner of your agency's AMS+ account to activate the integration.
- To modify integration settings or deactivate the integration after it has been activated, you must be an Administrator:
- You must be logged into AMS+ as an Agency User.
- You must be assigned to a Security Group with the Manage Users permission.
Starting quotes
- You must be logged into AMS+ as an Agency User or Agent CRM User.
- To start quotes for Individual Records, you must be assigned to a Security Group with the Individual Visible and Edit permissions.
- If you're an Agent CRM User, you need access to Individual Records assigned to your Accessible Agent, and optionally unassigned records.
For SunFire
Credentials
- You must have an active SunFire account.
- If you access SunFire through an upline, you must receive their approval before using the integration. Each upline must provide separate approval if you have access to more than one.
- A valid SunFire CRM Connect Code, obtained from your SunFire account. See Get your SunFire CRM Connect Code.
In this article
- Data flow
- Limitations
- Activating the integration (Account Owner)
- Setting up the integration (Account Owner or Administrator)
- Assigning a Servicing Agent to Policy Records (Agency User or Agent CRM User)
- Starting quotes in AMS+ (Agency User or Agent CRM User)
- Technical documentation
- Troubleshooting
- Legacy components
Data flow
Data moves between AMS+ and SunFire in two directions, each triggered independently and on demand rather than continuously or on a set schedule.
- AMS+ to SunFire: When you select the Start Quote button on an Individual Record, the record's data is sent to SunFire. See what data is sent to SunFire.
- SunFire to AMS+: After an enrollment is completed in SunFire, the enrollment's data is sent back to AMS+ according to the integration's sync settings. See what data is sent to AMS+.
See Starting quotes in AMS+ for the full workflow, and Technical documentation for field-level mapping in both directions.
Limitations
- Individual Records must originate in AMS+. You can't start a profile in SunFire and send it to AMS+.
- Attachments and files aren't included in the sync, in either direction.
- Prescription and provider data moves one-way, from AMS+ to SunFire only, and is available only on the Accelerate and Elevate subscription packages.
- SunFire doesn't scan for or merge existing lead profiles.
- Quote information that isn't entered into SunFire isn't saved and can't be revisited later.
- Medicare Part A and Part B effective dates must fall on the 1st of the month. SunFire automatically adjusts dates that don't.
Activating the integration (Account Owner)
- Go to My Agency Settings > Third Party Integrations > SunFire.
- Select Add to AgencyBloc…
- Fill out the required fields and select Save to complete activation.
Note: Once activated, review your enrollment sync settings and complete setup. This can be done by the Account Owner or an Administrator. See Setting up the integration.
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. If you have access to more than one SunFire account through different uplines, each upline must provide approval separately.
Deactivating the integration (Administrator)
- 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.
Hiding the integration (Account Owner)
If your agency doesn't currently use SunFire, the Account Owner can hide it from the Start Quote menu on SunFire's landing page before activating, so users don't see it listed as an option. This only applies while the integration is inactive. Once SunFire is activated, it's always shown in the Start Quote menu.
Setting up the integration (Administrator)
Before completing setup, keep the following in mind:
- 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, or duplicate Carrier Records or Carrier Products may be created. It's 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 and Plan ID.
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.
| SunFire | AMS+ |
|---|---|
| Beneficiary | Individual |
| Plan | Policy (and optionally Carrier Product) |
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 Individual Records. First by a 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 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.
Assigning a Servicing Agent to Policy Records (Agency User or Agent CRM User)
If you want Policy Records created by the SunFire integration to automatically assign a Servicing Agent, you must link your SunFire User ID to an Agent Record.
You can find your SunFire User ID in SunFire under the Account information section.
If you have this ID, follow these steps:
- Go to My Account > Integrations.
- On the Integrations tab, select SunFire.
- Enter your SunFire User ID and Servicing Agent (name of your Agent Record).
- The selected Servicing Agent will be assigned to all new Policy Records created by the SunFire integration.
- You must have at least one Agent Record in your AMS+ account to set the Servicing Agent.
- Select the Save button.
If a valid SunFire User ID is entered, all Policy Records created by the integration will be assigned to the specified Servicing Agent.
Starting quotes in AMS+ (Agency User or Agent CRM User)
Get your SunFire CRM Connect Code
To run quotes using this integration, you must obtain your SunFire CRM Connect Code from within SunFire.
- Log into your SunFire account.
- Navigate to your Profile page.
- Copy the CRM Connect Code shown in the CRM Connect section.
If you do not see a CRM Connect Code, contact your upline for approval. Each upline must provide separate approval if you have access to multiple uplines.
If you use your own SunFire site, you can use the integration in your own AMS+ account. You do not need to be a user in your upline's AMS+ account.
Your CRM Connect Code is unique to you and does not change.
You only need to enter your SunFire CRM Connect Code the first time you start a quote in AMS+. However, you may be prompted to enter it again if you have not logged into SunFire within the last 24 hours. This occurs when your SunFire session has expired and requires re-authentication.
Start a quote in AMS+
Note: If you want enrollment data to sync back to AMS+, you must start the quote from an Individual Record in AMS+.
- Open an Individual Record.
- Select the Start Quote button and choose Send to SunFire.
- Enter your SunFire CRM Connect Code if prompted.
- In the SunFire Partner ID dropdown, select the upline you want to send the record to. See what data is sent to SunFire.
-
Depending on your version of SunFire, you may see either "SunFire Blaze" or "SunFire Blaze Connect" with your upline name options. SunFire Blaze is used for call centers, while SunFire Blaze Connect is used by agents and downlines through an upline, with similar quoting and enrollment features. If you have questions about your platform or access, contact your SunFire representative.
Note: If AMS+ is unable to match a provider from Rx Collect to SunFire's provider database, a warning will appear when you start the quote. These providers will not carry over automatically and may need to be looked up manually in SunFire.
- Select the Start Quote button.
This sends the record's data to SunFire and logs you into SunFire in a new tab.
If you only have access to one upline account, that is the only option shown. If you have access to multiple uplines, each approved upline will appear as an option.
Complete the quote and enrollment in SunFire
In SunFire:
- Run your quotes.
- Add prescription and provider information as needed.
- Complete the enrollment.
If you do not enter quote information into SunFire, it will not be saved and can't be revisited later.
After an enrollment is completed in SunFire, the enrollment's Individual, Carrier Product, and Policy data is sent back to AMS+ according to your enrollment sync settings.
Note: Data doesn't sync automatically in either direction. To push updated Individual data from AMS+ to SunFire, start a quote again using the Start Quote button. The first time you send an Individual Record, SunFire creates a lead profile and links it to that AMS+ record, so later sends update the same SunFire profile rather than creating a new one. Data is only pushed from SunFire to AMS+ when an enrollment is completed in SunFire.
Technical documentation
Note: Rx Collect prescription and provider data moves one-way, from AMS+ to SunFire only, and is included only for AMS+ accounts on the Accelerate or Elevate subscription packages. Update prescriptions and providers in AMS+ before completing enrollment in SunFire. SunFire doesn't send prescription or provider changes back to AMS+.
Data sent to SunFire
When an Individual Record is sent to SunFire for quoting, the following data is included.
| AMS+ Field | SunFire Field |
|---|---|
| Zip Code* | Zip Code |
| First Name | First Name |
| Last Name | Last Name |
| DOB | Date of Birth |
| Medicare Beneficiary ID (MBI) | MBI |
| Medicare Effective Date (Part A)** | Hospital (Part A) effective date |
| Medicare Effective Date (Part B)** | Hospital (Part B) effective date |
| Email Address | |
| Home Phone*** | Phone number |
| Address Line 1**** | Address 1 |
| Address Line 2**** | Address 2 |
| City**** | City |
| State**** | State |
| Prescriptions: Pharmacy Name | Pharmacy Name |
| Prescriptions: Pharmacy Address***** | Pharmacy Address |
| Prescriptions: Medication Name | Medication Name |
| Prescriptions: Quantity | Quantity Per Refill |
| Prescriptions: Dosage Name | Dosage Name |
| Prescriptions: Refill Frequency | Drug Frequency |
| Providers: Doctor Name****** | Primary Doctor |
*If the zip code has any trailing spaces and you select the Start Quote button, the Individual's profile will fail to load in SunFire. Before sending an Individual, check that the zip code doesn't have trailing spaces and remove them if needed.
**The Medicare Effective Date for Part A and Part B must always be the 1st of the month. If it isn't, the integration will automatically adjust it to the 1st when it arrives in SunFire. For example, if the date is June 5th, it will be changed to June 1st.
***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.
****If more than one address is found, we'll use the primary address. Address Line 2 is only sent for Individual Records.
*****In AMS+, each pharmacy listed on the Prescriptions tab of an Individual Record has an NPI (National Provider Identifier). SunFire uses this NPI to look up the pharmacy's address in its system.
******We send over the doctor's name. SunFire doesn't store provider addresses from AMS+.
Data sent to AMS+
Data syncs after an enrollment is completed in SunFire.
Individual Records
| SunFire Field | AMS+ Field |
|---|---|
| Zip Code | Zip Code |
| First Name | First Name |
| Last Name | Last Name |
| Date of Birth | Date of Birth |
| Email Address | Email Address |
| Phone Number | Home Phone* |
| Address Type** | |
| Primary*** | |
| Address 1 | Address Line 1**** |
| Address 2 | Address Line 2 |
| City | City |
| State | State |
| Username | Servicing Agent***** |
| Part A Effective Date | Medicare Effective Date (Part A) |
| Part B Effective Date | Medicare Effective Date (Part B) |
| Medicare Number or Medicare Claim Number | MBI (Medicare Beneficiary ID) |
| Type | |
| Status | |
| Prescription Information | None****** |
| Provider Information | None****** |
*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 Assigning a Servicing Agent to Policy Records 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:
| SunFire Field | AMS+ Field |
|---|---|
| Address Type* | |
| Primary** | |
| Address 1 | Address Line 1*** |
| Address 2 | Address Line 2 |
| City | City |
| State | State |
| Type | |
| Status |
*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
| SunFire Field | AMS+ Field |
|---|---|
| Plan Type | Coverage Type* |
| Product Name** |
*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
| SunFire Field | AMS+ Field |
|---|---|
| Carrier Name | Carrier Name* |
| Enrollment Confirmation Number Note: SunFire's Enrollment Confirmation Number is only for the purposes of finding the app within SunFire. |
Policy Custom Field and/or Policy Number** |
| Premium Per Month | Premium |
| Submission Date | App Submit Date |
| Application Effective Date | Effective Date |
| Username | Servicing Agent*** |
| Status | |
| Plan Type | Coverage Type |
| Plan ID | Policy Custom Field**** |
| Carrier Product***** | |
| Pay Frequency****** |
*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 Assigning a Servicing Agent to Policy Records 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 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.
Troubleshooting
An Individual's profile fails to load in SunFire.
The Individual Record's Zip Code has trailing spaces.
Remove any trailing spaces from the Zip Code field on the Individual Record, then select Start Quote again.
AMS+ can't match a provider from Rx Collect to SunFire's provider database.
A warning appears when you start the quote if AMS+ is unable to match a provider from Rx Collect to SunFire's provider database.
The provider won't carry over automatically. Look it up manually in SunFire after the quote starts.
A duplicate lead profile is created in SunFire.
SunFire doesn't scan for or merge existing lead profiles. If a matching lead profile already exists in SunFire before an Individual Record is sent from AMS+ for the first time, sending it creates a duplicate instead of linking to the existing profile.
Always send the Individual Record from AMS+ first, before creating anything directly in SunFire, so the link between the two systems is established correctly.
Legacy components
The following content applies only to accounts still using Sales Records. If you're unsure whether this applies to you, check your subscription package on the Subscription page. Accounts on Enhanced Records will show a package type that includes "+ Enhanced Records" (e.g., Accelerate + Enhanced Records). If your package does not include "+ Enhanced Records," this section applies to you.
Legacy components in this section:
- Matching criteria for syncing enrollments to Individuals — accounts using Sales Records
- Start a quote from a Sales Record — accounts using Sales Records
- Sales Record permissions — accounts using Sales Records
Matching criteria for syncing enrollments to Individuals
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 matching Sales Record is linked to an existing Individual, it is merged into that Individual.
If no Sales Record is found, AMS+ attempts to match an existing Individual Record by unique AMS+ identifier in the URL. If this identifier is missing, it will try to match on First Name, Last Name, and Date of Birth. If no match is found, a new Individual is created.
Start a quote from a Sales Record
The steps for starting a quote from a Sales Record are the same as for an Individual Record. See Start a quote in AMS+ above. The data sent to SunFire is also the same — see Data sent to SunFire.
- Open a Sales Record.
- Select the Start Quote button and choose Send to SunFire.
Users can also start quotes for Sales Records in AMS+ using the same SunFire CRM Connect Code used for Individual Records.
Sales Record permissions
To start quotes for Sales Records, your assigned Security Group must also have the Sales Enablement Visible permission. You must also have user account Sales permissions to View and Edit Sales Records. Learn more.