---
title: "CDK eLead Integration Details"
canonical: "https://resourcecenter.kenect.com/space/Integratio/44663163/CDK%20eLead%20Integration%20Details"
format: markdown
---
### *CDK DRIVE AND CDK eLead are different integrations

- Easily keep track of your contacts by syncing contacts from CDK eLead to Kenect
- Automate review requests based on the opportunity stage
- Automatically import all contacts from your CDK eLead account to Kenect
- Keep track of new leads that push from Kenect into CDK eLead

#### **Features**

- Contact Import – initial import happens after you connect the integration
- Contact Sync – new contacts sync every 10 minutes
- Conversation Posting – conversations will post to the contact record as long as the contact is synced within Kenect
- Lead Push – new leads that come in through the Kenect webchat widget will be pushed into CDK eLead as well as creating a new opportunity within CDK eLead
- Review Invites – trigger review invites based on Opportunity status with CDK eLead

### Contact Import and Sync

- Sync contacts from CDK elead to Kenect.  
Synchronization occurs every 10 minutes.
- A contact is synced only if it is linked to an opportunity on CDK_Lead side.

| **Client Expectation: **Activate Kenect app within Fortellis, Grab CMF number within CDK eLead , Verify they have user permissions to authorize app |
| --- |
| **Kenect Expectation:** Generate subscription ID within Fortellis, authorize the request, paste sub ID within Kenect setup, Verify feature flags are enabled within Kenect |
| **Connection Type:** API |
| **Run Time: **Contacts – 10 minutes, events – 10am, 1pm, 4pm MST (daily) |
| **Setup Time:** 5-10 minutes |
| **Review Invites:** Yes |
| **Native Texting: **N/A |
| **Lead Push: **Yes |
| **Conversation Posting: **Yes |

### Lead Push from Kenect into CDK elead

​Contact is pushed from the Kenect Text Widget to CDK elead​

Name, Mobile Number, and Message​

A new Opportunity is created in CDK elead

### Post Conversation Histories into CDK elead

Text messages sent from Kenect will post into the CDK elead customer record in near real time. ​(*Messages will show as ‘Comments’)*

See conversation histories inside CDK elead

![image-20240508-160104.png](media://6a9bc4e2-6021-4feb-94f3-4ea91eeec7fd)

### **Text Automation**

**Opportunity {status}**

Automatically send texts to customers based on the following configured opportunity stages: 

- New
- Custom Status

> ℹ️ **Some dealers may add 'Custom' configured opportunities that are in addition to the above stage.**

- For `CUSTOM_STATUS` events we will now be pulling data for the past 5 days. We specifically compare the 'dateIn' value to the current date. The 'dateIn' value is the day the opportunity was created within eLead. So, if an opportunity was created OVER 5 days ago, we will not retrieve that information.
- For the other events, mainly `'Opportunity - New'`, we are going to pull events from 3 hours prior according to the new cron schedule we have implemented

# **FAQs (Frequently Asked Questions)**

- **When is a contact created in CDK? **
  - Whenever a lead arrives in Kenect, Kenect searches and, if it does not find an opportunity in CDK for that phone number; then a contact will be created in Kenect, and then an associated opportunity will be created for it.
- **Why is there a contact in CDK_Lead but it is not synced to Kenect?**
  - The user needs to verify the contact is linked to an oportunity. Only contacts linked to an opportunity on the CDK_Lead side will be synced.
- **What happen if the "Allow new opportunity creation for message sync" check box is unchecked**
  - This checkbox is related to message synchronization and opportunity creation in CDK; not to the leads' workflow.Messages are posted on opportunities. To synchronize a message, an opportunity must exist.That said, when a message needs to be synchronized, Kenect will look for an opportunity in CDK for the phone number:- If it exists, it will simply put the message in the notes of the opportunity- If it does not exist, it will discard the message. Nothing is going to happen, no contact or opportunity is going to be created.

![image-20240508-162140.png](media://61cc0c58-0363-4144-9fde-1db327129a44)

- **What happen if the "Allow new opportunity creation for message sync" check box is checked?**
  - This checkbox is related to message synchronization and opportunity creation in CDK; not to the leads' flow.That said, when a message needs to be synced, Kenect will look for an opportunity in CDK for this phone number:1- If it exists, it will simply put the message in the notes of the opportunity,2- If it does not exist, it will create a contact and then an opportunity for this contact; or if the contact exists but has not had any opportunity in the last 60 days, a new one will be created.
- **What is the time frame that Kenect takes into account to create a new opportunity for a contact?**
  - Kenect searches up to a maximum of 60 days. If no opportunity exists for the contact in this time frame, create one. If it does exist, simply add the messages to the notes of the existing opportunity
- **If a sale is made in CDK elead, is an automatic message generated in Kenect?**
  - No, its not. Sales must to have opportunities associated with them. Just making a sale on CDK_elead does not generate automatic messages.  
The communication between Kenect and CDK is through opportunities. This means that only events that have opportunities associated with them will be synchronized. The same applies to contacts. Besides that, the message will be generated only if the opportunity status has an automatic message configured on the integration page.
- **Does a contact have to be in an 'active' opportunity status to sync?**
  - Yes, only Active opportunites are available for the CRM Sales APIs
- **Why aren’t my contacts syncing?**
  - We will only sync newly created contacts linked to opportunities within CDK eLead.
- **Where will the conversation history post within CDK eLead?**
  - Text messages sent from Kenect will post into the CDK elead customer record in the ‘Contacts’ tab.