# Request Google reviews after matter closure

Canonical page: https://agents.paretoid.com/workflows/prepare-neutral-review-invitations/

Category: Local SEO

Practice relevance: cross-practice. A general operational method. Review the stated tool and jurisdiction limits before use.

Jurisdiction/provider scope: 

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

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

Verification: 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.

## 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 and evidence

- pain: [Pain evidence: Public discussion](https://www.reddit.com/r/LawFirm/comments/10lvcbt/google_reviews/)
  original post 2023-01-26. Attorney reports only one review per 10–20 clients and asks how other firms collect reviews. Older self-reported pain.

- method: [Google: local ranking factors](https://support.google.com/business/answer/7091?hl=en)
  Review quantity and ratings can help local ranking; no independent review-velocity or recency claim is established here.

- method: [Google: prohibited and restricted content](https://support.google.com/contributionpolicy/answer/7400114?hl=en)
  No incentives, selective positive-review solicitation or discouraging negative reviews.

- method: [Google: create a review link or QR code](https://support.google.com/business/answer/16816815?hl=en)
  Native Business Profile steps for obtaining a genuine review link.

- method: [Lawmatics: closure-based automation entry](https://help.lawmatics.com/en/articles/10699913-drip-campaigns)
  Documents closure through sub-status or custom-field matching.

- method: [Lawmatics: automation entry conditions](https://help.lawmatics.com/en/articles/10699907-automation-entry-conditions-triggers)
  Documents Match on Fields and Task Activity triggers.

- method: [Lawmatics: creating internal tasks](https://help.lawmatics.com/en/articles/10699821-creating-tasks-for-users)
  Documents Add Task and assigned staff ownership.

- method: [Lawmatics: task tags](https://help.lawmatics.com/en/articles/10699842-task-tags)
  Documents triggering a workflow on completion of a specifically tagged task.

- method: [Lawmatics: sending emails](https://help.lawmatics.com/en/articles/10699866-sending-emails-via-lawmatics)
  Documents template-based Send Email, recipient/sender selection and timeline evidence.

- method: [Lawmatics: exit conditions](https://help.lawmatics.com/en/articles/10699927-exit-conditions)
  Conditions are checked before action items; a target normally enters a given automation once, but manual reruns are possible.

- method: [Lawmatics: delivery windows](https://help.lawmatics.com/en/articles/10699933-using-delivery-windows-in-automation)
  Supports configured sending windows for automated emails.

- method: [Lawmatics: pipeline overview](https://help.lawmatics.com/en/articles/10699804-pipeline-overview)
  Imports into stages can trigger stage-based workflows; historical import controls are needed.

- method: [Lawmatics: automation actions](https://help.lawmatics.com/en/articles/10699906-automation-actions)
  Documents conditional branches and field updates; mappings require live configuration checks.

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.

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

## What you need

- 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

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

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

Tool: Google Business Profile

Location: 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.

Execution status: Official public documentation checked 2026-10-15. No login, installation, source-data access, client message or live workflow run.

Step documentation: https://support.google.com/business/answer/16816815?hl=en

### 2. Define neutral closure and safeguards

Tool: Lawmatics

Location: 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.

Execution status: Official public documentation checked 2026-10-15. No login, installation, source-data access, client message or live workflow run.

Step documentation: https://help.lawmatics.com/en/articles/10699913-drip-campaigns

### 3. Build the closure-to-task workflow

Tool: Lawmatics

Location: 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.

Execution status: Official public documentation checked 2026-10-15. No login, installation, source-data access, client message or live workflow run.

Step documentation: https://help.lawmatics.com/en/articles/10699821-creating-tasks-for-users https://help.lawmatics.com/en/articles/10699907-automation-entry-conditions-triggers https://help.lawmatics.com/en/articles/10699804-pipeline-overview

### 4. Review the contact and approve

Tool: Lawmatics

Location: 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.

Execution status: Official public documentation checked 2026-10-15. No login, installation, source-data access, client message or live workflow run.

Step documentation: https://help.lawmatics.com/en/articles/10699842-task-tags

### 5. Configure approval-to-email separately

Tool: Lawmatics

Location: 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.

Execution status: Official public documentation checked 2026-10-15. No login, installation, source-data access, client message or live workflow run.

Step documentation: https://help.lawmatics.com/en/articles/10699866-sending-emails-via-lawmatics https://help.lawmatics.com/en/articles/10699842-task-tags https://help.lawmatics.com/en/articles/10699906-automation-actions https://help.lawmatics.com/en/articles/10699927-exit-conditions https://help.lawmatics.com/en/articles/10699933-using-delivery-windows-in-automation

### 6. Test, activate only with approval, and reconcile

Tool: Lawmatics

Location: 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.

Execution status: Official public documentation checked 2026-10-15. No login, installation, source-data access, client message or live workflow run.

Step documentation: https://help.lawmatics.com/en/articles/10699927-exit-conditions

## What you will 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.

## Human review and limits

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.

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.

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.

## Original prepared-input schema

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 input:

```text
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 synthetic output:

```text
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.
```

Failure check: 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.

## Starter files

Native blank scaffolds and original synthetic examples may use different schemas. Follow NATIVE-INPUT-MAPPING where supplied. These files do not connect accounts or install automation.

- [Download starter kit](https://agents.paretoid.com/assets/starter-kits/g16-starter-kit.zip) — All inputs, synthetic examples and review notes in one ZIP. No automation is installed.

- [Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/g16/START-HERE.txt) — Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits

- [Blank input: closure-register.csv](https://agents.paretoid.com/assets/starter-kits/g16/closure-register-template.csv) — Header-only editorial setup-review table; use a synthetic packet for the optional AI prompt; not a Lawmatics export

- [Blank input: request-ledger.csv](https://agents.paretoid.com/assets/starter-kits/g16/request-ledger-template.csv) — Header-only editorial setup-review table; use a synthetic packet for the optional AI prompt; not a Lawmatics export

- [Uniform closure and invitation policy](https://agents.paretoid.com/assets/starter-kits/g16/policy-template.txt) — Blank firm-approved policy choices; example cooldown is not a legal or Google rule

- [Neutral invitation draft for firm approval](https://agents.paretoid.com/assets/starter-kits/g16/neutral-email-template.txt) — Human approval draft with genuine-link and working-opt-out placeholders; no send

- [Synthetic acceptance test plan](https://agents.paretoid.com/assets/starter-kits/g16/synthetic-tests.txt) — Expected cases to run with synthetic matters and a firm-controlled inbox after approval; not executed test results

- [Optional synthetic setup-review prompt](https://agents.paretoid.com/assets/starter-kits/g16/starter-prompt.txt) — Exact upgraded recipe prompt; no account changes, activation or sending

- [Current input mapping and legacy boundaries](https://agents.paretoid.com/assets/starter-kits/g16/NATIVE-INPUT-MAPPING.txt) — Exact closure/ledger contract and clear do-not-mix legacy boundary

- [Setup and current versus legacy files](https://agents.paretoid.com/assets/starter-kits/g16/README.txt) — Practical current kit instructions and synthetic-only validation limits

- [Legacy original route: Start here: get the sources and prepare the review](https://agents.paretoid.com/assets/starter-kits/g16/legacy/START-HERE.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Documentation-checked acquisition, explicit manual mapping, exact prompts and human review limits

- [Legacy original route: Input template: services.csv](https://agents.paretoid.com/assets/starter-kits/g16/legacy/services.csv) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Header-only input template; preserve exact names and order

- [Legacy original route: Synthetic input: services.csv](https://agents.paretoid.com/assets/starter-kits/g16/legacy/services-example.csv) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Fabricated sample rows for an offline manual trial

- [Legacy original route: Input template: request-log.csv](https://agents.paretoid.com/assets/starter-kits/g16/legacy/request-log.csv) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Header-only input template; preserve exact names and order

- [Legacy original route: Synthetic input: request-log.csv](https://agents.paretoid.com/assets/starter-kits/g16/legacy/request-log-example.csv) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Fabricated sample rows for an offline manual trial

- [Legacy original route: Output template: invitation-queue.csv](https://agents.paretoid.com/assets/starter-kits/g16/legacy/invitation-queue.csv) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Header-only output template; preserve exact names and order

- [Legacy original route: Expected output: invitation-queue.csv](https://agents.paretoid.com/assets/starter-kits/g16/legacy/invitation-queue-example.csv) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Hand-authored synthetic expected result; not an executed workflow result

- [Legacy original route: Policy/input template: uniform-policy.txt](https://agents.paretoid.com/assets/starter-kits/g16/legacy/uniform-policy.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Required source/policy preparation scaffold; not populated with firm instructions

- [Legacy original route: Synthetic policy/input: uniform-policy.txt](https://agents.paretoid.com/assets/starter-kits/g16/legacy/uniform-policy-example.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Fixture-only context; not an approved production policy

- [Legacy original route: Draft scaffold: invitation-draft.txt](https://agents.paretoid.com/assets/starter-kits/g16/legacy/invitation-draft.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Blank output scaffold; no message, form or appeal is sent

- [Legacy original route: Synthetic expected draft: invitation-draft.txt](https://agents.paretoid.com/assets/starter-kits/g16/legacy/invitation-draft-example.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Hand-authored draft or blocked-output example for fixture review

- [Legacy original route: Synthetic fixture expectations](https://agents.paretoid.com/assets/starter-kits/g16/legacy/fixture-expectations.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Acceptance targets and failure checks; no claim of workflow execution

- [Legacy original route: Review prompt](https://agents.paretoid.com/assets/starter-kits/g16/legacy/starter-prompt.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Copyable offline review prompt; no executable automation

- [Legacy original route: Setup and prerequisites](https://agents.paretoid.com/assets/starter-kits/g16/legacy/README.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Recipe-specific setup, evidence sources and usage boundaries

- [Legacy original route: Native input scaffold: Eligibility](https://agents.paretoid.com/assets/starter-kits/g16/legacy/native-eligibility-template.csv) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Empty editorial table for Eligibility; populate from verified source evidence after reviewed mapping; not a native export

- [Legacy original route: Native input scaffold: ApprovedPolicy](https://agents.paretoid.com/assets/starter-kits/g16/legacy/native-approvedpolicy-template.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Approved text input for ApprovedPolicy; complete from verified evidence and include in the AI-visible packet

- [Legacy original route: Native input scaffold: VerifiedLink](https://agents.paretoid.com/assets/starter-kits/g16/legacy/native-verifiedlink-template.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Approved text input for VerifiedLink; complete from verified evidence and include in the AI-visible packet

- [Legacy original route: Native input scaffold: Scope](https://agents.paretoid.com/assets/starter-kits/g16/legacy/native-scope-template.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Approved text input for Scope; complete from verified evidence and include in the AI-visible packet

- [Legacy original route: Native input mapping and scope guide](https://agents.paretoid.com/assets/starter-kits/g16/legacy/NATIVE-INPUT-MAPPING.txt) — Legacy schema/example for the earlier prepared-input route only. Do not mix with the upgraded closure-register/request-ledger workflow. Old-file-to-native-input compatibility map, acquisition requirements, privacy and blocking gates

## Optional original prepared-input prompt

Destination: Optional firm-approved AI assistant · synthetic setup only

This original prompt uses its own prepared-input schema. Do not mix it with native-step tables without the supplied mapping.

```text
Using only the supplied synthetic closure register, request ledger and approved policy, produce an implementation checklist for two INACTIVE Lawmatics workflows: neutral closure to staff task, then approved tagged-task completion to email. Separate documented native capabilities from proposed custom fields and manual checks. Never use outcome, satisfaction, rating, complaint history or fee value for selection. Flag opt-outs, missing permission, privacy holds, repeated contacts, cooldown conflicts, reopened matters, historical enrollments and uncertain sends. Do not infer approval from task closure unless it is the dedicated approved task with the documented reviewer decision. Do not claim cross-matter atomic dedup is native. Return mapping gaps and a test matrix; if reliable pre-send safety checks are missing, choose staff task plus manual send. Do not connect accounts, activate workflows, send messages, write customer reviews or publish replies. 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.
```

Proposed / not tested · editorial prompt

Published by Law Firm Agents. Proposed adaptation; not tested. Not legal advice.