Investigate the broken join path behind today's Google Local Services lead reconciliation and isolate whether the gap is caused by ingestion, normalization, or post-create linkage.
The break is not one single bug.
There are two distinct failure modes in the current Google Local Services phone path:
CallRail_Call_Log__c row exists in Salesforce by phone or by the CallRail ID exposed in the email.CallRail_Call_Log__c.Intake__c after staff later create the Intake.INT-26052855362 (a0CUV00006j4W602AE) was created by Timmera House at 2026-05-28T19:32:58Z, about thirty minutes after the LSA call email time. It has blank source, blank UTM, blank GCLID, and no Matter.CallRail_Call_Log__c row exists for Andrew by phone +15029123690 or by CallRail ID CAL019e6ff89c5d77e9abd51e657113cde8.CallRail_Call_Log__c row, CRAIL-26052814183 (a5WUV000000FEXJ2A4), but no Intake or Matter exists for that phone match.INT-26052855360 and INT-26052855361, do have governed source values, but their matching CallRail rows by phone still show blank Intake__c. That proves the bridge is not reliably backfilled after Intake creation.60 same-day CallRail_Call_Log__c rows on May 28, 2026 were created by Nathaniel Hatfield.78 Google - LSA - Louisville CallRail rows in the last 30 days were also created by Nathaniel Hatfield, and only 41 of 78 had Intake__c populated.litify_pm__Intake__c, with none on CallRail_Call_Log__c or Web_Form__c.CallRail_Call_Log__c.Intake__c after Intake creation. The nearby local automation is limited to GCLID propagation and audit scripts.This path is operationally split between two human-created streams: