Moving on without a Piece of Data

There are times when a CSL may with to move processing along without a particular piece of data.  Reasons could include:

  • The customer or vendor is not sending the file
  • Delays due to bad collect files
  • An integration is taking too long

Required Data Types

We are able to move on without the following optional pieces of data:

  • Call Tracking
  • Chat
  • Direct Mail
  • Email Opens
  • Other Equity Mining

The following are required and we cannot proceed without them:

  • DMS Sales
  • CRM Leads (except in rare instances where the dealer does not have a CRM or cannot export usable CRM leads like 180 CRM)

 

During Onboarding

If a dealer is still in Onboarding and you wish to move on and process the dealer's MTSA data without a piece of their data (an open Onboarding task):

🔴 If you do not want us to keep pursuing the missing data

  1. In the Rocketlane task, create a Private update in the Chat explaining that you want to skip this data.
  2. Set the Rocketlane task status to SKIP.
  3. If there is other data that we still need to get, STOP here.
  4. If you are satisfied that we have all data we need for processing, change the Rocketlane Project Status to Integration Complete.
    1. ✴️ This will update the Ops Overview Processing Status to “Waiting on First Month”.  
      1. 🚦 Depending on the dealer's Clarivoy Start Date, Make may subsequently change the Ops Overview Processing Status to “Working On It" and add the appropriate Processing Months.
        1. 🚨 When the Ops Overview Processing Status is set to “Working On It”, Monday Automations will move the item to the Active group.
  5. If this is a group onboarding, Zapier will only update 1 item's Ops Overview Processing Status.  You will need to manually set the other Ops Overview items' Processing Status to “Waiting on First Month”.  Automations will take over from here (see step 4a) and if it is time to start processing the dealer's first month of data, a combination of Make and Monday automations will move the Ops Overview items into Active processing.

NEVER change an Onboarding dealer's Ops Overview status to “Working On It” without first setting their Rocketlane Project Status to “Integration Complete”.  Doing so could cause delays later when the Rocketlane Project Status is eventually set to “Integration Complete”.

 

🟢 If you DO want us to keep pursuing the missing data

  1. Do not change anything in the Rocketlane task.  Leave the task Status alone.  Ops will continue to pursue the data from the Rocketlane data task.
  2. If you are satisfied that we have all data we need for processing, change the Rocketlane Project Status to Integration Complete.
    1. ✴️ This will update the Ops Overview Processing Status to “Waiting on First Month”.  
      1. 🚦 Depending on the dealer's Clarivoy Start Date, Make may subsequently change the Ops Overview Processing Status to “Working On It" and add the appropriate Processing Months.
        1. 🚨 When the Ops Overview Processing Status is set to “Working On It”, Monday Automations will move the item to the Active group.
  3. If this is a group onboarding, Zapier will only update 1 item's Ops Overview Processing Status.  You will need to manually set the other Ops Overview items' Processing Status to “Waiting on First Month”.  Automations will take over from here (see step 4a) and if it is time to start processing the dealer's first month of data, a combination of Make and Monday automations will move the Ops Overview items into Active processing.

NEVER change an Onboarding dealer's Ops Overview status to “Working On It” without first setting their Rocketlane Project Status to “Integration Complete”.  Doing so could cause delays later when the Rocketlane Project Status is eventually set to “Integration Complete”.

 

After Onboarding

If a dealer has completed Onboarding and you wish to move on and process the dealer’s MTSA data without a piece of their data:

🔴 If you do not want us to keep pursuing the missing data

  1. Set the individual task on the Monthly Tasks board status to SKIP.  
  2. Do not tag @Ops.  There is no action for Ops to take at this point since you will be setting the task status to SKIP.
  3. The dealer's Ops Overview will move on to the appropriate status at the next update via automations (see When does Ops Overview update?).
  4. IF TODAY IS WITHIN THE LAST 3 BUSINESS DAYS OF THE MONTH:  
    1. Go to Ops Overview and QA the dealer's data.
    2. Change the Processing Status to Approved for Prod in order to get the dealer's data into PROD before the board resets.

 

🟢 If you DO want us to keep pursuing the missing data

  1. Do not make any changes to the task on the Monthly Tasks board.
  2. On the Ops Overview board item, note your approval in the updates (“I approve moving on without XXX data this month”)
  3. Depending on the timeline:
    1. IF TODAY IS WITHIN THE LAST 3 BUSINESS DAYS OF THE MONTH:  
      1. QA the dealer's data.
      2. Change the Processing Status to Approved for Prod in order to get the dealer's data into PROD before the board resets.
    2. OTHERWISE:
      1. Change Processing Status to Prelim QA
      2. Ops Team will Prelim QA the data the next time they perform Prelim QA (either the same day or the next day).  If the data is good, they will move it on to Automatch (and potentially CSL QA based on the task dates).

 

Moving Part of a Group to Prod

If you wish to push part of a group to PROD, but not all rooftops, see Pushing partial groups to prod.

 



Can't find what you're looking for?

Our team is here to help.

Contact Support