START WITH THE PRODUCT STEPS
Read START-HERE.txt first. It states the actual source acquisition, access/privacy limits, manual field mapping and exact next prompt. The original file templates and synthetic examples below are supporting review aids. Some paths need separately supplied documents or source text; a blank worksheet is not a native export or completed integration.

Request Google reviews after matter closure
Starter kit G16

Documentation-checked component path; proposed workflow, not tested

Read START-HERE.txt for the full product steps and approval gates. This kit supports planning and controlled synthetic validation. It does not configure, activate or run either workflow.

CURRENT FILES
- closure-register-template.csv and request-ledger-template.csv are blank editorial inputs for optional synthetic setup review
- policy-template.txt records firm decisions, approval/recheck rules, true opt-out and verified location link
- neutral-email-template.txt is a draft for firm approval
- synthetic-tests.txt lists expected cases, not performed test results
- starter-prompt.txt is the optional synthetic-only planning prompt
- NATIVE-INPUT-MAPPING.txt explains the exact inputs and unresolved native mapping

LEGACY FILES
The legacy/ folder preserves the old prepared-input route and invented fixtures. Keep it separate. Its schema and expected outputs do not test the upgraded automation.

BEFORE REAL USE
- 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.

COPYABLE OFFLINE PROMPT
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.

EXPECTED SYNTHETIC FIXTURE RESULT
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.

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.

Run the current acceptance plan only after approval, using synthetic matters and a firm-controlled inbox. No account test was performed while preparing this kit.
