Darrell (darrell@shield-legal.com)
2024-06-12 13:27:05

Team, thank you again so much for the time yesterday. I know some of you prefer Slack over email so I'm sending to both. As promised, I’m attaching a spreadsheet to show our duplicate counts along with a created dates like we discussed. We can resolve this and future proof with a simple strategy change outlined herein. I’m also attaching a simple workflow diagram to indicate the change I’m suggesting. Finally, below I’ve outlined how we can resolve it with incremental changes. With this plan, by default we will have our system of record.

Notes: • The Excel attachment is part of an export of records from Law Ruler • Export was taken from Jan 1, 2023 - Today • Export contained 367,193 Lead records that were inserted into Law Ruler over that time period.
• There were 54,386 duplicate records created resulting in 27,193 duplicate leads with different lead IDs.
• There were 50,706 leads created with no contact information. Goals: Integrate Salesforce (as a pass through) between Leadspedia (and other sources) and Law Ruler through a series of small manageable steps that provide incremental changes. Below are the changes we can effect immediately.

Salesforce serves as a centralized platform to aggregate lead data from Leadspedia and other sources, then passthrough to Law Ruler, consolidating all lead information in one database and allowing the below changes overnight.

• Create validation rules to enforce data quality standards for fields like email address and phone numbers.
• Set up validation rules to ensure that essential fields are not left blank • Enable duplicate management in Salesforce to identify and prevent creation of duplicate • Configure duplicate rules for exact (not just fuzzy) matching • Use data enrichment services to validate email addresses, phone numbers, and other lead information • Set up lead assignment rules to automatically assign to campaigns and dialer lists - Remove the manual processes • Regularly monitor conversion rates, lead quality, and pipeline metrics • Dynamically route leads based on calculated value through a series of journey checkpoints • Salesforce's robust reporting and analytics capabilities can transform the flatirons reporting.

IPOE Salesforce.pdf
Duplicate Lead Records Jan 1 2023 - Today.xlsx
Ryan (ryan@themedialab.agency)
2024-06-12 13:30:32

*Thread Reply:* @Tony @Cameron Rentch, this is basically a "baby step" to allow TIP to have a Salesforce instance to control the deduplication, validation and storage of all the IDs we need across Leadspedia, LawRuler to track and trace leads.

Over time it could be used as a way to pilot Salesforce for Intake Operations versus LawRuler.

@Darrell, do know that many leads come from phone calls only and thus won't have contact information FYI. It's not all "errors" FYI.

Darrell (darrell@shield-legal.com)
2024-06-12 13:41:27

*Thread Reply:* @Ryan Yes, completely understand and 100% agree with you there. The recipient database should be pushing back on these as well

☝️:skin_tone_4: Ryan
Ryan (ryan@themedialab.agency)
2024-06-24 14:07:36

*Thread Reply:* @Darrell, you have the greenlight from us to create a TIP Instance of Salesforce that will act as the receiving system of leads from Shield and Brandlytics' use of Leadspedia to orchestrate delivery of form-leads to LawRuler and their phone numbers in the form-data to the FiveNine dialer.

@Darrell, meet with @Brian Hirst to first, and only first, "asses the amount of campaigns / form-fields data you must pass and where it MUST go in LawRuler". Brian knows this better than anyone and the data goes in LawRuler in places by strict design of microservices that serve Cameron and his media team.

Once you have that whole project scoped out, setup time with me, @Tony @Nick Ward and @Brian Hirst so we can get your timeline, implementation plan, etc.

FYI @Nick Ward @Tony @Cameron Rentch

🙏 Darrell