Slack Export - #mpdm-cameron--darrell--jturner--ryanvaspra--jsantana-1

Public Channels

Private Channels

Direct Messages

Group Direct Messages

Cameron Rentch (cameron@internetthings.com)

2024-12-23 17:03:21

@Darrell @James Turner I know you both have independently created and mapped out the work-flows of each department and how they process each lead and claimant from intake all the way through post acquisition. Can you guys please post here what you hvae done to date? Me, @Joe Santana and @Ryan need to review. Happy Holidays!

👏:skin_tone_4: Ryan

Ryan (ryan@themedialab.agency)

2024-12-23 17:04:31

We meet Tuesday to review it, we asked for it that Tuesday

James Turner (jturner@shield-legal.com)

2024-12-23 17:11:17

Hey there- We are making great progress but still getting it all sorted out with department supervisors out on my end. Currently in the process of attempting a Lead "swim lane" that travels through all of the potential status's

👏:skin_tone_4: Ryan

Darrell (darrell@shield-legal.com)

2024-12-23 17:38:19

@here Hello All! Happy Holidays! Yes, happy to include all of it here. I'll start with the most recent work.

DiCello Levitt - This example is for NEC but will scale to any case and we should be prepared to populate all intakes (Signed Final) within 72 hours of request

Key Flow Highlights:

Shield Legal API Integration: • Start: Shield Legal posts a new Account via the API, including the following required fields: ▪︎ First Name (Required) ▪︎ Last Name (Required) ▪︎ RecordTypeId: 012Dn000001Tom7IAC (Individual) ▪︎ Phone ▪︎ Email ▪︎ DOB ◦ LawRulerId (Custom Field)
The RecordTypeId indicates that a Person Account should be created, which automatically creates the associated Contact object.
Litify Trigger - AllAccountTrigger: • Upon receiving the Account from Shield Legal, Litify will return the AccountId and proceed to trigger the AllAccountTrigger. ▪︎ For “Individual” Record Type: The trigger will set the Account name to [FirstName] [LastName] and enforce a 1:1 relationship with the Contact record. ◦ It will also update Person Information fields and display names for related Intakes & Matters.
Internal Custom Flow - Intake Creation: • A custom Salesforce Flow will automatically create an associated Intake record, populating known fields, including: ▪︎ AccountId (from the previous step) ▪︎ RecordTypeId: Converted ▪︎ Status: Converted ◦ LawRulerId (Custom Field)
Assumption/Feedback Request: I’ve set the Intake Status to always be Converted by default. However, I’m wondering if this status should always be Converted or if we should introduce logic to vary the status based on specific conditions (e.g., based on intake progress or other factors). Can we discuss the appropriate status logic?
Litify Trigger - AllIntakesTrigger: • Upon Intake creation, the AllIntakesTrigger will run to: ▪︎ Set the Display Name for the Intake. • Populate Intake fields with Account/Party details: • Intake.FirstName = Account.FirstName • Intake.LastName = Account.LastName ◦ Intake.Email = Account.Email

☝️:skin_tone_4: Ryan

Darrell (darrell@shield-legal.com)

2024-12-23 17:44:08

This is what we built - I feel like some of this may require detail and I'm happy to meet and discuss. Abe seems happy with the progress. We met earlier today.

Shield Intake Data Process Map (1).pdf

Darrell (darrell@shield-legal.com)

2024-12-23 18:08:33

I've completed these three apis for DL in their test environment and Dustin is working on sending these accounts over to test now. In the meantime I'll continue to build in prod.

Non related to 'Integrations' - I built an Intranet in Salesforce based on Mark and Adam's bullet points, and I'm working those requirements when not focused on Integrations

Lastly with DiCello Levitt - I built out Sales Cloud for Brian O'Mara and team. Here is our process map for this build. These are for 'Monitored/Non-Monitored' investment clients to include the investors/Funds Brian has shared with us. I have their entire UI built and ready to receive in Production. All questionnaire and intake data when ready.

Screenshot 2024-12-23 at 4.07.54 PM.png

Darrell (darrell@shield-legal.com)

2024-12-23 18:21:24

My work with with Jarret and TJ (BFG/SBA Loan Group) area related to a migration out of Hubspot to their already subscribed Salesforce environment using standard features. It saves them 30k+/year in HubSpot subscription fees. Along with this I'm building out Sales Cloud.

Darrell (darrell@shield-legal.com)

2024-12-23 18:23:34

I'm not sure you all want to see all of the project docs for that here, but happy to share and review with all

Darrell (darrell@shield-legal.com)

2024-12-23 18:29:06

With BG we built the mapping from Law Ruler to Salesforce for AFFF. Here is that mapping. We have yet to fire on this as I was waiting for word.

In addition, I created this same mapping for all sex abuses cases (prior to knowing we were moving Integrations to Google Cloud).

I'm now waiting on the Integrations team to process the triggers form Google Cloud.

LR Integration Form (2) (1).xlsx

Darrell (darrell@shield-legal.com)

2024-12-23 18:30:11

Happy to meet and discuss detail on all of this as needed team! TYSM for asking.

Ryan (ryan@themedialab.agency)

2024-12-23 18:45:29

Thanks @Darrell

James Turner (jturner@shield-legal.com)

2024-12-26 14:58:32

Progress update on all this -The ultimate goal is to have an in-depth flow on the SOP of each department, but for the sake of understanding a "General lead lifecycle from the perspective of LR status" I put this together... It begins pre-intake and provides both a 1000, and 100ft view of how a lead moves through each department, the checks and balances in place for each, and the lead status changes as it moves through.

Currently I have met with one supervisor from each "Major" department, to have it reviewed for accuracy. (Screeners, Closers, PD, CSP, and VSS) During this time I learned there are apparent issues of understanding how departments run even at a supervisory level.

Because of this I plan on doubling up and meeting with a team lead for each department to get closer to "ground level" view of what's actually happening and learning about the specific use cases to fill in the gaps.

Currently I am debating adding to scope to set up a google sheet with department reasoning for each status, the trigger on what causes it once the flowchart is set up. The reason for that is a general lack of understanding across the company why different status's exist and what they are used for. (How a change at one department, may affect another)

Strat and Ops - Pipelines - Lead Lifecycle.jpg