A review request needs a process, not a script

A client’s matter closes. The team sends a final invoice, archives the file, and moves on to the next deadline. Someone may remember to ask for a review, but the timing and wording depend on who handled the file and how busy the office is.

That creates two problems. You miss chances to invite clients to share feedback, and an inconsistent request can create professional-conduct risks. A public review request should be neutral, voluntary, and separate from legal advice, billing pressure, or the outcome of a matter.

Automating the reminder can help, but the goal isn’t to automate judgment. It’s to send an approved request at an appropriate time, to an appropriate client, through an approved channel, while keeping confidential matter details out of the message.

The rules vary by jurisdiction and can depend on how a firm’s communications are classified. Have counsel or your ethics adviser review the workflow against the rules that apply to your practice. The process below gives you a practical starting point, not a substitute for that review.

Where manual review requests break down

In most firms, the information needed to send a request already exists in practice-management software, email, or a closing checklist. The failure is often that no one owns the handoff between “matter complete” and “request sent.”

A paralegal may close the file but not know whether the attorney considers the relationship suitable for a review request. A billing team member may see a final payment but not know that a fee dispute is still active. A partner may want to ask a satisfied client, but can’t reliably identify which clients should receive the same request.

Manual processes also create uneven treatment. One practice group may ask every eligible client, while another asks only clients who appear pleased with the outcome. That kind of selective process can raise concerns about whether public reviews are being solicited fairly, especially if a firm is also asking clients to rate their experience privately first.

There’s a real cost to that inconsistency. Operational gaps can pull staff and attorneys away from billable work. Review administration is one small, visible example of the matter admin that can pull staff and attorneys away from billable work. Firms may rely on reminders in email, task lists, and individual memory rather than a defined workflow.

The answer isn’t to ask every client at every stage. It’s to establish a consistent eligibility policy, make the request easy to decline, and give a person a clear way to pause or review exceptions.

The safeguards to set before automation

Start by writing down the firm’s rules for eligibility. Avoid letting an automated workflow infer that a client is happy, that an outcome was favorable, or that a particular matter is suitable based on the tone of an email or a case result.

Use objective triggers that your firm has approved. A trigger might be a matter’s formal closure, completion of a defined service, or another milestone that the responsible attorney has confirmed. The trigger should not be “invoice paid” if payment status could cause the request to feel like pressure or if a dispute may still be open.

Then define exceptions. Depending on the firm’s policies and applicable rules, you may want to hold a request for matters involving ongoing disputes, complaints, sensitive personal circumstances, a client who has opted out, or a relationship where the responsible attorney has asked for a pause. A hold should be a recorded status with an owner and a reason, not an informal note buried in a file.

A sound workflow usually includes these safeguards:

Consent and contact preferences: Use contact details and communication channels the client has agreed to use. Respect opt-outs and any channel-specific requirements.
Confidentiality: Keep the message generic. Don’t include the client’s name alongside a practice area, case type, outcome, legal issue, or other matter detail. Review how vendors handle contact data and set access and retention controls.
Neutral language: Invite honest feedback without suggesting a positive rating, asking the client to change an existing review, or linking a request to a discount, gift, or other benefit.
No pressure: Make clear that participation is voluntary and won’t affect the client’s matter, service, or relationship with the firm.
A human exception path: Let staff pause a request before it goes out, and give the responsible attorney a way to stop or correct a workflow.
A record of the process: Log the trigger, template version, recipient, send date, opt-out status, and any manual hold. Keep the record in line with your retention policy.

Remember that a private request can lead to a public post. Once a client publishes a review, the firm may not be able to control what they disclose. Staff should not confirm or reveal that someone was a client when responding publicly, and should not disclose facts about a representation to rebut criticism without appropriate authority. Have counsel approve a response protocol as well as the request itself.

What an end-to-end workflow looks like

A practical setup begins with the matter record, not an email campaign list. When a matter reaches a firm-approved milestone, the system checks a small set of fields: matter status, responsible attorney, client communication preference, review-request eligibility, opt-out status, and any active hold.

If a required field is missing, the workflow creates a task for staff rather than guessing. If the client is opted out or the matter is on hold, it records that result and sends nothing. If the matter is eligible, it prepares the approved neutral message using only the client’s permitted contact details.

Before the first launch, the firm can require a human to approve every request. After the process is tested, the firm might allow routine, low-risk requests to send automatically while exceptions still require review. Keep that distinction explicit. “Automation” shouldn’t mean that an uncertain case is silently treated as eligible.

The message itself should be short. For example, the firm might thank the client for working with the team and invite them to share honest feedback through a link. It should state that the request is voluntary. It shouldn’t ask for a five-star review, mention a case result, or suggest that a client contact the firm privately before posting publicly.

Set a reasonable sending window after the milestone, based on the firm’s policies and client expectations. If the client doesn’t respond, a single follow-up may be appropriate if counsel approves it. Avoid a sequence that makes a client feel pursued. A stop rule should prevent further messages after an opt-out, complaint, reply asking for help, or any other signal that requires a person to step in.

Finally, track operational results without turning them into pressure on clients. Useful measures include the share of eligible matters that received a request, the number paused for review, opt-outs, delivery failures, and staff time spent managing the workflow. Don’t set staff targets that reward them for positive reviews or encourage them to select clients based on perceived satisfaction.

If you want to map this against your own systems and matter handoffs, Book a 60-min Omni Audit. We’ll use the hour to identify where the workflow should start, where a person needs to approve it, and what should never be sent automatically.

Where an agent fits, and where it doesn’t

An agent can monitor approved matter-status changes, check the eligibility fields, and prepare a task or message for the right person. It can also maintain a record of what happened, flag missing consent or contact preferences, and stop when it encounters an exception.

It shouldn’t decide that a client is satisfied by reading private correspondence. It shouldn’t infer that a matter is safe to mention publicly. And it shouldn’t send a message that hasn’t been approved for the firm’s jurisdiction and practice.

For a law firm, the useful design is often a narrow workflow connected to existing operations. An agent in a separate process can help organize incoming information and route it to the right person. That’s a separate process from requesting reviews, but it illustrates the same principle: use automation to organize information and route decisions, while defining where a person has to take responsibility. A voice agent used for calls or consultation bookings should not be repurposed to solicit reviews without a separately approved script and process.

The workflow also needs an owner. Assign someone to review template changes, monitor holds and opt-outs, and confirm that the automation still matches firm policy when systems or rules change. If a client responds with a question, complaint, or sensitive information, route the reply to a person rather than generating a canned answer.

For adjacent parts of the client experience, you can compare this process with automating client communication in law firms and automating follow-up emails to clients. Those workflows need their own approval rules, but they often depend on the same accurate matter status and communication preferences.

Build the request around a defined milestone

Before connecting software, write down the workflow in plain language:

Which matter status or milestone can start a request?
Which clients or matters are excluded, and who can set a hold?
What consent and contact-preference fields must be present?
Which approved template and review link can be used?
Who receives a task if the system finds missing information?
What stops a request or follow-up from going out?
Where are the activity record and opt-out stored?
Who reviews the process and template over time?

If the answers differ by jurisdiction, practice group, or client type, document those differences. A single generic workflow may not fit every matter. The first version can be narrow, such as one practice group and one closure milestone, then expand only after the firm has reviewed its exceptions and logs.

This is also a good point to check whether a request is appropriate for the firm’s chosen public platform and how that platform handles reviews. Keep platform rules and professional-conduct rules in view. A platform allowing a certain feature doesn’t mean that the firm’s use of it meets its own ethical obligations.

Start with the economics, then measure the workflow

The return from this process is not a guaranteed number of new clients. Reviews can influence how prospective clients assess a firm, but results vary by practice area, location, competition, and the client’s own experience. Don’t build a business case around a promised ranking or a target review count.

Instead, measure the work you can control. How many eligible matters reach the approved milestone? How many requests need manual correction? How often do staff find a missing preference, an active hold, or a data-quality problem? How much time does the current process take each month? Those answers show whether the workflow is reliable and whether the firm is spending less time chasing administrative tasks.

For a firm, recovering even a portion of recurring admin time can matter. But don’t count the time as recovered billable revenue unless attorneys actually use it for billable work and the client can appropriately be billed. Review-request automation is a small operational improvement, not a cure for broader billing or capacity problems.

If client intake and early matter handling also consume partner or staff time, the AI Client Intake Checklist for Law Firms gives your team a practical worksheet for identifying handoffs and missing steps. Download the checklist to work through your current intake process. It’s a separate part of the client journey, but it can reveal where contact preferences, ownership, and status tracking need to be clearer.

What to bring to an Omni Audit

An Omni Audit can map the current workflow and identify useful next steps:

A clear view of the matter milestones, people, systems, and handoffs involved.
A shortlist of automation opportunities, including the checks that should stay with a person.
A practical first-step plan with the data, approvals, and safeguards needed to test the workflow.

Bring your current request template, the fields your team uses to close a matter, and any existing opt-out or review policies. If those documents don’t exist yet, that’s useful to know. We can identify what needs to be decided before a workflow is built.

You can see Omni for law firms and review how the audit fits a legal practice. If the process is ready for a closer look, Book a 60-min Omni Audit. We’ll leave you with a defined next step, not a generic automation pitch.

A well-designed request process makes it easier for the firm to ask consistently without turning a client’s matter into a marketing trigger. Start with the rule, the milestone, and the exceptions. Then automate the parts that are predictable, keep a person responsible for judgment, and see the AI audit for law firms when you’re ready to map it across your current systems.

Automate Law Firm Review Requests Within Bar Rules