Check missed calls against later inquiries
Get the source data and prepare the review

Documentation-checked component path; proposed workflow, not tested

WHAT WAS CHECKED
Public official documentation and supplied candidate artifacts only. No product login, account exports, client data, installation, credential access, external writes, advertising spend, template imports or live tests. Proposed prompts do not prove a feature supports every requested field. Missing required source data blocks execution.

BEFORE YOU START
- 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.

DATA ACQUISITION LIMITS
- No universal CRM/CallRail call-ID join or full later-contact export is established.

STOP IF
- Missing stable staff-verified map, missing answer-status definition or incomplete later-contact window.

KEEP THE ANALYSIS COPY SEPARATE
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.

INPUT FORMAT LIMIT
All capitalized analysis tables and alias fields are editorial contracts. Native exports retain real vendor headers; mapping is explicit. No blank starter template is evidence of available data.

NATIVE REVIEW INPUTS
version: 1
status: Requires distinct native-input templates or an explicit reviewed mapping; existing kit is not drop-in compatible
compatibleWithoutMapping: False
existingKitFilesInspected: - file: callback-policy-template.txt
firstLine: Approved by/version: [required]
- file: calls-template.csv
firstLine: call_id,contact_token,started_at,timezone,disposition,acknowledged_next_step,source_record_id
- file: forms-template.csv
firstLine: form_id,contact_token,submitted_at,timezone,staff_acknowledged,source_record_id
requiredNativeInputs: - name: Calls
kind: editorial_table
proposedDistinctTemplate: native-calls-template.csv
columns: - call_alias
- caller_alias
- missed_at
- answer_state
- source_ref
acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.
- name: Later
kind: editorial_table
proposedDistinctTemplate: native-later-template.csv
columns: - inquiry_alias
- caller_alias
- event_at
- event_type
- source_ref
acquisitionRequirement: Populate only from the recipe’s documented export or explicit manual evidence capture. Existing blanks and synthetic fixtures do not supply facts.
- name: Scope
kind: approved_text_section
proposedDistinctTemplate: native-scope-template.txt
requiredContent: 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.
templateFilesCreatedByThisTask: False
requiredGate: Kit owner must add the named inputs or document field-level mapping before replacing an existing kit prompt. Preserve the old kit contract; never rename headers without acquiring missing evidence.

OPEN THE INPUT MAPPING GUIDE
NATIVE-INPUT-MAPPING.txt
Use the distinct native input scaffolds listed below. Complete them from the acquired, reviewed evidence and include every required scope section in the AI-visible packet. Existing synthetic examples exercise the original review prompt only. They are not acquired evidence or a test of this native chain.

Calls: native-calls-template.csv
Later: native-later-template.csv
Scope: native-scope-template.txt

STEP 1: Export the calls with their real scope
Tool: CallRail
Open: Analytics > Activity > Call log > date/company filters > Edit Columns > Export > Excel
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

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.

Expected output: Native call Excel; exact available identifiers inspected locally.
Use it next: Open caller Timeline for candidate missed calls to inspect later calls/forms/text events.
Check: Do not assume a voicemail or missed call implies no contact later; no transcript export is needed.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
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

STEP 2: Check later CRM assignment and inquiry evidence
Tool: Lawmatics / CallRail
Open: Lawmatics top-right phone icon > Assigned / Unassigned / All Callers; matter Activities; CallRail call Timeline
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

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.

Expected output: A local restricted matching map and evidence ledger.
Use it next: Replace caller identities with staff-created aliases before downstream analysis.
Check: Phone matching is not proof of a unique person: shared/recycled numbers and several matters require review. Unassigned callers are not necessarily unreturned calls.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://help.lawmatics.com/en/articles/10699987-callrail-integration
https://support.callrail.com/hc/en-us/articles/5711366294285-Viewing-caller-timelines-with-visitor-tracking

STEP 3: Make the checked, minimized handoff
Tool: Excel / source-record reviewer
Open: Restricted original workbook > separate analysis workbook > Scope worksheet
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

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.

Expected output: Calls(call_alias,caller_alias,missed_at,answer_state,source_ref); Later(inquiry_alias,caller_alias,event_at,event_type,source_ref); Scope(window,coverage,matching_policy)
Use it next: Format each approved range as a named table. Carry source-row references and coverage into the analysis workbook.
Check: Every field has an observed source or an explicit missing reason; staff assignments are marked editorial, not native.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.microsoft.com/en-us/excel/merge-queries-power-query
https://help.lawmatics.com/en/articles/10699987-callrail-integration

STEP 4: Ask AI to inspect the checked inputs
Tool: Excel Copilot, optional
Open: Analysis workbook > Copilot icon at lower right > Chat only
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: downstream_application_ai

Open the minimized workbook containing the named tables and Scope. Paste the exact prompt; if unavailable, perform the same rule checks manually.

PASTE THIS PROMPT
Match Calls to Later only by the exact approved caller_alias and the stated look-forward window. Return missed calls with evidenced later inquiry, no observed later inquiry with complete coverage, or unknown due to ambiguity/incomplete window. Show source refs and time difference. Never use fuzzy names, infer identity from location, label a caller lost, or trigger outreach.

Expected output: Missed-call reconciliation with ambiguous/unknown queue.
Use it next: Copy checked results into a new Review sheet, retaining source references and unresolved blockers.
Check: Staff rechecks every candidate match and the full later window.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel

STEP 5: Human review and final action
Tool: Responsible firm reviewer
Open: Internal Review worksheet / review document
Access needed: Existing authorized access and relevant plan/region feature; exact live subscription and permissions not tested. No setup or persistent access changes included.
AI role: not_an_ai_step

Intake staff reviews unresolved calls using the original systems and decides whether any authorized follow-up is appropriate.

Expected output: Checked reconciliation and internal questions.
Use it next: Human creates an approved task or communication separately.
Check: No automatic callback, text, data merge or lead creation.
Documentation limit: The source verifies the component feature; workflow prompts, schemas, manual captures, checks and handoffs are proposed editorial adaptations.
Source documentation:
https://support.callrail.com/hc/en-us/articles/5711366294285-Viewing-caller-timelines-with-visitor-tracking
https://help.lawmatics.com/en/articles/10699987-callrail-integration

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- The live account, entitlement, exact headers, records and field coverage have not been observed.

USING THE FILES IN THIS KIT
Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs.

The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.
