Law Firm Client Updates: What to Automate First

I'd start with three triggers: a matter changes stage, a matter goes quiet, or a client asks where things stand. Agree what each trigger should prepare, who checks the message and where the record goes. Much of the work can use approved wording without AI.

The NSW Office of the Legal Services Commissioner says complaints often arise from miscommunication or clients feeling their lawyer is unresponsive or unapproachable. My starting point is the gap between a change on the file and someone telling the client. For the wider priorities, see the Truespeak guide to choosing a law firm's first automations.

Which Client Updates Should a Law Firm Automate First?

These three workflows cover progress, silence and incoming questions. I'd introduce them separately so the firm can check the wording and workload each creates. The following is a proposed design.

1. Stage-change updates. Trigger when the recorded matter stage or workflow step changes. Prepare agreed wording explaining what happened, what comes next and whether the client needs to act. A solicitor approves each stage template and reads any matter-specific additions before sending. Save the message to the matter. Measure the delay between stage change and message, plus the share of relevant changes followed by an update. Start here because the recorded change gives staff a concrete reason to communicate.
2. Quiet-matter check-ins. Trigger when an open matter passes a contact threshold set by the firm for that matter type. Prepare the last recorded activity, who the matter is waiting on and a short draft. The responsible fee earner sends, edits or dismisses it. Record the message or reason for holding it. Count matters past the threshold each week. This catches files where nothing has moved far enough to trigger a stage update.
3. Drafted replies to status questions. Trigger when an email or portal message asks where the matter stands. Prepare recent file activity and a draft reply for a solicitor or assistant to review every time, escalating anything involving advice. Save the reply and file note. Measure status enquiries per fee earner and time to first reply. This gives the reviewer the relevant records beside the draft.

A quiet-matter draft should distinguish the last recorded event from something checked today. If the file only records that documents were requested, the draft must not claim the other side is still preparing them.

What Can LEAP, Smokeball and Actionstep Already Do?

Use native features first. I checked these capabilities on each vendor's published pages as at 6 November 2026. Ask your vendor to confirm your plan, configuration and Australian availability before scoping extra work.

A portal gives clients somewhere to read an update; the firm still needs a process that prepares the message. The Truespeak Australian legal practice management software guide covers the broader software decision.

For additional connections, Smokeball publishes a matterstage.updated event and says firms should request API access through their account manager. Actionstep publishes StepChanged and other matter events. Those are possible triggers to investigate, subject to access and workflow checks.

Which Client Updates Need a Solicitor to Read Them?

I'd allow routine administration to use solicitor-approved wording within agreed rules. Any AI draft still gets read before sending. An assistant can check a factual acknowledgement; a solicitor should check a message explaining what a development means or what the client should do.

Route costs changes, bad news, settlement discussions, complaints and uncertain facts to the solicitor. The reviewer needs the source records beside the draft. Check each fact in the draft against those records.

Make the approval step explicit: name the reviewer, hold the message until approval and record who approved the final wording. The Truespeak guide to human approval in automation explains that design.

What Do Australian Conduct Rules and AI Guidance Mean for Client Updates?

The Queensland Law Society's published version of the Australian Solicitors' Conduct Rules requires clear and timely advice under rule 7.1 and protects client confidentiality under rule 9.1, subject to exceptions. Rule 7.1 concerns advice; it does not prescribe a regular status-message schedule. Check the version applying in your state.

The joint AI statement from the Law Society of NSW, Legal Practice Board of WA and Victorian Legal Services Board + Commissioner says lawyers cannot safely enter confidential, sensitive or privileged client information into public AI chatbots or copilots. It calls for reviewing contractual terms, personally verifying outputs, supervising staff use and transparency with clients.

Before enabling drafting, assess the actual tool, its terms and how client information is handled. Set rules for staff use, review and client disclosure. Buying a commercial subscription does not settle those questions.

Costs need a separate decision. The Victorian regulator says a significant matter change can require updated written costs disclosure. Automation can flag a possible change for the solicitor to assess. Check your own costs obligations with your law society or regulator; this workflow design is not legal advice.

What Would a Stage-Change Update Look Like?

Example - a proposed commercial dispute workflow. The matter moves to document review. The system prepares: “We have received the documents requested for review. Your solicitor will review them and contact you about the next step.”

The assistant checks receipt against the file and confirms the wording fits the approved stage template. Any added explanation of legal significance goes to the solicitor. After approval, the portal message is sent and logged on the matter. A later quiet-matter check would prepare a fresh draft from the recorded activity. For another proposed workflow, see conveyancing client updates.

How Do You Measure Fewer Status Calls?

Keep a simple tally for a few weeks before and after introducing each workflow. Agree what counts as a status enquiry so staff record calls and emails consistently.

• Count status enquiries per fee earner and compare similar matter workloads.
• Track time to first reply, stage-update coverage and matters past the contact threshold.
• Review dismissed drafts, failed sends and clients who call again after an update.

A lower enquiry count needs context. Check a sample of messages for accuracy and usefulness, and ask repeat callers what the update failed to explain.

What Should a Law Firm Not Automate in Client Communication?

I would keep advice, settlement discussions, bad news, costs decisions and conflict or complaint replies with the solicitor. Also flag matters where contact itself may be unsafe, including some family matters. A recorded stage change alone should never authorise contact in those circumstances.

Keep substantive detail in the portal; use SMS only to say there is something to read, subject to the firm's contact-safety rules. Assign someone to review failed sends and held messages. The NSW regulator explicitly says system failure cannot excuse compromised client service.

When Is Truespeak the Best Fit?

Truespeak is the best fit for an Australian law firm that needs automation designed, built and run around its existing software, with a person approving anything sensitive. At Nikon Australia, I built an AI chatbot that deflected 140+ customer service calls a month.

For this proposed design, I'd check native settings first, then scope any additional layer. Truespeak works with existing tools; where there is no usable connection, that step stays manual. After launch, Truespeak monitors failures, reviews exceptions and improves the rules. Truespeak provides no legal advice. The Truespeak law firm automation page explains the service, and a discovery call is the first step.