Law Firm Agents
CRM & Follow-upProposed workflow

Find leads without an owner or next step

Flag unassigned leads and overdue tasks using the firm’s written response rules.

Tools for the documented steps

These tools support separate parts of the method. The prompt does not connect them or verify a native integration.

Practice relevance

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

The problem

Flag unassigned leads and overdue tasks using the firm’s written response rules.

Why it matters: An open lead can be overlooked when nobody owns its next step. An exception list makes missing ownership and overdue administrative tasks visible without deciding whether the firm should accept the matter.

Sources & evidence

Proposed / not tested. The public discussion supports the problem; the method source supports only the documented features. No outcome from this adapted recipe has been verified.

What’s been verified

The linked sources support the complaint and documented method components. We have not run this recipe or verified its results. The example below is synthetic, not a customer result.

What to measure: During the pilot, count findings confirmed by the reviewer, false alarms, and missing-input cases. Do not infer time or money saved.

Source checked: October 15, 2026. Pain reports are self-reported and identities are unverified. Method documentation supports components, not a tested end-to-end workflow. This CRM recipe shares its firm discussion with other CRM tasks; it is not another independent firm report. We wrote these prompts. The adapted workflow hasn’t been tested.

Suggested approach

Start when: Each workday or new intake

  1. check owner, next-task date, completion and firm-defined response interval
  2. Keep row or page references and mark missing or ambiguous evidence. Do not apply the suggested changes.
  3. The responsible staff member checks the draft against the source records and approves any separate 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: Human resolves emergency/deadline indicators and prioritization. An elapsed interval never authorizes closing a potential matter or sending a non-engagement letter.

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
  • The next-action field is firm-maintained, not a guaranteed native field. No bulk task export was verified.
Check access and setup
  • The live account, entitlement, exact headers, records and field coverage have not been observed.

  1. Ask the in-app assistant for the source report

    Lawmatics Merlin Copilot, optional · Left navigation > Merlin > Copilot

    With an already approved seat and firm-wide reporting access, paste the prompt. Open the returned report/export or inspect its preview; if unavailable or incomplete, use the native report route below. Do not accept mutation previews, routines or feature-request sending.

    Expected output
    A report/one-time export or explicit unsupported/missing-field result; exact custom query coverage is not promised.
    Next step
    Check actual fields and records, then use the native CSV path where a report is returned. Prose alone does not certify completeness.
    Check before continuing
    Existing firm-approved AI entitlement and data handling approval are prerequisites. Lawmatics Merlin reporting can operate at firm scope; do not use it across ethical walls or assume matter-level permissions protect aggregate/search output. The detailed Copilot article and September 2026 release notes describe availability; the suite overview still contains a stale Coming Soon heading. Verify actual account access, with no purchase or permission changes.
    Step documentation 1 ↗Step documentation 2 ↗Step documentation 3 ↗

  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, Stage, Owned by, Created At and the exact firm-maintained next-action field if it exists. Record the agreed review period and matter 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. Check tasks without inventing a task export

    Lawmatics · Matters > selected matter > Tasks; or main Tasks dashboard

    For each nominated row, inspect actual tasks and status/due-date/assignee filters. Open a task for its activity history if needed. Manually record the next open task and due date with a record pointer; no native bulk task CSV is claimed.

    Expected output
    A bounded staff-checked task capture with coverage per matter.
    Next step
    Pass only task existence, assigned-role alias and due date to the analysis workbook.
    Check before continuing
    A blank next-action field does not prove there is no task; incomplete access or omitted tasks means unknown.
    Step documentation 1 ↗Step documentation 2 ↗

  4. Make the checked, minimized handoff

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

    Create Leads from the export and TasksChecked from explicit per-matter task inspection. Staff assign lead_alias and source_row_ref. Define active statuses and overdue rules in Scope. 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
    Leads(lead_alias,status,stage,owner_present,next_action_present,source_row_ref); TasksChecked(lead_alias,open_task_present,due_at,coverage,source_ref)
    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 ↗

  5. 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
    Source-linked owner/next-step exceptions.
    Next step
    Copy checked results into a new Review sheet, retaining source references and unresolved blockers.
    Check before continuing
    Inspect each flagged matter; report excluded/unknown rows and the denominator.
    Step documentation 1 ↗

  6. Human review and final action

    Final human review

    Responsible firm reviewer · Internal Review worksheet / review document

    Intake manager verifies each exception in the matter and decides owner/next action. Save the reviewed queue; any task creation is a separately authorized human action.

    Expected output
    Approved internal follow-up queue or unresolved coverage list.
    Next step
    Human returns to the cited matter/Tasks record if corrections are approved.
    Check before continuing
    No autonomous lead ranking, client communication or legal judgment.
    Step documentation 1 ↗

What you’ll get

lead-exceptions.csv: lead_alias, rule_id, exception, observed_timestamps, current_owner, proposed_next_step, reviewer

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

Input files

  • leads.csv: lead_alias, owner_alias, status, opted_out, next_action_id, next_action_due, last_activity_at
  • tasks.csv: task_id, lead_alias, owner_alias, status, due_datetime, completed_at
  • response-rules.csv: rule_id, stage, allowed_working_hours, response_interval, escalation_owner; include timezone and staff roster

Synthetic example

L1: open, no owner, no next action
L2: open, assigned, task overdue during working hours
L3: completed, old task still present

Expected output

L1: missing owner and next action
L2: overdue task for manager review
L3: excluded from the open-lead queue

Test a failure

Add an opted-out lead and a weekend interval. Do not draft contact for the opted-out lead or count non-working hours as overdue unless policy says so.

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 14 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.