Objective

Investigate the converted call leads with CallRail API evidence so the offline conversion upload uses real call timing and not stale call-log status labels.

What Was Accomplished

• Queried live Salesforce CallRail call logs linked to converted Litify intakes.
• Fetched the matching CallRail API record for each CallRail ID.
• Exported redacted and sensitive investigation artifacts locally.
• Confirmed 11 CallRail API records across 9 converted intakes.
• Confirmed every CallRail API GCLID matched the Salesforce call log GCLID.
• Confirmed CallRail API lead_status was blank on all 11 records, so CallRail is not currently providing a final signed/converted label for these calls.
• Confirmed 7 calls happened before Litify conversion and 4 calls happened after the matter had already converted.

Key Findings

• The Not Signed value is a Salesforce CallRail_Call_Log__c text snapshot, not authoritative final matter status.
• The linked Litify intake and matter are the reliable source of truth for conversion.
• Five converted call-attributed intakes remain appropriate for the offline conversion upload because the call happened before conversion.
• Four converted intakes should stay excluded from the upload because the CallRail call happened after the matter was already converted.
• INT-26041354174 had two same-day calls before conversion; the first was marked Not Signed and the second Signed. The Litify conversion later that day makes the intake legitimate for upload.
• INT-26041454202 had an abandoned first call and a long answered follow-up before conversion. The conversion happened after those calls, so the later answered call supports attribution even though the call-log text says Not Signed.

Artifacts

• Redacted CSV: /Users/samaguiar/Documents/Projects/Repos/sail-litify-hub-mdt/Litify_AI_Integration_Project/output/callrail-conversion-investigation/2026-05-28/callrail-api-investigation-redacted.csv
• Redacted JSON: /Users/samaguiar/Documents/Projects/Repos/sail-litify-hub-mdt/Litify_AI_Integration_Project/output/callrail-conversion-investigation/2026-05-28/callrail-api-investigation-redacted.json