Levitate + QQCatalyst
Why did we build this?
Before the integration, we’d rely on exports of customer data to be imported into Levitate to build our lists of contacts to keep in touch with. By building an integration directly with QQCatalyst, we’ll simplify the process for our mutual customers, allowing them to pull their data in themselves and never have to worry about updating their lists.
With this integration, customers are also able to trigger new client automations and see up to date policy tags at a glance
Who is this available to?
The QQCatalyst integration is available to any Insurance customer with a paid Business or Business Plus, Silver or Gold account.
What does it do?
Levitate will automatically pull contacts, key facts, and tags from QQCatalyst for each connected user. Data syncs daily, keeping the data evergreen. Contact information includes first and last name, phone number, email address, preferred physical address, company name and title, etc. We also do quite a bit of filtering and enhancement to help keep emails authentic (Nicknames replace first names, deceased clients are automatically removed, etc).
We also push activities from Levitate (notes, emails, texts) into QQCatalyst so you have seamless recordkeeping between the two systems!
What do we pull in?
- Contacts
- Name (Nicknames replace First Name when a Nickname exists)
- Address
- Phone
- Company Name
- Birthdays (key fact)
- All active policies
- Expiration date (key fact)
- Lines of business (tag)
- Writing carrier (tag, based on optional setting)
- Agent / CSR (tags -- one or both, depending on optional setting and ownership role)
- Customer ID # (key fact)
*Contacts sync daily!*
What do we push to QQCatalyst?
Emails sent through Levitate (via the Web UI or email plugins), notes, and text messages will automatically push back to QQCatalyst. These will be found in the Contacts section in QQCatalyst.
This feature needs to be enabled by your Success Rep, so if you don’t see your Levitate activities pushing to your Contacts in QQCatalyst, just let them know and they can turn on this setting for you!
Personal and Commercial Nested Contacts
For Personal lines contacts, Levitate does not pull in Additional Contacts (nested / relationship contacts) from QQCatalyst.
Commercial lines contacts in QQCatalyst tend to represent companies and they have nested “Business Contacts” that represent individual people. Levitate pulls in each nested business contact separately and combines their personal details with the company details of the parent commercial contact.
By default we load only the business contact marked primary. All business contacts may be loaded by request to your Success Specialist
Enabling the Integration
Once enabled for your account by your Success Specialist, the new integration card will appear on your dashboard.
From there, you will be prompted to connect to QQCatalyst.
You will be taken to QQCatalyst’s login page. Enter your username and password to access QQCatalyst.
(Levitate does not ever see your credentials -- we use the industry-standard OAuth login flow to provide us with a token to access contacts on your behalf)
You may be prompted to expressly authorize Levitate’s access. Choose Yes.
If successful, you will be taken back to Levitate and your contacts will start syncing!
FAQ
Q: Does Levitate write anything back to QQCatalyst?
A: Everything is written to the "Notes" section of a Contact in QQCatalyst. The ability to ‘Write Back’ to Levitate needs to be turned on by your Success Rep, so if you’re not seeing this happen, please reach out to them and they’ll get you squared away.
Q: Why does it take so long to sync contacts?
A: We’re throttled by their API, we can’t make it go any faster unfortunately! Sometimes it’s quite speedy, but it’s unpredictable.
Q: Can we get all QQCatalyst contacts by having just a single Levitate user connect?
A: It depends. If that one user can see everything in QQCatalyst, then no other user needs to connect from Lev. If the customer has special permissions for each user in QQCatalyst, however (e.g., some users can only see contacts belonging to certain locations), then we need multiple users to connect in order to find every contact.
Data Mapping
The following table shows how each piece of data in QQCatalyst maps to corresponding contact details in Levitate.
QQCatalyst | Levitate |
Contact type | Contact type tag - Personal, Commercial, Personal Prospect, Commercial Prospect |
Contact status | Client tag (if active with policies) Inactive Client tag (if inactive with policies) |
Personal:Customer Info > Personal Information > First Name, Nickname, Last Name Commercial: Customer Info > Business Contacts > First Name, Nickname, Last Name |
First Name, Last Name |
Personal:Customer Info > Basic Contact Info > Email Addresses Commercial: Customer Info > Business Contacts > Email AddressesIf primary business contact lacks email addresses, we fall back to the parent commercial contact’s Basic Contact Info |
Email (primary only by default) Unsubscribe tag (if marked Opt-Out in QQCatalyst) |
Personal:Customer Info > Basic Contact Info > Phone Numbers Commercial: Customer Info > Business Contacts > Phone Numbers If primary business contact lacks phone numbers, we fall back to the parent commercial contact’s Basic Contact Info |
Phone numbers, labeled by type (e.g., Home, Business Cell, etc.) |
Personal:Customer Info > Personal Info > Date of Birth Commercial: Customer Info > Business Contacts > Date of Birth |
Birthday key fact |
Personal:Customer Info > Addresses > Street, Apt/Suite/Other, City, State/Province, Zip, Country Commercial: Customer Info > Business Contacts > Street, Apt/Suite/Other, City, State/Province, Zip, Country |
Address, City, State/Province, Zip/Postal Code, Country |
Customer Info > Account Information > Agent, CSR | Determines contact owner, depending on ownership role setting and user mapping Producer / CSR tag |
Policies > Expiration Date | Renewal key fact (per policy) WinBack tag, if policy is expired and contact is a prospect |
Policies > Line of business | Renewal key fact (per policy) Line of business tags (per policy) |
Policies > Carrier | Carrier tag (optional setting, enabled by default) |