Skip to main content

BirdEye Native Integration - CCC One

Updated in the last hour

*This integration is supported for both SMB & Enterprise businesses.

Integrating BirdEye with CCC One
User Manual

Table of Contents

Introduction

Details required from the client

  • Triggers Supported

Details required from the BirdEye dashboard

  • Enterprise ID for multi-location account and Business ID for all locations

  • Business ID in case of an SMB Business

Details required from the CCC SECURE SHARE dashboard

  • Facility ID

NOTE: BirdEye support will reach out to the client and ask to connect the ‘BirdEye’ app through the Marketplace by selecting the CCC Secure Share configuration option within their CCC ONE application.

Once the client connects to the ‘BirdEye’ app, a notification will be sent to cccone@birdeye.com email. The BirdEye support will search for the Facility ID from CCC SECURE SHARE dashboard.

Integration Process

Business Integration Group

  • Create Integration Group (Curl Command)

  • Fetch information for all the triggers (Curl Command)

  • Find business integration group details (Curl Command)

  • Update Trigger Information (Curl Command)

Integration Mapping

  • Integration Mapping (Curl Command)

Important Instructions


Introduction

CCC One is a leading provider of innovative cloud, mobile, telematics, hyperscale technologies and apps for the automotive, insurance, and collision repair industries. It is a total repair platform that brings the functions of business together in one application to help manage shop performance, business, and costs. CCC One is used by both small and medium-sized repair shops.

Integrating BirdEye with CCC One will automate the process of review request solicitation for BirdEye clients using CCC One. Once the setup is complete, BirdEye starts receiving notifications from Client CCC One CRM for any new customer who has recently been serviced by the client repair-shop. BirdEye will start sending out review requests immediately as per the configuration setup within the dashboard. BirdEye collects the first name, last name, email address and phone number of your clients and automatically sends them review requests based on the preferences set within the BirdEye dashboard.


Integration Requirements:

Triggers supported

BirdEye allows you to fetch data from your CRM using some predefined triggers. As part of the integration process, you will need to ask the business for its preference. After integration is complete, requests will be sent out based on the configured trigger. Here is the supported trigger for CCC One:

Trigger Name

Trigger Description

CCC One Repaired Vehicle Pickup Trigger

This trigger is used to fetch customer data based on the actual pickup date of the repaired vehicle

Information required from CCC SECURE SHARE dashboard

As part of the integration, you will require the businesses’ Facility ID.

NOTE: Please ask your customer to connect to the BirdEye app through the Marketplace by selecting the CCC Secure Share configuration option within their CCC ONE application.

Visit cccone.com/settings and log in to your account. Click on the ‘Secure Share’ button

Activate BirdEye account. (It takes 3-4 steps to finalize)

Once the client connects to the BirdEye app, a notification will be sent to cccone@birdeye.com email. After that you will search for the Facility ID from the CCC SECURE SHARE dashboard.

Steps to find Facility ID

Go to: https://www.cccsecureshare.com/dashboard/application/242/customers
And, click on the ‘Sign in with Google’ button, and use the following credentials:

Username: ccconeint@birdeye.com
Password: BirdEye@123

After login, you will land on the Customers page.
On the search bar, enter the business name for which you need the Facility ID.

Information required from the BirdEye Dashboard

  1. For single location SMB account - Business ID

  2. For multi-location account - Enterprise ID and Business IDs of all locations
    Enterprise ID

Business IDs of all locations


Integration process

Before you can integrate CCC One with BirdEye, you will need to set up the following configurations:


1. Business Integration Group:

A business integration group is a configuration that supports the business hierarchy of individual businesses on the BirdEye platform. The properties that are common for all business integrations are entered at the group level. Setting up a business integration group allows you to associate multiple business locations with the Enterprise account. Below is the list of curl commands that you will need to run to set this up.

a) Create Integration Group (Curl Command)

Copy this Curl Command

curl -X PUT https://common-services.birdeye.com/integration/add/businessintegrationgroup -H 'Cache-Control: no-cache' -H 'Content-Type: application/json' -d '{"parentBusinessNumber":152820762348934,"integrationSourceId":25,"integrationGroupTriggers":[{"triggerId":30,"triggerTypeId":2}],"integrationGroupProperties":[{"triggerId":30,"propertyKey" : "delay.sending.rr","propertyValue": "0"},{"propertyKey" : "valid.vehicle.pickup.days","propertyValue": "1"}]}'
  • 152820762348934 - Business ID - This is Enterprise ID for multi-location account and Business ID for a single location SMB account

  • 30 - Integration Trigger ID - Can be one or more triggers. Ask client what trigger they would like to integrate with then run the curl command to fetch all possible triggers for CCC One. Identify the trigger ID(s) and insert (use commas) in case of multiple trigger IDs.

  • 30 - Integration Trigger ID - Trigger ID for which delay need to be added

  • 0 - in.sending.rr - No of days to send review request after the vehicle pickup. If need to send RR instantly then value will be 0

  • 1 - vehicle.pickup.days - Review Request will be sent to the customers who have Actual pick date within current date and (current date - value of valid.vehicle.pickup.days property). Default value is 7 days

NOTE: We will get the group ID once we run the first curl (Integration Group) and make a note of group ID as that will required while we will be doing the integration mapping.

b) Fetch information for all the triggers available for CCC One (Curl Command)

Copy this Curl Command

curl -X GET https://common-services.birdeye.com/integration/trigger/integrationtriggers/sourceid/25 -H 'cache-control: no-cache' -H 'content-type: application/json'

Sample response: A sample response like this would appear after you run the curl command. The response will have the trigger name, description and the ID. This trigger ID will be utilized while creating the integration group. An integration can have one or more triggers. To use more than one trigger, enter comma-separated values while creating the integration group

[
{
"id": 30,
"integrationSourceId": 25,
"triggerService": "ccconeRepairedVehiclePickupTrigger",
"displayName": "CCCOne Repaired Vehicle Pickup Trigger",
"description": "This trigger is used to fetch customer data based on actual pickup date of repaired vehicle",
"active": true,
"integrationSourceName": "CCCOne",
"integrationTriggerType":[{"id":2,"name":"WEBHOOK"}]
}
]
  • 30 - Trigger ID

c) Find business integration group details (Curl Command)

Copy this Curl Command

curl -X GET https://common-services.birdeye.com/integration/businessintegrationgroup/152820762348934 -H 'Cache-Control: no-cache'
  • 152820762348934 - Business ID: Enter the Business ID here to get the integration group details for a business.

Sample Response:

[
{
"groupId": 264,
"integrationSourceType": {
"id": 25,
"integrationSource": "CCCONE",
"sourceCategory": "Automotive",
"oauthEnabled": false
},
"integrationGroupTriggers": [
{
"triggerId": 30,
"triggerTypeId": 2
}
]
}
]
  • 264 - Group ID: A group ID will be returned in the sample response with the details of the existing triggers for a business.

d) Update Triggers Information (use only if business wants to change) (Curl Command)

Copy this Curl Command

curl -X POST 'https://common-services.birdeye.com/integration/update/businessintegrationgroup?replaceTriggers=true' -H 'cache-control: no-cache' -H 'content-type: application/json' -d '{ "groupId": 264,"integrationGroupTriggers":[{"triggerId":30,"triggerTypeId":2}]}'
  • replaceTriggers=true - To replace existing trigger(s), enter the value for replaceTriggers as To add new trigger(s) to the existing list, the value for replaceTriggers should be false

  • 264 - The Group ID that was returned in the previous step will be entered here.

  • 30 - Enter the Trigger ID(s) that need to be added or updated to the integration.


2. Business Integration Mapping:

This configuration is developed to create actual business integration mapping. Each business integration mapping corresponds to the individual business location.

Copy this Curl Command

curl -X PUT https://common-services.birdeye.com/integration/add/businessintegrationmapping -H 'Cache-Control: no-cache' -H 'Content-Type: application/json' -d '{"businessNumber": 152820784670555,"active": true,"integrationGroupId" : 264,"integrationProperties":[{"propertyKey" : "facility.id","propertyValue": "311943"}]}'
  • 152820784670555 - Business ID- Enter the Business ID here

  • 264 - Integration Group ID: Enter the Integration Group ID which was returned when the Integration group was created.

  • 311943 - id: facility ID of the business. Refer to the section Steps to find Facility ID to find the Facility ID.


IMPORTANT: If the business makes any changes in the customer information after putting in actual pick up date, BirdEye will get multiple notifications to send review requests to the same customer. To restrict this, you will need to make below-mentioned changes before integration.

  • Login the BirdEye account and click on the ‘Campaigns’ tab on the left navigation rail.

  • On the ‘Campaigns’ page, hover over the ‘Templates’ tab on the top panel and from the drop-down menu click on the ‘Settings’ button.

  • On the ‘Settings’ page, turn ‘On’ the ‘Limit Email or SMS Frequency’ button to ‘YES’.

  • On the next drop-down menu, set the frequency to 7 days (or as per business requirement). After you have made all the changes, click on the save button on the bottom right.

Did this answer your question?