Overview
As a user of SunFire and AMS+, you can streamline your quoting and enrollment process with this integration. If you have access to SunFire through your upline, you will need to reach out to them for approval to use the integration. There is no additional cost to your AMS+ subscription to take advantage of this.
With this integration, users can securely transfer Individual and Sales Records from AMS+ to SunFire for quoting and enrollment. After an enrollment is completed in SunFire, the enrollment’s Individual, Carrier Product, and Policy data is sent back to AMS+.
IN THIS ARTICLE
Activating the integration
Setting up the enrollment sync
Using the integration
How to assign a Servicing Agent to Policy Records
How to start quotes in AMS+
Technical documentation
Data sent to SunFire
Data sent to AMS+
Common questions
Activating the integration
You must be the Account Owner in AMS+ to activate or deactivate this integration in AMS+.
Go to the Settings > Servicing > Integrations > SunFire page and select the “Add to AgencyBloc...” button.
Deactivating the integration
Go to the Settings > Servicing > Integrations > SunFire page and select the “Deactivate” button in the top-right corner.
Setting up the enrollment sync
You must belong to a Security Group with the 'Manage Users' Administrative permission to access and modify the SunFire integration settings.
For a smooth and optimal setup:
- You need an account with SunFire.
- Review your Carriers and Plans/Carrier Products in SunFire and AMS+. Their names need to match or the integration could create duplicate Carrier Records and Carrier Products in AMS+. We recommend changing the names in AMS+ to match SunFire.
- Some SunFire data can be stored in Policy Custom Fields. You may want to create Custom Fields for the 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.
SunFire | AMS+ |
---|---|
Beneficiary | Individual |
Plan | Policy (and optionally Carrier Product) |
When SunFire sends enrollment data to AMS+, we will take steps to put that data in the right places based on your integration settings. See below for more details.
Individual Records
By default, we will try to match SunFire beneficiaries to existing Sales Records first. If a match is found, we will convert the Sales Record into an Individual Record. If the matching Sales Record is linked to an existing Individual, we will merge it into the Individual.
If a Sales Record is not found, we will attempt to match to existing Individual Records. We’ll first try to match on a unique AMS+ identifier in the URL. If this identifier is missing, we’ll try to match on First Name/Last Name/Date of Birth. If we can't find a match, we'll create a new Individual.
Then, we can optionally update all of the Individual's fields with the new info or only the address fields depending on your integration settings.
You can choose what happens in your integration settings. 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 you choose to bring over Carrier Product data, we will try to match SunFire plans to existing Carrier Products by "Carrier Product Name".
If we can't find a match, we can create a new Carrier Product depending on your Carrier Product Sync settings. What Carrier Product fields are updated?
Policy Records
By default, we will automatically create a new Policy Record in AMS+ for every SunFire plan. What Policy fields are populated?
Also, we will try to match the carrier in a SunFire enrollment to a Carrier Record by carrier name. If we can't find a match, we will create a new Carrier Record and associate it with the new Policy Record.
The new Carrier Record's name will be the same as the SunFire Carrier name.
If we find a match, we'll associate the Carrier Record with the new Policy Record.
Using the integration
How to assign a Servicing Agent to Policy Records
If you want to assign a Servicing Agent to Policy Records created by the integration, you will need a SunFire User ID. This ID is located in your SunFire account under the User Profile > User Details section.
If you have this ID, go to My Account and link it to a Servicing Agent in your account profile.
- Go to My Account > Integrations.
- On the Integrations tab, select SunFire.
- Enter your SunFire User ID and Servicing Agent.
- The specified Servicing Agent will be assigned to all new Policies created by our SunFire integration. You must have at least one Agent Record in your AMS+ account to set the Servicing Agent.
- Save.
- If a valid ID was entered, all Policy Records created by this integration will be assigned to the specified Servicing Agent.
How to start quotes in AMS+
To run quotes with this integration, you must have a SunFire CRM Connect Code. You can find this code in SunFire. Simply log into your SunFire account, navigate to the Profile page, and copy the code shown in the CRM Connect section.
SunFire quoting is available for Sales Records and Individual Records.
Note: The quoted Sales Record or Individual Record must originate in AMS+ if you want the enrollment to return to AMS+.
Before starting a quote in SunFire, make sure you have all the necessary information to add the beneficiary’s prescriptions and providers and complete the enrollment within the same session. If you begin a quote but leave at any time before completing the enrollment, SunFire will not sync any data back to AMS+ and you will have to start all over.
To start a quote in AMS+:
- Click the “Start Quote” button on any Sales Record or Individual Record and select “SunFire” from the menu.
- Quoting menu on a Sales Record:
Quoting menu on an Individual Record: - Enter your SunFire CRM Connect Code.
- SunFire will prompt you to enter this information the first time you start a quote in AMS+. This ensures AMS+ sends data to the correct Sunfire account. Additionally, you will be prompted to enter it again if you haven't logged into SunFire within the last 24 hours.
- In the SunFire Partner ID dropdown, select the upline name you want to send the record to, then click the 'Start Quote' button. This sends the record's data to SunFire and logs you into SunFire in a new tab. See what data is sent to SunFire.
- If you only have access to Sunfire through The Brokerage Inc., for example, that's the only upline you will see. However, if you have access to other uplines, they will appear as additional options.
- In SunFire, run your quotes and add prescription and/or provider information.
- Note: If you don’t enter quote information into SunFire, it won’t be saved and you can’t revisit it in the future. Make sure to enter all quote information into SunFire.
- Complete enrollment in SunFire.
- After an enrollment is completed in SunFire, the enrollment’s Individual, Carrier Product, and Policy data is sent back to AMS+ according to the integration's sync settings.
- See enrollment sync settings
- See data sent to AMS+
Technical documentation
Data sent to SunFire
When you send a Sales Record or Individual Record to SunFire for quoting, here is the data we send over:
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 |
*If the zip code has any trailing spaces at the end and you select the “Send” button, the Individual’s profile will fail to load in SunFire. Before sending an Individual, we recommend checking to make sure its zip code doesn’t have any trailing spaces at the end and to remove them if it has any.
**The Medicare Effective Date for Part A and Part B on a Sales Record or Individual Record 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. In addition, Address Line 2 is only sent for Individual Records.
Data sent to AMS+
When SunFire syncs enrollments to AMS+, here is the data that comes over:
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 |
*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 section for more on assigning the servicing agent.
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 Sync Setup tab of the integration, if:
- You have selected "PlanName + Plan ID" then Product Name = Plan Name + Plan ID.
- You have selected “PlanName" then Product name = 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 this section 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.
Common questions
Which types of enrollments will be sent to AMS+ through the integration?
Only enrollments completed through the SunFire site will be sent to AMS+. That means quotes labeled as “MA & PDP” in SunFire.
Medicare Supplement, Hospital Indemnity, Dental, Final Expense, Life, and LTC are NOT included in the integration.
Can users map the Carrier names?
No they can’t. Whatever Carrier name is received, that is the Carrier name we will use exactly verbatim from the API.
What will happen if I already have lead profiles in AMS+ and SunFire before I activate the integration?
When you send a Sales Record or Individual Record to SunFire, the integration will scan your SunFire account for a matching record based on the following criteria: first name, last names, and DOB.
If a record exists in both systems and matches exactly on the above criteria, the integration will create a unique ID linking the two records. From then onward, changes made to the AMS+ record will be sent to its linked SunFire record.
What happens if there are multiple records with the exact same first and last names?
Search on DOB. If that doesn't work, integration will create a new Lead Profile and vice-versa. Manual work may be necessary.
Not case sensitive.