How It Works
When you add or change data in AMS360:
AMS360 sends Fuse a "Notification," letting Fuse know that something changed. For example, AMS360 tells Fuse, "A change was made to this customer!" or "A change was made to this policy!"
Fuse then makes a request to download that record (the changed customer or changed policy) from your AMS360 database.
This process gives you "near-real-time" integration between AMS360 and Fuse.
However, please be aware that AMS360 does not trigger a "notification" for all types of changes.
Editing most of the commonly-used "Customer" and "Policy" fields will trigger a notification, but editing certain other fields will not.
Fields That Do NOT Trigger Notifications From AMS360
These fields do not trigger a notification (an automatic re-sync), but you can force a resync of these fields by (A) editing a different field in the same record that does trigger a sync, or (B) looking up the Account in Fuse and clicking "Refresh".
This is not a comprehensive list and is only meant as a quick reference for a few commonly-used fields that will not cause an automatic sync of the record.
Profile Questions / Profile Answers
Notation / Notation ID
Contact > Sort Order
Claims-level Fields (Edits made to any field in the Claims section will not trigger a sync of the record. As a workaround to help claim data stay relevant, Fuse automatically re-syncs all claims and claim updates once per week.)
Fields That DO Trigger Notifications from AMS360
The following list, kindly provided by Vertafore, includes all fields that DO trigger a notification to Fuse:
Please note: Some of these fields are not available for use in Fuse.
This is strictly a list of fields that, if edited, will cause AMS360 to notify Fuse that the record has been edited. Fuse will then re-sync the fields we integrate from the relevant Customer or the Policy
Customer-Level Fields
Customer Number
Customer ID
First Name
Middle Name
Last Name
Firm Name (Business Name)
Address 1
Address 2
City
County
State
Zip Code
Res Phone Area Code
Res Phone
Res Extension
Business Area Code
Business Phone
Business Extension
Fax Area Code
Fax Phone
Fax Extension
Marine Area Code
Marine Phone
Marine Extension
Pager Area Code
Pager Phone
Pager Extension
E-Mail
Web Address
Formal Salutation
Informal Salutation
Date of Birth (DOB)
Occupation
Married
Business Since
Type Entity
DBA
NAICS
Federal ID Number
DUNS Number
Type Customer
Is Broker Customer
Active
Producer 1 Code
CSR Code
Broker Code
GL Division Code
GL Department Code
GL Branch Code
GL Group Code
Customer Added Date
PermAttrFlagsCust (?)
Is Health Customer
Is Life Customer
Is Financial Services Customer
Is Benefits Customer
Is Non-PC Customer
Is Personal Customer
Is Commercial Customer
Contacts Fields
Customer ID
Customer Contact ID
Contact Name
Title
Is Officer
Is Director
Address 1
Address 2
City
State
Zip
County
Res Area Code
Res Phone
Res Extension
Bus Area Code
Bus Phone
Bus Extension
Fax Area Code
Fax Phone
Fax Extension
Mobile Area Code
Mobile Phone
Mobile Extension
Pager Area Code
Pager Phone
Pager Extension
E-Mail
Formal Salutation
Informal Salutation
Policy Fields
Customer ID
Policy ID
Policy Number
Type Of Business
Policy Type
Policy Type LOB (Line of Business)
Writing Company Code
Exec Code
CSR Code
Broker Code
Policy Effective Date
Policy Expiration Date
Is Continuous
Policy Status
GL Division Code
GL Department Code
GL Branch Code
GL Group Code
Billing Method
Is New B Policy
Full Term Premium
Is Financed
Company Type
Is Multi-Entity
Policy Sub-Type
Description B Policy
Policy Transaction Premium Fields
Policy ID
Policy TP ID
Effective Date
Line Of Business
Plan Type
Writing Company Code
Premium
Billed Premium
Written Premium
Full Term Premium
How Billed
IncludePremium
IsCorrected
IsPosted
IsSuspended
Charge Code Policy TP
NonPrRecipientPolTP
NonPrinstTreatPolTP
Company Code Policy TP
Company Type Policy TP
Description Policy TP
Insert Seqential Number
Reconciled
TiComId