The call usually lands in the early afternoon, right when you've finally got your head down. It's a client you filed for last week. They're not angry, they're not even worried exactly, they just want to know. Did it go through? Is it done? Has the other side responded yet?
Your front desk doesn't have the answer sitting in front of them, so they put the client on a brief hold, walk back to your office, and interrupt the very work the client is calling about. Two minutes later everyone's back where they started, except now you've lost your place in it.
One call like that is nothing. The trouble is they cluster. A few a day, every day, each one small, each one pulling someone off billable work to report news you already knew and simply hadn't passed along. The client isn't asking for anything new. They just don't know what you know, and to a client, silence tends to read as nothing is happening.
Where the 'any update?' call really starts
People don't reach for the phone when they feel looped in. They call when there's a gap, and the gap usually isn't about facts. It's about reassurance. A client who dropped off a folder of documents wants to know the folder didn't vanish into a pile. A patient waiting on a pre-authorization (the insurer's sign-off before a procedure) wants to know somebody's actually chasing it.
Watch when these calls hit and you'll see they're rarely random. They come at the moments a reasonable person starts to wonder: a few days after they handed something over, right around a deadline they already know about, or whenever they've heard nothing for a stretch that feels long to them even if it's routine to you.
That predictability is the whole opening. If you can name the three or four points where a client reliably gets anxious, you can get a short message to them at each one, before they ever pick up the phone.
The four messages worth sending on their own
You don't need a running commentary on every matter. You need a handful of plain checkpoints that fire when a real step happens in your case management or practice software (the system where you already track the work). Keep them short, specific, and free of jargon.
- We've got everything we need. Goes out the moment intake marks the file complete. It kills the most common worry of all, that the handoff didn't land, and it's the single message that heads off the most calls.
- It's filed today. Sent the day you file the matter, submit the claim, or send the return. Put the date in it, so the client has a record and a starting point to count from.
- We're waiting on someone else now. The honest one. It tells the client the ball sits in another court (the court, the insurer, the other firm) so a quiet week reads as normal rather than stalled.
- Expect to hear from us by X. Sets the next checkpoint. A client who has a date in hand isn't counting days against a finish line they can't see.
Notice that none of these promise an outcome. Every one reports position, not verdict, and that distinction is where the honesty lives.
What automation can't do, and shouldn't try
Here's the part worth being straight about. An automated message can tell a client that a step happened. It cannot tell them whether the step was good news. Those are two different jobs, and only one of them is safe to hand to software.
'Your claim was processed' is a fact. Whether it was paid, cut down, or denied is a judgment, and a denial that shows up as a cheerful automated text is worse than no text at all. The same goes for a ruling that went against your client, a return with a balance due they weren't expecting, or anything touching a diagnosis. Those conversations stay human, every single time.
So draw the line at position, not substance. Automate 'it's filed,' 'we've received their response,' or even 'there's an update on your matter and your attorney will call you this afternoon.' That last kind, the heads-up that signals contact without revealing the news, is often the right move for anything sensitive. The client hears from you promptly, and a person still delivers the part that needs a person.
Keep it from sounding like a robot
Status messages tend to fail in two directions. Too robotic and they feel like a shipping notification nobody asked for. Too chatty and they bury the one fact the client actually wanted. A few habits keep them on the rails.
- Write them once, in your own voice. Plain sentences, the firm's name, a signature that sounds like a human wrote it. You draft each message a single time and reuse it for years.
- Always leave a way back to a person. Every message should name someone to call or reply to. A status note that closes the door just makes people call to pry it open again.
- Send it where the client already is. Text for most, email where you need a paper trail, and honor anyone who asked for one or the other.
- Don't over-send. Four meaningful checkpoints beat twelve twitchy ones. If a message doesn't change what the client knows, skip it.
- Guard the names. One update sent to the wrong client erases the trust the other hundred built. Test every new message on your own number before it goes live.
Worth doing this week
You don't need to wire up the whole practice to start. Pick the one matter type that generates the most 'any update?' calls, probably the one with the longest waits between steps, and map just that.
- List the moments clients actually worry: after they hand something over, on filing day, during the wait on the other side, and near any deadline they know about.
- Write four short messages, one per moment, in your own words, each with a name and number to reply to.
- Mark the line. Decide which updates are safe to send automatically and which should be a 'we'll call you today' heads-up instead.
- Pick the channel for each client and confirm the reply path lands somewhere a person checks.
- Run it by hand for a week before you automate anything, so you catch the awkward wording while a human is still in the loop.
If stitching those triggers into your existing software is the part that stalls you, that's the kind of setup we do. The goal is simple either way: the client hears where things stand from you, and the phone rings a little less while you're heads-down on their work.