Good morning everyone I want to bring this into your attention that I'm showing 7 paraquat 12 signed e-sign re-triggered leads show up on page 0 dashboard. @James Turner please take a look at the screenshot below
They would still be billable, and when they triggered, they would show up by design
*Thread Reply:* They are 2023's leads and re-triggered yesterday.. so I don't think they would be billable
I wonder if we should just set the filter default to exclude them James?
Interesting- only way they should be showing up is if the earliest E-Sign date was in fact yesterday, or these leads never got signed in the activity log and got changed to a billable status. (We would then grab the date of the earliest billable status if it's deemed billable but has no E-signed date)
*Thread Reply:* We might be able to use lead_contract (where serverstatus=Completed) as a backup if the activity log does not show an esign.
*Thread Reply:* Lets definitely poke more at this after we figure out this inital set of Re-Triggered leads
Thanks for bringing this to my attention Zek!
I'll dig a little deeper into the leads activity and see why they are on there.
@Dustin Surwill has joined the conversation
Taking a look at these leads, they all appear to be copied / Imported from an old case so their history of original e-sign is not included. That is why their 'billable date' is considered yesterday when they hit a billable status for the first time.
What is odd is the 'Secondary' campaign (Paraquat - Dicello Filing Project) here is the campaign that actually came first, and includes the usual intake process. It seems like these are secondaries that aren't labeled as secondaries.
Pulling in Brittany and Dustin to see if they have a better idea of what kind of unusual process was done for these leads.
@deleted-U04GZ79CPNG @Dustin Surwill Hey there~ We got a notification on the financial end of these leads (Example) hitting a billable status for the very first time yesterday (Retriggered) and upon inspection, found some lead history I'm not used to seeing.
Findings:
• It looks like these are being treated as an intake campaign, but are copies of an unverified lead.
• These leads all have a secondary lead ID that came before this lead in the vitals.
• The 'secondary' lead referenced in the vitals is in a secondary status, but contains the original e-sign and usual intake process.
• The 'secondary' campaign it refers to is
Thank you!
I was told by @deleted-U04GG7BCZ5M that Signed e-Sign QA & Signed e-Sign FINAL - SENT should be treated the same as FINAL, so I set them to re-triggered to do the DL backfill
Interesting- After a lead gets triggered to be sent via Integrations on that Re-Triggered status, does it ever return to it's previous status? Like is RE-TRIGGERED a 'temporary' status?
*Thread Reply:* No, most of the time the previous status triggers an email to the firm therefore we can not put it back
*Thread Reply:* And do we normally send the Secondary AND the intake or just one?
*Thread Reply:* Usually just the intake
*Thread Reply:* but if secondary integration they are separate because we have to send when intake finalizes and the secondary hasn't been conducted yet
*Thread Reply:* What's odd here is it looks like the secondary happened before the original by lead ID https://tortintakeprofessionals.lawruler.com/update-lead.aspx?lead=346128&Case=10
Hello! There are ~15 profiles from the paraquat 12 campaign that have this same situation: They were among the first few clients signed up and when the CSP agents got the list of clients to begin working on secondary interviews, they took the original intake file, turned it into a case (cannot be undone in LR), and changed the case type to the secondary interview case type. They then began completing the secondary interview in that profile. We need the intake and secondary files to be separate and it was less work for us to make duplicate intakes and input the responses than it would have been to revert back the secondary and redo the secondary interview. So, we made another profile, input all of the responses, and made them signed e-sign QA status.
This was before we knew about how to update LR with API and no one in my department could code. The import wizard at the time was only accepting CSVs of ~20 columns and it would take 3+ hours to map one import. We can swap them back now and make the one that was originally the intake the intake again and make the copy into the secondary interview to clean this up. I can grab a list of the affected profiles as well if you don't already have that