AMS Field Mapping
When you integrate your AgencyZoom account with most AMS systems- after selecting your basic settings, you’ll be prompted to go through the “Field Mapping” process.
You can always change these field mapping settings later or go through the process later- after the initial Integration Setup. However, having the proper Field Mapping in place is pivotal to leads, customers, and policies syncing between AgencyZoom and AMS systems (and vice versa), so we recommend Field Mapping as soon as possible.
What is Field Mapping?
Field mapping is the process of matching users, actions, and data types in AgencyZoom to their equivalent in the AMS system. As an example- Let’s say the user “David O’Neil sells a policy in AgencyZoom, which prompts the system to create a policy shell in AMS360. If David’s account isn’t field mapped to any account in the AMS, the system has no way of knowing who that policy shell should be assigned to when it syncs over to the AMS system. This can result in policies or customers syncing over as assigned to “unknown” or “unassigned”. Or in some cases, it can prevent them from syncing over at all.
However, if the account for David O’Neil is selected in the dropdown on the right, the system knows the account “David O’Neil” in AgencyZoom, should sync to the account “David O’Neil” in the AMS. This will assure that when the policy shell syncs to the AMS, it will sync over assigned to the correct user.
How to Field Map
Outside of the initial integration, you can access AMS Field Mapping at any time by going to MyAgency (the gear in the bottom left of AgencyZoom) > Integrations > Clicking your AMS system > Field Mapping.
From there you’ll see multiple tabs for each type of field mapping (Carriers, Sales Producers, Locations, etc), and you’ll want to make sure that each section has as many fields mapped as possible. The left side will display the data coming from the AMS, while the right side will have dropdowns where you can select the equivalent data in AgencyZoom.
The dropdown box will display as Red if there’s no equivalent in AgencyZoom selected yet. If you need to, you can leave one as un-mapped, just note that any policy using that carrier, producer, or location may not correctly sync. Once you select an option in the dropdown- it saves automatically, no need to manually click Save anywhere.
Once you’ve gone through every tab and made sure every necessary piece of data on the left is matched to an equivalent in AgencyZoom on the right, you should be all set!
Field Mapping in AMS360 FAQ
Why Do Some of my Field Mapped Sales Producers have arrows between them?
When Field Mapping Sales Producers in AMS360 integrated accounts, you may notice that some producers have arrows pointing between the accounts in AgencyZoom, and the accounts in your AMS360.
This happens when you have more than one account in AMS360 mapped to a single account in AgencyZoom. The user with the Blue Bi-Directional arrow represents the “Default” Field Mapped account, when uploading leads, customers, or policies from AgencyZoom to the AMS.
For instance, in the example above- if changes are made in AMS360 under Angela Welsh’s account, the ASDF Test account, or the AMS360 Development account, they will all sync to AgencyZoom under Bri’s account. However, if a change is made in AgencyZoom under Bri’s account, it will only sync under the account called AMS360 Development, as indicated by the Blue Bi-Directional arrow. The accounts with the grey arrows map one way, while accounts with the blue arrow will map both ways.
If an account in AgencyZoom is only mapped to one account in AMS360, the arrow will not be present. These arrows will not be present for QQCatalyst or other AMS Field Mapping, as they require that one producer in AgencyZoom only be mapped to one producer in the integrated AMS.
I added a new user to AgencyZoom, why aren’t they showing in the Producer or CSR dropdown when assigning Leads?
When AMS360 integrated Agencies add new users to AgencyZoom, they’ll often find they’re unable to assign that new Agent to Leads and Customers after adding them. This is often because they haven’t manually field mapped the new user after adding them in AgencyZoom and in AMS360.
With AMS360 integration specifically- if a user is not Field Mapped, they won’t even show as an option to assign in AgencyZoom. So whenever you add a new user in AgencyZoom and AMS360, you have to make sure to manually Field Map that new user using the steps above.
Why aren’t there any options in the Action Types dropdown?
Similar to the issue above, recently integrated AMS360 users often notice they’re unable to post notes or create tasks, because when they click the “Action Types” dropdown the box populates as empty. This is also a result of Field Mapping- specifically, no Action Types having been field mapped.
If there are no action types Field mapped in your AMS360 Integration settings, you’re unable to select an action type- and complete the note or task. You’d have to make sure to Field Map the Action Types tab using the steps above.