It would be really helpful to get an updated report of duplicate cases pushed into the system. With Abrego, much of the info pushed into the UDFs was different, so when I was trying to determine whether it was a duplicate I was unable to tell.
Also, DOBs, addresses, SS# (when we have it), email addresses, etc., are not always being pushed into the contacts and those are critical.
Finally, the cases are ALL coming over with a Subtype of Tier 1, even though they aren’t all Tier 1 cases. This is an issue raised numerous times and it is not something we can easily fix on our end, but rather, are forced to go in case by case to review and correct.
This is from meadow. if we could have an explanation or solution going in to our weekly meeting today id be appreciative!!! :)
Hey Alex, I am checking into the audit report I sent Ashley like a week ago for this dup. I am 90% certain I have told her this is a duplicate so they could delete it.
As for the tier 1 this is the value intake or PD is putting on the leads. We just fixed the formatting so populate in the field.
so how do we get the tiering situation fixed from us to them? is there a troubleshoot way to resolve this? i can understand why its a big thing due to the mass volume of cases they only want to concentrate on tier 1's
I know previously pd was deleting the video games played answers if it was not minecraft, roblox or fortnite. It would not surprise me if they are just marking all the leads as a tier 1. Not saying PD is doing that but this is something we need to get with PD on if this is occurring.
Well we fixed the formatting to included Tier because before the SA system was not catching the data for the field. As for the value, ie 1 , 2, or 3. We may have to manually and painstakingly going through case by case and ensure it has the correct value. I will talk with Dustin about some automation solution and let you know.
I am a bit under the weather today so I wont be able to do todays meeting, but I will work over some solutions and get them to you by 2ish so when you have the meet with then at 3 I believe we will have a response at least.
@deleted-U07EH86AAN9 send to Dustin and I too. @deleted-U06F9N9PB2A we can join the meeting with you today. Can you send us the invite?
https://us06web.zoom.us/j/89458065157?pwd=eS7yfaIAHfD7O1lDJ08khSJo9nwdF2.1
Meeting ID: 894 5806 5157 Passcode: 963940
@Dustin Surwill has joined the conversation
Spot checked some of the leads in final status most are marked as tier 1, only found a single lead in tier 3
did we batch over the tier 2/3?? i know the auto push is only for tier 1's
*Thread Reply:* Yes we are piping over all leqds. Whatever intake/PD leaves in that tier field is what shows up in SA. For the pipeline integrations setup.
So quick update. • currently pulling a report of all sends so meadow can see the dups • Smart Advocate engineers are currently looking into the weird bug of false positive deliveries. Ashley is on that email thread ◦ For the interim We are running a audit report twice a day, morning and once in the evening to catch any failed send. @deleted-U06F9N9PB2A
Also when we ran the failure report in the am nothing failed. 13 leads posted correctly with all three case types. Levinson, Ghozaland, crump
Here is report I am going to send to Meadow. I will only send the Output sheet since they do not need the rest of the data. Any concerns before I send it?
https://docs.google.com/spreadsheets/d/1bM9FusVVnV-vDdiSs1uh5sD1SpF-Xu2ThWsVVVZUn-Q/edit?usp=sharing
im sure whatever you came up with is good @Dustin Surwill just cc me in the email so they know were all on the same page thank you for coming up with this!
and maybe just quickly put explanations for the columns in very very simple terms
I had to leave, I will work with Ahsan in the morning to pull data from Meadows system to include as well
Morning @deleted-U06F9N9PB2A
The report name we need access to is udf report
Hey Alex, my calendar is pretty free. Did you want to just add in like a 30 minute meeting prior to the usual Tuesday meeting so we can discuss the UDF report?
@Dustin Surwill for vis
hi we actually cancelled this tuesdays due to the holiday... it really should only be a 5 minute walkthrough to show ashley how to pull it
im kind of putting it on them to manuever so we are covering our bases as being extra helpful
Gotcha. Are you good with an early Monday meeting? Say 10 or 11am?
lets let them call it, the offer was more goodwill based lol
Hi can u confirm the mapping was done for JDC to accommodate the signer field? They asked in our 2pm meeting and I said yes but just want to confirm we’re good :)
Chris just confirmed the other fields are added in. Updating the mapping and pushing into production
Not since 10 AM when he said he was working on it
dont push anything.... long story but he needs to have some internal convos w. meadow
hi ----- time sensitive.. list of field and field types for VGA intake/sec by end of day?
Hi pls let me know if those field lists take longer I need him to swap favors so have to fulfill my end. My numbers
Gaming Addiction - ML - Levinson - Justin Michael Wayne Rash 629415 --- 1/31 not in SA....What is going on?
Timeline is 1/24/25-2/7/25, 34 leads not sent. Already spot checked for dups. Will resend now
ok pls send the leads w. coordinating SA id when sent so i can send to them
I have only check levinson. Once sent will check crump then give a sheet with all the ids for you
*Thread Reply:* 0, Seems this issue only impacted levinson
Why weren’t they sent and why weren’t these caught in the checks we set up?
The checks we set up were looking for issues from the vendor (SA) not our system. The problem was a missing mapping key that we fixed 2/13
Ok make sure we have reporting for both for all campaigns. We need to be catching what should send vs what was sent. Can’t have this be a recurring issue.
hi i have a dr appt at 3 so cant make vga and they wanted to reschedule so i can be there so we will lump VGA after JDC thurs.
Thanks for hopping in today — he’s happy and inspired. Appreciate it!
becker gearing up for a rahul argument..... @deleted-U07EH86AAN9 lololol