Levitate + Applied Epic Integration
Overview
Levitate's Applied Epic integration helps insurance agencies bring contact and policy data into Levitate for better organization, segmentation, and outreach.
- Industry: Insurance
- Integration Type: Report-based (file import)
- Sync Frequency: Daily scheduled updates
- Writeback Capabilities: Not available (read-only)
- Authentication: Individual user authentication is not required
How the Integration Works
The Applied Epic integration uses scheduled reports to keep your data up to date.
- Reports are generated in Applied Epic and sent automatically on a recurring schedule
- Levitate processes those reports and updates contact and policy data
- This allows for continuous syncing without manual uploads
Integration Settings
The Applied Epic integration includes flexible settings to control how contacts are synced and managed in Levitate.
Agency ID
Each integration is tied to a unique Applied Epic Agency ID.
Ownership Mapping
Contacts in Applied Epic are typically associated with:
- Producer
- CSR (Customer Service Representative)
You can choose one of these roles to determine ownership in Levitate.
- Ownership mapping is either Producer or CSR (not both)
- Each unique Producer or CSR can be mapped to a Levitate user
Ownership Tags
Levitate automatically applies a tag to indicate the Producer or CSR associated with each contact.
Key Facts (Date-Based Data)
- Birthday Key Fact — Pulled from contact records when available. Options include:
- All contacts
- Clients only
- Prospects only
- Renewal Key Fact — Based on policy expiration dates
Prospect Handling
Levitate identifies prospects as contacts without active policies.
You can choose to:
- Include all prospects
- Exclude all prospects
- Include prospects within a defined timeframe
Tags
Levitate can generate tags from Applied Epic data to help organize contacts.
Available tag options may include:
- Carrier
- Agency Code
- State
Primary Email Only
If a contact has multiple email addresses, you can choose to:
- Sync only the primary email (recommended)
- Sync multiple email addresses
Data Mapping
Contact Requirements
To be included in Levitate:
- Contacts must have at least a name or email address
- Contacts without sufficient data may be skipped
- Contacts with the same email address may be merged
Contact Information
| Levitate | Applied Epic |
|---|---|
| First & Last Name | First Name / Last Name |
| Company Name | Business Name |
| Primary or Secondary Email | |
| Phone Number | Phone Number |
| Address | Address fields |
Notes:
- Primary values are prioritized
- Fallback values are used if primary data is missing
Contact Handling
- For business contacts without a first name, the business name may be used
- Secondary insured contacts are not currently supported
Tags
Levitate automatically assigns tags based on Applied Epic data.
Client & Status Tags
- Client – active contact with policies
- Commercial – contact with commercial policies
- Personal – contact with personal policies
- Personal Prospect – personal contact with no active policies
- Commercial Prospect – commercial contact with no active policies
- Winback – contact with expired or canceled policies
Integration Tag
- Applied Epic – identifies contacts synced from Applied Epic
Policy & Business Tags
Depending on configuration, Levitate may also tag contacts based on:
- Line of Business
- Carrier
- Agency Code or Branch Code
Agency Code vs. Branch Code
Levitate maps both AgencyCode and BranchCode to the same field — it is one or the other, not both. Whichever value is present in the report Levitate pulls will be used for tagging. To switch between Agency Code and Branch Code, contact your Success Specialist to update the Epic report configuration.
Ownership
Contacts are assigned to Levitate users based on:
- Producer or CSR (depending on configuration)
Each Producer or CSR can be mapped to a Levitate user to ensure proper ownership.
Ownership Changes
If the ownership mapping setting is changed (e.g., from Producer to CSR):
- Contacts may need to be remapped
- Existing mappings may reset
Key Facts
Birthday
- Pulled from Applied Epic contact records
- Accuracy depends on how contact data is structured
Renewal Dates
- Based on policy expiration dates
- Helps support renewal outreach and automation
Client ID
Each contact includes a unique identifier from Applied Epic.
FAQs
Q: Does Levitate write data back to Applied Epic?
A: No. The Applied Epic integration is read-only. Levitate does not update or write data back into Applied Epic.
Q: How are inactive or prospect contacts handled?
A: Contacts without active policies may be categorized as prospects. Depending on your settings, these contacts may be included, excluded, or archived.
Q: Can I change ownership mapping later?
A: Yes, but changing ownership mapping (Producer vs. CSR) may require remapping users and can reset ownership assignments.
Final Notes
Because Applied Epic is highly customizable and report-based, your exact fields and tags may vary depending on how your reports are configured. The integration is designed to provide consistent, automated updates so your team can focus on relationship-building and communication within Levitate.