G13: native input mapping Check missed calls against later inquiries Purpose and compatibility A blank file is an input scaffold, not a native export or completed mapping. Preserve the exact column names/order and input names. Populate only from the documented native acquisition or explicit manual evidence. Stop if a required input, permission, privacy condition or coverage requirement is missing. Do not replace an old prompt until the named inputs and field-level mapping are reviewed. These files do not authorize login, setup, imports, account changes, message sending, publication, test submissions or spending. Contract status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible Compatible without mapping: false Required inputs Calls -> native-calls-template.csv Exact columns: call_alias,caller_alias,missed_at,answer_state,source_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. Later -> native-later-template.csv Exact columns: inquiry_alias,caller_alias,event_at,event_type,source_ref Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts. Scope -> native-scope-template.txt Required content: Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. Complete each required field from approved source evidence. Old files and reviewed mapping callback-policy-template.txt Original first line: Approved by/version: [required] calls-template.csv Original first line: call_id,contact_token,started_at,timezone,disposition,acknowledged_next_step,source_record_id forms-template.csv Original first line: form_id,contact_token,submitted_at,timezone,staff_acknowledged,source_record_id calls-template.csv -> Calls: verify call_id -> call_alias, contact_token -> caller_alias and source_record_id -> source_ref through the restricted checked map. started_at becomes missed_at only for an event meeting the approved missed-call definition. disposition must be interpreted using actual answer-status evidence. forms-template.csv -> Later: verify form_id -> inquiry_alias, checked contact_token -> caller_alias and submitted_at -> event_at; record actual event_type and source_ref. Capture other in-scope later-contact channels separately. staff_acknowledged is not proof of contact timing. callback-policy-template.txt -> Scope: carry the exact look-forward interval, timezone, late-data cutoff, matching rules, consent/opt-out rules and full inspection coverage. Retain ambiguous/unmatched calls; incomplete windows block absence conclusions. How to perform the handoff 1. Keep original exports and raw evidence unchanged in restricted firm storage. Check actual source fields, dates, coverage, privacy and access before mapping. 2. Prepare the distinct native inputs above. Record every mapped field, derived interpretation, missing value and observed source reference in Scope. Identically named columns still require source/evidence validation. 3. Create a separate minimized analysis workbook or text packet. Name tables/sections exactly as listed. A CSV file does not itself create a named Excel table. 4. Include the full completed Scope in the same AI-visible workbook or pasted packet. Verify exclusions, denominator, matching rules and unknowns. Do not hide raw client data on another worksheet. 5. Obtain the responsible reviewer’s approval of the completed mapping and evidence coverage before using the native prompt. Keep all blocked items visible. Any later external action is a separately authorized human step. Acquisition and privacy requirements Use approved minimized administrative metadata and aliases only. Aliases alone do not guarantee anonymity. Keep untouched exports/screenshots, identifying source maps, full documents and sensitive narratives in restricted firm storage. A hidden worksheet is not a privacy boundary. Do not insert credentials, payment/tax identifiers, raw client documents or unsanitized review text. Unknown is not zero, false, completed or absent. Existing authorized access to the correct source account and records; no new login, credentials, installation or permission grant is included. Responsible lawyer/operations reviewer approves scope, definitions and any later action. AI optional; use only approved minimized data and retain originals separately. No universal CRM/CallRail call-ID join or full later-contact export is established. The live account, entitlement, exact headers, records and field coverage have not been observed. Recipe acquisition / manual mapping instructions Export the calls with their real scope Location: Analytics > Activity > Call log > date/company filters > Edit Columns > Export > Excel Export the reviewed call period with actual answer status, tracking context and the available caller/call identifiers. Preserve originals and filter cover sheet locally. Staff checks which status qualifies as missed under the firm definition. Verification: Do not assume a voicemail or missed call implies no contact later; no transcript export is needed. https://support.callrail.com/hc/en-us/articles/5711277622029-Export-Call-log https://support.callrail.com/hc/en-us/articles/5711366294285-Viewing-caller-timelines-with-visitor-tracking Check later CRM assignment and inquiry evidence Location: Lawmatics top-right phone icon > Assigned / Unassigned / All Callers; matter Activities; CallRail call Timeline Manually establish exact cross-tool record links or an existing staff-verified caller/matter map for the look-forward window. Capture later inquiry timestamp, channel and record ref. Check the source period extends through the full window. Verification: Phone matching is not proof of a unique person: shared/recycled numbers and several matters require review. Unassigned callers are not necessarily unreturned calls. https://help.lawmatics.com/en/articles/10699987-callrail-integration https://support.callrail.com/hc/en-us/articles/5711366294285-Viewing-caller-timelines-with-visitor-tracking Make the checked, minimized handoff Location: Restricted original workbook > separate analysis workbook > Scope worksheet Use only exact, staff-approved matching keys. Keep all ambiguous and unmatched calls. State allowed look-forward interval, timezone and late-data cutoff. Keep untouched original exports/screenshots and the identifying source map in restricted firm storage. Build a separate minimized analysis file; do not hide raw client data on another tab. Include the complete Scope/coverage note in the AI-visible workbook or prompt. Use aliases and administrative metadata only. Unknown is not zero, false, completed or absent. Verification: Every field has an observed source or an explicit missing reason; staff assignments are marked editorial, not native. https://support.microsoft.com/en-us/excel/merge-queries-power-query https://help.lawmatics.com/en/articles/10699987-callrail-integration Do not proceed when - Missing stable staff-verified map, missing answer-status definition or incomplete later-contact window. Scope template requirements Full approved scope, source account aliases, date filters, date basis/timezone, as-of capture time, definitions, source-to-alias map provenance, matching rules, inspected/excluded records, permission/privacy limits, missing-data reasons, coverage and responsible reviewer. Include recipe-specific policies, versions and tests. Scope must be inside the AI workbook or pasted packet, not merely a separate unprovided file. Old examples and validation limits Legacy synthetic examples and negative cases belong to their old prompts. They do not automatically test the native route and must not be fed into a new prompt without an explicit reviewed mapping and separately approved test design. These new files contain no synthetic values, source exports, account results or live-test evidence. Documentation-checked component path; proposed workflow, not tested Public official documentation checked 2026-10-15; no login, export, live query, import, installation, configuration, message or client workflow was executed. Local validation covers only exact scaffold schemas, placeholder presence, blank CSV rows and required warnings. It does not establish live account coverage, native export validity, successful integration or completed workflow tests.