Richardson, TX
Legal Client Update Texting for Richardson TX Attorneys
Most Richardson firms that decide to text clients about their matters get the technology working in an afternoon and then stall for a month. The reason is never the platform. It is that nobody has decided who is allowed to write the messages.
Book a Demo
The attorney is in a deposition. The paralegal knows the answer to the client's question. The client is waiting. Everybody involved understands that a two-line message would resolve it, and nobody is quite sure whether the paralegal can send it. So it waits, and by the time it does not wait, the client has already called twice.
Cleod9 provides cloud communication for Dallas-Fort Worth businesses, including business text messaging. This page is about the workflow rather than the channel: who drafts, who approves, what can go without approval, and how to build that so it does not become a bottleneck. It is operational guidance about communication practice, not legal advice, and the firm's supervision obligations are for the firm and its own counsel to interpret.
Three kinds of update, and they do not need the same handling
Treating every client message as requiring attorney review is the reason firms end up sending none. Sorting them once solves most of it.
Purely factual and administrative. A hearing date moved. A document arrived. An appointment confirmation. These state a fact the client can verify and involve no judgment about the matter.
Substantive but routine. A stage of the matter has changed, something was filed, a response was received. The fact is factual, but describing it involves choices about what to say and how to frame it.
Consequential. News the client will not like, anything touching strategy, anything where the client is likely to reply with a question the sender cannot answer.
The first category can be sent by trained staff from approved wording without waiting for anyone. The second is drafted by staff and reviewed before it goes. The third is written by the attorney, and it is often not a text message at all.
Write that split down and put names against each level. It takes half an hour and it is the difference between a channel that works and a channel that sits idle.
A template library is the actual deliverable
The first category only works if the wording exists in advance. Otherwise every message is a fresh drafting decision, which means every message is a judgment call, which means everything drifts back to needing review.
Build a short library of pre-approved messages with blanks in them. Ten to fifteen covers the great majority of what a firm sends. Each one is written once, reviewed once by whoever the firm decides reviews such things, and then used as written.
The discipline that keeps this working is that staff fill the blanks and do not edit the sentences. If a situation does not fit any template, that is the signal to escalate rather than to improvise, and staff should be told so plainly. A template that gets rewritten each time is not a template, it is a suggestion.
Review the library twice a year and whenever a practice area changes. Retire what is unused, add what keeps getting escalated, and keep the whole thing on one page.
Who may press send
Name the people. Not roles, people, with a written list that somebody owns.
Access to the messaging channel should match that list, so the answer is enforced by configuration rather than by memory. Ask during setup who can see threads, who can send, and whether those two permissions can be separated, because being able to read a client thread and being able to write in it are genuinely different levels of trust.
The other half of this is that messages leave from the firm's number, never from an individual's mobile. A thread on a personal phone cannot be supervised, is invisible to whoever covers when that person is out, and leaves the firm when they do. That is not a policy preference. It is the reason the whole workflow is possible at all.
The review queue, and how to keep it from becoming the bottleneck
The second category needs approval, and approval is where good intentions go to die. Two things prevent it.
First, batch it. An attorney who is asked to look at drafts twice a day, at set times, will do it. An attorney interrupted eleven times a day with single messages will start deferring, and the deferrals accumulate into a backlog nobody clears.
Second, set a maximum age. Anything in the review queue for more than a stated period, which for most firms is one business day, either goes out or gets a decision that it is not going out. A queue with no expiry becomes a place where drafts go quietly to sit, and the client experiences that as silence rather than as caution.
Both of those need someone to own them. In a small firm that is usually the same person who owns the queue in the first place, and the ownership should be explicit rather than assumed.
Supervision is why the workflow exists
A firm's obligations for supervising both attorneys and non-lawyer assistants are its own to interpret, and its own counsel is the right source on what those obligations require.
The operational point is narrower and worth stating. A workflow with defined categories, approved wording, a named list of senders, and a reviewed queue is a workflow the firm can describe. An arrangement where a paralegal texts clients from her own phone using her own judgment is not, regardless of how good her judgment is.
That is the practical case for doing the half hour of design work. It is not about distrusting staff. It is about the firm being able to say how client communication happens, which becomes important on exactly the days nobody planned for.
What a message may contain
Separate from who writes it, there is what may be in it, and this list should be written on the same page as the template library.
An update reports. It does not interpret, predict, or reassure. Saying the hearing is set for the fourteenth is a report. Saying the hearing is set for the fourteenth and it should go well is an opinion the firm did not intend to give and the client will remember precisely.
Keep case substance out. A text message is read on a lock screen, possibly in front of somebody else, and it is stored on a device the firm does not control. The safe shape for anything sensitive is a message saying the firm needs to speak with them and offering a time, rather than the content itself.
And avoid estimates unless the firm genuinely intends to be held to them. Should be about two weeks is heard as two weeks, and the follow-up conversation in week three is entirely avoidable.
The message the attorney has to write
News a client will not want is the category that most often gets handled badly, and text is usually the wrong container for it.
The workable pattern is that the difficult content is delivered by the attorney, by phone or in person, and the messaging channel is used to arrange that conversation rather than to carry it. A short message saying there has been a development and asking when the client can talk today does its job without doing damage.
The firm should say this explicitly in its written rules, because in the moment it is genuinely tempting to send the bad news in writing and avoid the call. Staff need to know that is not an option available to them, and attorneys benefit from having decided it in advance too.
Replies are the part nobody staffs
Every update invites a response, and roughly one in five clients will send one. Those replies arrive at a shared number rather than at the person who sent the message.
Decide who watches the reply queue and during what hours, and decide what happens to a reply that needs the attorney. The default failure here is that replies are seen by everyone and owned by no one, which produces both duplicate answers and unanswered ones in the same week.
The firm should also decide what the channel is for and tell clients. If texting is for updates and scheduling rather than for substantive questions about the matter, say so at the start, kindly, and repeat it when a substantive question arrives.
Keeping the record straight
A message to a client is a communication about the matter, and it should be retrievable later along with everything else.
Settle the factual questions with Cleod9 in writing: where message history lives, how long it is retained, whether that is configurable, who inside the firm can see it, and how a thread is exported into the matter file. Then the firm and its counsel can set a policy that actually holds.
Consent and stop requests belong in the same discipline. Client consent to be texted should be captured with the engagement rather than assumed, and a request to stop is honored promptly and recorded where the next person will see it. Federal rules on how consumers revoke consent have been updated in recent years, and the current requirements are a question for the firm's counsel rather than for a summary.
Common questions
Can a paralegal send client updates at all?
That is a supervision question for the firm and its counsel. What the workflow above does is make the answer specific rather than general: certain approved messages, sent by named people, with anything outside that escalated. Firms usually find that a defined narrow permission is easier to stand behind than an informal broad one.
How many templates does a firm actually need?
Ten to fifteen for most practices. If the number climbs past twenty five, the library has usually started absorbing messages that belong in the reviewed category.
What if the client replies with a legal question?
Have a pre-written response for exactly that, saying the firm wants to answer it properly and offering a time to talk. It is the most common reply a firm gets and the one most likely to be answered off the cuff.
Should attorneys send updates themselves?
For the consequential category, yes. For the routine ones, an attorney doing the sending is usually the reason updates stop happening during a busy month, which is the problem the workflow exists to solve.
What to look at after ninety days
A few signals show whether the workflow is holding:
How long drafts sit in the review queue, and whether anything is aging past the stated limit.
How many messages are sent from templates without review, which should be most of them if the categories were drawn correctly.
How often staff escalate something that turns out to be routine, which should be non-zero. If it is zero, the escalation rule is not being used.
Client calls asking for a status, which is the number the whole program exists to reduce.
Whether anyone is still sending from a personal phone, which is worth confirming rather than assuming.
Talking to Cleod9
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a Richardson firm works with someone in the same metro rather than a distant queue. The platform is described on the Cleod9 services page.
The concrete questions to settle are permissions, retention, and export: who can read a thread, who can send in it, how long history is kept, and how it comes out into the matter file. The three categories and the template library stay with the firm, and they are the part that determines whether the channel gets used at all.