Levitate + AMS 360 Integration
Overview
Levitate's AMS360 integration helps insurance agencies sync client and policy data into Levitate while keeping key engagement activity reflected back in AMS360.
- Industry: Insurance
- Integration Type: API-based
- Sync Frequency: Near real-time updates, plus a weekly full sync
- Authentication: Individual user authentication is not required
Activity Writeback
Levitate can write activity back to AMS360, including:
- Notes
- Emails
- Phone call logs
- Inbound and outbound text messages
- Handwritten cards
Where activities appear in AMS360:
- Notes created in Levitate are written back as Notes
- Emails, text messages, phone calls, and handwritten cards are written back as Activities
Levitate also includes the name of the Levitate user who performed the action in the activity details for clearer attribution.
Integration Settings
The AMS360 integration includes flexible settings to control contact syncing, ownership, tagging, and writebacks.
Agency ID
Each integration is connected to one AMS360 agency account.
Ownership Mapping
Contacts can be assigned to Levitate users based on AMS360 roles:
- Executive / Producer
- Representative / CSR
Ownership is determined by the selected mapping method and user mapping configuration.
Ownership Tags
Levitate can add tags based on the AMS360 Executive or Representative associated with each contact.
Options may include:
- Executive
- Representative
Birthday Key Facts
When Levitate can identify a contact's birthday from AMS360, it can be added to the contact profile as a Key Fact.
Prospect Handling
Levitate can identify prospects as contacts without active policies.
You can choose whether to sync:
- All prospects
- No prospects
- Prospects within a defined timeframe
Commercial Profile Handling
For commercial accounts with multiple associated contacts, you can choose whether to sync:
- All contacts
- Primary and secondary contacts only
Primary Email Only
If a contact has multiple email addresses, this setting controls whether Levitate syncs only the primary email address.
Import Inactive Contacts
You can choose whether inactive AMS360 contacts should sync into Levitate.
Segment by Tags
Contacts can be included or excluded from syncing based on selected tags for more granular control.
Data Mapping
Contact Requirements
To sync into Levitate, a contact must have enough identifying information.
- Contacts without a name or email address may be skipped
- If a contact has an email address but no name, the email may be used as the first name
- Contacts sharing the same email address may be merged
Contact Information
| Levitate | AMS360 |
|---|---|
| First & Last Name | Primary Contact / Customer Contact |
| Company Name | Firm Name |
| Email Address | Customer or Contact Email |
| Phone Number | Customer or Contact Phone |
| Address | Customer or Contact Address |
AMS360 can store information both at the customer level and within nested contact profiles. Levitate uses the best available contact information from these records to create a complete contact profile.
Levitate can also pull in a second insured from AMS360.
Key Facts
Birthday
Birthdays may be pulled from the AMS360 customer record when available.
Renewal Date
Policy expiration dates can be added as Renewal Key Facts in Levitate.
If a policy is marked as continuous, that status may be reflected in the Key Fact.
Tags
Levitate can create tags from AMS360 customer and policy data.
Default Tags
- AMS360 – identifies contacts synced from AMS360
- Client – active client with policies
- Inactive – inactive client with policies, if inactive contacts are enabled
- Commercial – commercial customer
- Personal – personal customer
- Personal Prospect – personal customer with no active policies
- Commercial Prospect – commercial customer with no active policies
- Winback – prospect with expired or canceled policies
Policy & Business Tags
Depending on configuration, Levitate can also tag contacts based on:
- Line of Business
- Carrier
- Branch
- Department
- Division
- Group
- Notation
- City
- State
- Postal Code
- Health Flag
Ownership Tags
Levitate can tag contacts with AMS360 Executive or Representative initials to reflect the ownership data synced from AMS360.
Ownership Behavior
Ownership can be configured based on AMS360 Executive and Representative roles.
Common mapping options include:
- Commercial contacts assigned to Executive; personal contacts assigned to Representative
- Commercial contacts assigned to Representative; personal contacts assigned to Executive
If a merged contact includes both commercial and personal records, the selected configuration determines which record type takes priority for ownership.
Writeback Details
Levitate writes back activity to AMS360 so teams can maintain a record of engagement.
- Notes are written back as AMS360 Notes
- Emails, text messages, phone calls, and handwritten cards are written back as AMS360 Activities
AMS360 activity attribution is determined using the available user mapping information. Levitate also includes the acting Levitate user's name in the activity description for clarity.
Name Derivation Logic
The following rules describe how Levitate derives contact names from AMS360 data.
Nicknames
In AMS360, nicknames are specified with parentheses () in the First Name field. Anything between the parentheses is treated as the nickname and becomes the first name in Levitate.
Important: Do not add text like "(Deceased)" to a contact's name — Levitate would greet them as "Hi Deceased".
Example — AMS360 entry Jonathan (Jon) Doe becomes First Name: Jon, Last Name: Doe in Levitate.
Levitate looks for a nickname in this order:
- First Name field
- Informal Salutation
- Formal Salutation
If a nickname is found in any of these fields, it is set as the first name in Levitate.
First Names
First names are derived in this order:
- Nickname extracted from the First Name field (if present)
- First Name field
- Informal Salutation
- Formal Salutation
- If none of the above yield a value, no first name is set
Last Names
Last names are derived in this order:
- Last Name field
- Formal Salutation
- Informal Salutation
Multiple Names
Levitate recognizes multiple names in a single field when separated by: &, and, +, or &/or. The following fields are checked: First Name, Firm Name (if Personal), Informal Salutation, Formal Salutation.
Example: Contact Name Jonathan & Johanna Doe with Informal Salutation Jon and Jane Doe → First Name: Jonathan & Johanna, Last Name: Doe, Nickname: Jon and Jane.
Levitate also preserves initials and suffixes (e.g., "Billy B. Bradley Jr.").
Commercial Contacts
If a commercial customer record has only a firm name (no first/last name), Levitate takes the first Customer Contact record with a name and merges it into the record. The firm name is set as the Company name. If no Customer Contacts are found, the firm name is used as the First Name.
If no email address is found on the primary record, Levitate searches the list of Customer Contacts for any available email address.
Personal Contacts
If a personal customer record has no first name, Levitate first attempts to derive it from the Firm Name, then falls back to the common field order described above. Name changes made in Levitate are not overridden by AMS360 data on subsequent syncs.
FAQs
Q: Does the AMS360 "Do Not Market" field sync as an unsubscribe status in Levitate?
A: No. The AMS360 "Do Not Market" field does not currently sync into Levitate as an unsubscribe status.
Q: How quickly does data sync?
A: AMS360 changes are typically reflected near real time when notifications are enabled. Levitate also performs a weekly sync to help keep data up to date.
Q: Where do writebacks appear in AMS360?
A: Notes appear as Notes. Emails, text messages, phone calls, and handwritten cards appear as Activities.
Final Notes
AMS360 data structures can vary by agency, especially around contact records, customer profiles, and policy data. Levitate is designed to use the best available information from AMS360 to create accurate contact profiles, tags, ownership, and Key Facts in Levitate.