Objective

Pull a wider recent Google LSA sample through the CallRail API to determine whether Andrew Cummings was a one-off or part of a broader ingestion failure, then add a three-way mailbox plus CallRail API plus Salesforce check to the LSA reconcile workflow.

What Was Accomplished

• Created reusable script scripts/audit-lsa-callrail-ingestion.mjs in the canonical Litify project.
• Ran a 30-day audit from 2026-04-29 forward against live CallRail API and live Salesforce LITIFY_ORG.
• Created workflow doc docs/google-lsa-three-way-reconcile-workflow-2026-05-29.md to standardize future reconciles across mailbox, CallRail API, and Salesforce.
• Updated Skills/litify-integration-ops/SKILL.md so future Google LSA reconcile work routes through the three-way check.
• Appended the benchmark and file paths to docs/litify-environment-diary.md.

30-Day Benchmark

• LSA API calls in scope: 112
• Matched Salesforce CallRail_Call_Log__c rows: 106
• Missing Salesforce rows by CallRail_ID__c: 6
• Matched Salesforce rows with blank Intake__c: 56
• Matched Salesforce rows linked to Intake: 50
• Matched Salesforce rows with blank Call_Summary__c: 9
• Source split: Google - LSA - Louisville = 80, Lexington LSA = 32

Interpretation

Andrew Cummings is not a one-off. Missing Salesforce CallRail row creation is a real recurring failure mode, but the larger operational problem is blank Intake__c on already-created Salesforce CallRail rows. The three-way workflow now keeps missing_salesforce_row, matched_blank_intake, and missing_salesforce_summary as separate exception classes.

Key Files

• Script: /Users/samaguiar/Documents/Projects/Repos/sail-litify/Litify_AI_Integration_Project/scripts/audit-lsa-callrail-ingestion.mjs