Law Firm Agents
CRM & Follow-upProposed workflow

Find missing call outcomes and loss reasons

Flag calls and closed leads that lack an approved outcome code.

Tools for the documented steps

These products support separate steps. Their presence does not imply a tested connection or endorsement.

Practice relevance

Cross-practice idea · A general operational method. Review the stated tool and jurisdiction limits before use.

The problem

Flag calls and closed leads that lack an approved outcome code.

Why it matters: Blank or inconsistent call outcomes make follow-up and reporting harder to trust. A missing-code review asks the record owner to confirm what happened rather than turn unclear notes into a reason for closing a lead.

Sources & evidence

Proposed / not tested. The public source describes the problem. Documentation supports only the stated method components; no result from this recipe has been verified.

What’s been verified

Source methods and reported problems have been reviewed. We have not run the adapted workflow. The sample below describes expected behavior on synthetic data, not a customer result.

What to measure: In a synthetic pilot, count correctly found exceptions, false alarms, and unresolved inputs. No time or cost saving is assumed.

Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. Several CRM jobs come from the same firm discussion, not independent firms. We wrote these prompts. The adapted workflow hasn’t been tested.

Suggested approach

Start when: End-of-day call/stage export

  1. locate substantive calls with missing outcomes and staff-closed leads without reason codes
  2. Keep source references and report unknowns instead of filling gaps.
  3. The responsible reviewer checks the report before any separately approved action.

Limits and review

The assistant drafts or reports only. Check source records and review the output before a human performs any separately approved send or change. No automatic legal decision, money movement, account connection or publication is included.

Who reviews it: No automatic case qualification or decline. Do not convert vague notes into legal determinations; preserve original notes and approval history.

What you need

Your firm-approved AI assistant · prepared files

  • 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.
  • Use synthetic inputs first. Keep real data in firm-approved accounts and processing, with appropriate access, confidentiality and retention controls. Aliases alone do not anonymize records. Never paste credentials, API keys or unnecessary client details.

How to use

Documentation-checked component path; proposed workflow, not tested

Before you start
  • CallRail Excel is verified; universal staff disposition and Lawmatics loss-reason fields are not automatic.
Check access and setup
  • The live account, entitlement, exact headers, records and field coverage have not been observed.

  1. Download the actual call log

    CallRail · Analytics > Activity > Calls > Call log > date/company filters > Edit Columns > Export > Excel

    Select the reviewed companies and dates. Include only displayed administrative call classification fields needed for the check. Choose Excel, not Excel with transcriptions. Retain the filter cover sheet and raw workbook.

    Expected output
    Native Excel log with actual selected columns and filter cover sheet.
    Next step
    Inspect native headers locally; separately capture Lead Qualification/Tags from the caller timeline if not present in the export.
    Check before continuing
    Do not rename Answered into a staff disposition or a qualified lead into a retained client. Date-based communication retention is capped at 25 months in current docs.
    Step documentation 1 ↗Step documentation 2 ↗

  2. Get the actual Lawmatics rows

    Lawmatics · Reports > Custom Reports > existing matter report > eye/view icon > Export

    Use an existing authorized report, or have its owner prepare a targeted report with Status and the actual Sub-status used for loss reasons, plus a safe record locator. Record Lost matters in the selected scope, including which date field sets the range. Export the viewed report to CSV; large exports may arrive by email. Preserve headers and file unchanged. A report creation/save is a separate account write, not performed here. If no suitable report exists, use the documented Settings > Export > Export Matters route only in restricted storage, then minimize locally.

    Expected output
    Native matter/contact-field rows; no promise of task history, audit history, destination IDs or custom fields that the firm never recorded.
    Next step
    Open in restricted Excel; compare rows to matter records before preparing aliases.
    Check before continuing
    A matter report may contain contact and matter fields. A contacts-only export omits matter fields. Date-created and date-converted scopes differ; exported grouping is not preserved.
    Step documentation 1 ↗Step documentation 2 ↗Step documentation 3 ↗Step documentation 4 ↗

  3. Make the checked, minimized handoff

    Excel / source-record reviewer · Restricted original workbook > separate analysis workbook > Scope worksheet

    Create Calls from observed call metadata and Leads from the Lawmatics export. Use the firm’s approved outcome vocabulary. If CallRail has no recorded disposition field/tag or the integration lacks a cross-reference, check calls separately rather than invent a join. 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,answer_state,staff_outcome_present,outcome_source,source_ref); Leads(lead_alias,status,loss_reason_present,source_ref); Scope(outcome_rules,coverage)
    Next step
    Format each approved range as a named table. Carry source-row references and coverage into the analysis workbook.
    Check before continuing
    Every field has an observed source or an explicit missing reason; staff assignments are marked editorial, not native.
    Step documentation 1 ↗Step documentation 2 ↗Step documentation 3 ↗

  4. Ask AI to inspect the checked inputs

    Excel Copilot, optional · Analysis workbook > Copilot icon at lower right > Chat only

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

    Expected output
    Two internal exception queues and missing-field list.
    Next step
    Copy checked results into a new Review sheet, retaining source references and unresolved blockers.
    Check before continuing
    A no-answer event is not a loss reason; staff decides factual disposition.
    Step documentation 1 ↗

  5. Human review and final action

    Final human review

    Responsible firm reviewer · Internal Review worksheet / review document

    Staff checks cited calls/matters and supplies only outcomes they know. Keep unknown reasons unknown. Save the reviewed exception list.

    Expected output
    Reviewed completeness list.
    Next step
    If separately approved, a human edits the original classification field/sub-status.
    Check before continuing
    No recordings, transcripts, caller identities or client narratives enter downstream AI.
    Step documentation 1 ↗Step documentation 2 ↗

What you’ll get

outcome-review.csv: record_id, missing_or_conflicting_code, supported_suggestion, source_note_ref, owner, review_status

Inputs and a sample test Synthetic example · not a measured result

Input files

  • calls.csv: call_id, lead_alias, disposition_code, redacted_staff_note, owner_alias
  • closed-leads.csv: lead_alias, supplied_status, loss_reason_code; code-dictionary.csv: code, definition, allowed_stage

Synthetic example

C1: answered call with blank disposition
L2: closed lead with missing reason
C3: unclear note with no explicit outcome

Expected output

C1: missing code
L2: ask owner for reason
C3: unresolved, no invented code

Test a failure

No automatic case qualification or decline. Do not convert vague notes into legal determinations; preserve original notes and approval history.

Try with the sample files

Follow the tool steps above and use the inputs named in each step. Where provided, native-* files are blank scaffolds and NATIVE-INPUT-MAPPING explains their fields. Original examples and the optional full review prompt use a separate prepared-input schema. Keep them separate unless the mapping explicitly connects them. Downloading a kit does not connect accounts or prove the workflow works.

Download inputs and checklist 17 files

Instructions, blank templates and separate synthetic examples; these files do not install an automation. Blank templates still need verified source data.

Optional full review prompt for prepared inputs

Prepared-input review prompt with Your firm-approved AI assistant · prepared files

Proposed / not tested · editorial prompt. This prompt uses the original prepared-input schema shown in the sample test. Step prompts may use different tables. Follow NATIVE-INPUT-MAPPING where supplied; do not mix the original examples with native-step inputs without mapping and checking every field.

Read original method Read pain evidence

Published by Law Firm Agents. These are source-linked editorial adaptations; no end-to-end execution is claimed. Read the plain-text version.