Automated Client Communication: Drip Sequences

Automated client updates save 15–30 minutes per matter per week on routine status emails — but the setup has more decision points than any of the three vendors advertise, and the human approval step is where most small firms either win or lose the time savings entirely.

This workflow is for solo lawyers and firms of 2–10 attorneys running Clio Manage, MyCase, or Smokeball who spend real time each week writing “just checking in” emails that say roughly the same thing for every matter at the same stage. If that describes you, a drip sequence tied to matter-stage triggers can reclaim that time without making clients feel ignored. The workflow below walks through configuration, AI-drafted update text, client-portal delivery, and — critically — the human approval step that keeps templates from going out cold on the wrong matter.

What you’ll need

Clio Manage (Boutique plan or above for automated reminders and client portal), MyCase (any paid tier — automation lives in the Communications tab), or Smokeball (Grow or Prosper plan for automated workflows)
Access to ChatGPT-4o or Claude 3.5 Sonnet for drafting update templates — either works; pick whichever you already pay for
Your firm’s matter stages already defined in your practice management software — if they aren’t, do that first; the automation is useless without it
30–60 minutes of setup time per practice area the first time through; roughly 10 minutes per additional practice area afterward

Step 1: Audit your matter stages and map which ones need updates

Before touching any automation settings, pull a list of every matter stage you use in your practice management software. In Clio, go to Settings → Matter Stages. In MyCase, it’s Settings → Case Stages. In Smokeball, stages live inside each matter type’s workflow template.

For each stage, answer two questions: Does a client typically wonder what’s happening right now? And would a two-sentence update genuinely answer that question? Stages where the answer to both is yes are your automation candidates. Stages where the answer to the second question is “not really — it depends” are your human-drafting stages. Mark them separately; you’ll treat them differently in Step 4.

A realistic estate planning matter might yield four automatable stages — intake complete, drafts sent for review, execution scheduled, matter closed — and two human stages — client review meeting pending, and any stage where a court date or third-party delay is involved. Family law matters almost always have more human stages than automatable ones. Factor that in before you invest setup time on a practice area that will override the automation constantly.

Step 2: Draft your update templates with AI

For each automatable stage, draft a short update template. The template should run three to five sentences: confirm what just happened, state what happens next and a rough timeframe, invite one specific question. Do not write these from scratch. Use this prompt — paste it into ChatGPT-4o or Claude 3.5 Sonnet, filling in the bracketed variables for each stage:

You are helping a law firm draft a brief client status update email for a specific stage in a legal matter. Write in plain, warm language — no legal jargon. Do not give legal advice or characterize outcomes.

Matter type: [e.g., Estate Planning / Personal Injury / Business Formation]
Matter stage: [e.g., "Draft documents sent to client for review"]
What just happened: [one sentence — e.g., "We emailed draft will and trust documents to the client today."]
What happens next: [one sentence — e.g., "The client reviews the drafts and sends questions or edits back to us."]
Typical timeframe for next step: [e.g., "1–2 weeks"]
Firm name: [Your Firm Name]
Attorney name: [First name or full name, your preference]

Write a 3–5 sentence client update email body only (no subject line, no salutation, no sign-off). Use "you" and "your" to address the client directly. End with one open question inviting the client to respond if they have questions or concerns. Keep total length under 100 words.

Run the prompt once per stage. Read each output carefully before saving it anywhere. The model occasionally produces a sentence that accidentally implies a timeline guarantee or characterizes what the client “should expect” in a way that overpromises. Delete those sentences and replace them with vaguer language. You are looking for warm and informative, not predictive.

Save each approved template in a plain text document organized by practice area and stage name. You’ll paste these into your practice management software in the next step.

Step 3: Configure triggers in Clio, MyCase, or Smokeball

Setup differs enough across the three platforms that it’s worth covering each separately.

Clio Manage

Clio’s native automation for client updates runs through Clio Grow (the CRM side) for intake and through document automation + tasks on the Manage side for in-matter updates. For stage-triggered emails, the most reliable path currently is: Settings → Task Automation → create a task rule that fires when a matter stage changes to your target stage, then use Clio’s email templates (under Communications → Email Templates) to attach a pre-written message to that task. The task assignee gets a prompt to send the email; it does not send automatically unless you’re using Clio’s Zapier integration to push to an email tool like Gmail or Outlook with a “send on behalf of” setup.

Fully automatic sending in Clio without a Zapier bridge is limited as of mid-2025. If you want true fire-and-forget, you need either Zapier (roughly $20–$50/month depending on your plan) or to wait for Clio’s own automation roadmap to mature. For most small firms, the task-based prompt is actually fine — it creates the human approval step naturally, which you want anyway.

MyCase

MyCase handles this more cleanly out of the box. Go to Settings → Workflows → Automated Messages. You can create a message rule tied to a case stage change, write or paste your template into the message body, and choose delivery via the MyCase client portal, email, or both. The portal delivery option is worth using — it creates a logged, timestamped record of every update, which beats digging through email threads later.

MyCase does allow fully automatic sending without a human approval step. That is a configuration choice, not a requirement. For the reasons covered in Step 4, I’d recommend leaving the “require approval before sending” checkbox on, at least for the first 60 days. MyCase surfaces this option in the workflow builder as a toggle labeled “Send automatically” versus “Queue for review.”

Smokeball

Smokeball’s automation lives inside matter type workflow templates. Open the matter type you want to configure, go to the Workflow tab, add a step at your target stage, and select “Send Email” as the action. Paste your template. Smokeball will merge the client’s name and matter details from the record automatically using its merge field syntax (e.g., {{client.firstName}}). Check the Smokeball merge field reference in their help docs for the current field names — they updated the syntax in the 2024.3 release and some older forum posts show the deprecated format.

Smokeball’s email actions in workflows go out via the firm’s connected email account (typically Outlook), which means they appear in sent mail and feel less like a portal notification and more like a direct attorney email. Clients sometimes reply to these expecting immediate personal attention. Set expectations in your onboarding paperwork accordingly.

Close-up detail shot of two hands resting on a laptop keyboard, the screen visible only as soft blue-grey light and abst

Step 4: Build the human approval step — and actually use it

This step is the one most workflow guides skip, and it’s the one that determines whether you save time or create problems.

Every automated update should pass through a 60-second review before it reaches the client. Not because the template is likely wrong, but because the matter context might make a generic update feel tone-deaf or, worse, factually off. A stage-change trigger doesn’t know that the client just called in tears, that opposing counsel sent a hostile letter this morning, or that the timeline in the template is no longer accurate because of a court delay.

Structure the review as a daily task, not a per-update interruption. In Clio and Smokeball, set the automation to generate a draft or a queued task rather than send immediately. In MyCase, use the “Queue for review” toggle. Then assign a 9 AM daily review task to the attorney or a trained paralegal: open the queue, read each queued update, check it against the matter, approve or edit, send. Firms that run this as a batched morning review rather than an interrupt-driven approval process consistently report it taking under five minutes per day once the templates are dialed in.

Flag any matter with an emotionally difficult development — a denial, a bad deposition, a custody complication — and pull it from the queue entirely. Write that update fresh. A template that says “Things are moving along and we’ll be in touch soon” landing the day after bad news is worse than no update at all.

Step 5: Connect to the client portal

If your practice management software includes a client portal — Clio for Clients, the MyCase portal, or Smokeball’s client-facing view — route automated updates through it rather than raw email where the platform allows it. Portal delivery gives you a read receipt equivalent (you can see when the client viewed the message), keeps the communication thread inside the matter record, and reduces the chance that a client replies to a firm-sent update by texting the attorney’s personal cell instead.

In MyCase, portal delivery is the default option in the automated message builder. In Clio, you’ll need to post updates to the client portal manually or via a Zapier step — Clio’s native stage-trigger emails go out by email, not portal post, as of mid-2025. In Smokeball, portal integration is available on the Prosper plan; on Grow, updates go via email only.

One practical note: some clients don’t log into portals. If a client hasn’t accessed your portal in 30 days, MyCase will flag this in the contact record. For those clients, switch delivery to email. Sending to a portal that nobody checks is not a client update — it’s a logged message to yourself.

Where this breaks

The time savings are real for transactional and process-heavy matters — business formation, estate planning, straightforward real estate closings, uncontested matters of most kinds. For those, 15–30 minutes per matter per week is a defensible estimate once the templates are running smoothly.

It breaks in two specific situations. First, emotionally heavy matters. Family law, criminal defense, personal injury with serious injuries — any practice area where the client’s anxiety is high and the situation is volatile will generate constant exceptions to the approval queue. You’ll spend more time deciding whether to override the template than you would have spent writing the email from scratch. Several family law solos I’ve spoken with tried this workflow and abandoned it for active litigation matters entirely, keeping it only for intake and closing stages.

Second, the setup cost doesn’t amortize well across a very small matter volume. If you have five active matters and cycle through them in two months, you’ll spend more configuring the triggers and drafting templates than you’ll ever recover. This workflow pays off at roughly 15+ active matters running concurrently, with meaningful stage repetition across matters in the same practice area.

There’s also a maintenance burden that vendors don’t mention: when your practice management software updates its workflow engine — which Clio, MyCase, and Smokeball each did at least once in the past 18 months — you may need to re-audit your triggers to confirm they still fire correctly. Build a quarterly 20-minute calendar block to test a sample trigger end-to-end. It’s tedious but cheaper than discovering three months of updates silently failed.

What this saves you

On a matter with six automatable stage updates across its lifecycle, a three-sentence status email that previously took 8–12 minutes to draft, find context for, and send now takes 60–90 seconds to review and approve. Across 20 active matters with one or two stage transitions per week each, that’s roughly 2–3 hours returned per week once the system is running. That’s not a theoretical maximum — it assumes the approval step stays disciplined and templates don’t need heavy editing. If you’re rewriting more than one in five templates at the approval stage, your templates need tighter drafts or your matter stages need finer granularity.

The less quantifiable return is client satisfaction. Clients who receive consistent, timely updates call less. In a firm where the attorney handles their own phones and email, fewer inbound “just checking in” calls from clients compounds the time savings beyond what any spreadsheet captures.

Notes on sustaining this over time

Revisit your templates every six months. Language that felt natural in January can feel stale or slightly off by July — especially if your intake process, fee structure, or standard matter timelines have shifted. Schedule a 30-minute template review twice a year; treat it like updating your engagement letter boilerplate.

If you add a practice area, don’t adapt templates from another area — draft fresh ones with the AI prompt above for that area’s specific stages. A business formation update repurposed for a probate matter will read as exactly that.

The human approval step is not optional overhead — it’s the feature. Firms that turn it off to save five minutes a day are the ones that eventually send a warm “great news, we’re making progress” update on a matter that went sideways two days earlier. Keep the queue. Keep the 60-second read. The system only works because a person is still in the loop.

Automated Client Communication: Setting Up Drip Sequences in Your Practice Management Software