Law Firm Agents
Local SEOProposed workflow

Request Google reviews after matter closure

Use Lawmatics to queue a neutral Google review invitation at matter closure, check privacy and contact rules, then send an approved email.

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

Review requests get forgotten at matter closure; outcome-based selection, duplicate messages and sensitive matters make a simple send-on-close rule risky.

Why it matters: Review requests are easy to miss when a matter closes. A consistent queue helps staff catch missed invitations and duplicate contact, while a current human approval protects client confidentiality and contact preferences.

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: Eligible closures reviewed; requests actually sent; duplicate/opt-out prevention; privacy holds resolved; aggregate new reviews and Business Profile enquiries over time. Never equate clicks, email opens or send events with a posted review or causal ranking improvement.

Source checked: October 15, 2026. Pain accounts are self-reported. Documentation supports components; this adapted recipe and prompt have not been tested. Google says review count and positive ratings can help local ranking alongside other factors. Its cited guidance does not establish review frequency or recency as an independent ranking factor; no ranking gain is promised. We wrote these prompts. The adapted workflow hasn’t been tested.

Suggested approach

Start when: A matter reaches the firm’s uniformly defined closure milestone, regardless of result or client sentiment. Closure creates only an internal task; email requires a separate current documented approval.

  1. A neutral matter-closure field triggers an internal approval task in Lawmatics.
  2. Staff check privacy, channel permission, identity, opt-outs, prior requests and the approved cooldown across all matters for that contact.
  3. A dedicated approved-task completion event plus explicit current approval=true and a recorded reviewer decision permits the separate send workflow; current safeguards are rechecked immediately before sending.
  4. Record actual send evidence and reconcile failures without blind retries; public responses remain a separate, individually reviewed workflow.

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: The firm approves the uniform policy, privacy rules, channel and exact template before activation. Staff approve each recipient after checking consent, opt-out, identity, privacy and duplicates. No sentiment, star rating, complaint, fee value or favorable-result filtering. No public response is posted. The send workflow requires BOTH a dedicated approved-task completion event AND a current approval=true field backed by a recorded reviewer decision, decision time and policy version. Missing, stale, conflicting or revoked approval stops the send. Held or declined tasks must have the trigger tag removed before they are closed; approval remains false.

What you need

Optional firm-approved AI assistant · synthetic setup only

  • Firm-approved advertising/confidentiality/contact policy for its jurisdiction and practice; responsible reviewer and explicit email/template activation approval.
  • Existing authorized Lawmatics and Google Business Profile access; actual subscription, fields and send controls must be verified. No purchase, login, connection or new access is included.
  • A uniform matter-closure milestone, documented privacy criteria, contact-level request history, opt-out data, cooldown policy and genuine firm/location review URL.
  • Synthetic inputs first. Keep client identity and the contact ledger in firm-approved systems. AI is optional and does not need client records.

How to use

Documentation-checked component path; proposed workflow, not tested

Before you start
  • Proposed field names and ledger schemas are editorial, not native export headers.
  • Lawmatics documents a once-per-target automation limit, but separate matters and manual reruns require additional contact-level deduplication. Atomic cross-matter locking is not verified.
  • Never copy a positive/neutral/negative review-routing template: the same genuine review opportunity must not depend on sentiment or case outcome.
Check access and setup
  • Live entitlements, available custom-field conditions, exact recipient mapping, unsubscribe behavior, cross-matter dedup and delivery-window rechecks require synthetic testing.
  • If timely pre-send checks or reliable reservation cannot be implemented, automate the task only and keep the email send manual.
  • Verify the live account can require a current approval=true field and recorded reviewer decision at dispatch; otherwise use the manual-send fallback.

  1. Copy the real review link

    Google Business Profile · Business Profile > Read Reviews > Get more reviews > Copy

    Open the existing authorized profile for the intended firm location. Copy the native review-request URL and verify the destination. Save it in the approved template; do not generate a guessed URL. QR download is optional on desktop.

    Expected output
    Verified firm/location link and neutral template.
    Next step
    Human setup and review required; keep workflows inactive until separately authorized.
    Check before continuing
    Documentation checked; exact live field mapping, plan access and end-to-end behavior remain untested.
    Step documentation 1 ↗

  2. Define neutral closure and safeguards

    Lawmatics · Matter record and firm-approved custom fields / sub-status

    Use a closure milestone that covers completed services regardless of outcome. Staff maintain proposed fields for permission, opt-out, privacy hold, review-request state, approval (default false), reviewer decision, decision time and policy version; these are editorial fields, not guaranteed built-ins. Keep a contact-level request ledger across matters. Approve a consistent cooldown (example: 180 days, a firm choice, not a Google rule). Unknown eligibility stays on hold.

    Expected output
    Mapped fields, responsible reviewer and approved uniform policy.
    Next step
    Human setup and review required; keep workflows inactive until separately authorized.
    Check before continuing
    Documentation checked; exact live field mapping, plan access and end-to-end behavior remain untested.
    Step documentation 1 ↗

  3. Build the closure-to-task workflow

    Lawmatics · Automations > Workflows > Create New Automation > target Matter > Entry Conditions > Match on Fields; add Add Task

    Create an inactive workflow matching the approved closure field. Add an internal eligibility-review task, assigned to the responsible staff member, using a dedicated tag such as Review-invitation-approved. Label the task: complete only when approved; use a separate disposition for held or declined cases. Restrict enrollment to an approved launch cohort so historical imports do not trigger outreach. The send workflow requires BOTH a dedicated approved-task completion event AND a current approval=true field backed by a recorded reviewer decision, decision time and policy version. Missing, stale, conflicting or revoked approval stops the send. Held or declined tasks must have the trigger tag removed before they are closed; approval remains false.

    Expected output
    Inactive closure-to-task workflow; no client send action in this first workflow.
    Next step
    Human setup and review required; keep workflows inactive until separately authorized.
    Check before continuing
    Documentation checked; exact live field mapping, plan access and end-to-end behavior remain untested.
    Step documentation 1 ↗Step documentation 2 ↗Step documentation 3 ↗

  4. Review the contact and approve

    Lawmatics · Assigned task and contact/matter timeline; firm-controlled request ledger

    Before completing the approval task, verify contact identity and appropriate email permission, current opt-out, neutral privacy criteria and closure state. Check prior sends across every matter for the contact, active pending approvals and the cooldown. Reserve one request for the contact/location and close duplicate tasks without the approval tag. Sensitive matters remain on a lawyer hold until privacy clearance; dissatisfaction alone is never a hold reason. Log reviewer, decision time and policy version. The send workflow requires BOTH a dedicated approved-task completion event AND a current approval=true field backed by a recorded reviewer decision, decision time and policy version. Missing, stale, conflicting or revoked approval stops the send. Held or declined tasks must have the trigger tag removed before they are closed; approval remains false.

    Expected output
    Auditable approval or hold; one reserved request per contact/location.
    Next step
    Human setup and review required; keep workflows inactive until separately authorized.
    Check before continuing
    Documentation checked; exact live field mapping, plan access and end-to-end behavior remain untested.
    Step documentation 1 ↗

  5. Configure approval-to-email separately

    Lawmatics · Automations > Workflows > new Matter workflow > Entry Conditions > Task Activity > completed task with dedicated approval tag; Send Email

    Use task completion as the separate send trigger. Add current field conditions and exit rules for opt-out, privacy hold, reopened matter and already-sent state; unknowns stop. Choose the approved Marketing > Emails template, recipient and sender; configure a reasonable delivery window. The approval must still be valid at dispatch. Cross-matter atomic deduplication and cooldown are not established native features: retain manual dispatch if the firm cannot reliably recheck and reserve at contact level. No follow-up reminder by default. The send workflow requires BOTH a dedicated approved-task completion event AND a current approval=true field backed by a recorded reviewer decision, decision time and policy version. Missing, stale, conflicting or revoked approval stops the send. Held or declined tasks must have the trigger tag removed before they are closed; approval remains false.

    Expected output
    Inactive approval-to-send workflow, or a documented manual-send fallback.
    Next step
    Human setup and review required; keep workflows inactive until separately authorized.
    Check before continuing
    Verify the second workflow checks current approval=true and recorded reviewer decision in addition to its tagged-task event. If live fields cannot express these checks reliably, keep automated email inactive and use manual send after checking the recorded decision and current safeguards.
    Step documentation 1 ↗Step documentation 2 ↗Step documentation 3 ↗Step documentation 4 ↗Step documentation 5 ↗

  6. Test, activate only with approval, and reconcile

    Lawmatics · Synthetic test matter; automation status; recipient timeline

    First test with a synthetic matter and firm test inbox, never a real client selected as sample data. Verify enrollment, hold/exit logic and the genuine link. After separate firm activation approval, reconcile each send against timeline evidence; update the request ledger only from observed status. Never retry an uncertain send before checking the timeline. Reopened matters, imports and manual reruns must not bypass the contact ledger. Do not infer review publication or reviewer identity from clicks or names.

    Expected output
    Test evidence and per-request sent, failed, held or unknown status; no automated public reply.
    Next step
    Human setup and review required; keep workflows inactive until separately authorized.
    Check before continuing
    Documentation checked; exact live field mapping, plan access and end-to-end behavior remain untested.
    Step documentation 1 ↗

What you’ll get

An inactive two-workflow Lawmatics implementation plan, neutral email template, eligibility checklist and synthetic failure tests. No account is connected and no message is sent.

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

Input files

  • closure-register.csv: matter_alias, contact_alias, location_alias, closed_at, closure_verified, email_permission, opted_out, privacy_hold, reopened, reviewer, policy_version, approval, reviewer_decision, decision_at, approval_valid_until
  • request-ledger.csv: contact_alias, location_alias, request_id, state, requested_at, reserved_at, send_evidence_ref; policy.txt: launch cohort, timezone, cooldown_days, approved closure rule, privacy criteria, approved template, verified review URL

Synthetic example

Synthetic fixture: eligible closure; identical closure with negative sentiment; opt-out; privacy hold; two matters for same contact; recent request; reopened matter; historic import; unknown permission; ambiguous prior send.

Expected output

Eligible records receive identical review consideration regardless of outcome. Opt-outs are suppressed; privacy and unknowns held; duplicate, historic and recent requests blocked. No message is sent by this starter kit.

Test a failure

A negative-service-feedback fixture must remain eligible on the same facts. Block simultaneous duplicate matters, late opt-out, reopened matters, historical import and manual rerun. An uncertain prior send must stop retry pending timeline inspection. A completed tagged task with approval=false, no recorded decision, expired approval or revocation must never send. Closing held or declined tasks after removing their trigger tag must not start the send workflow.

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 29 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 Optional firm-approved AI assistant · synthetic setup only

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.