Grand Prairie, TX
Two-Way SMS Client Messaging for Grand Prairie TX Law Firms
Somebody takes over a Grand Prairie firm. A partner buys out a retiring founder, a managing partner takes the administrative side, or a firm acquires a smaller practice and now owns its arrangements.
Book a Demo
Among everything else they inherit is a communications setup nobody documented. Numbers pointing at destinations chosen years ago for reasons nobody remembers. A greeting recorded by somebody who left. Access held by people who no longer need it. A messaging channel where the history is unclear and the rules were never written down.
None of it is urgent, which is exactly why it stays that way for two years and then produces a problem at the worst possible moment.
Cleod9 provides cloud communication for Dallas-Fort Worth businesses. This page is a method for auditing a setup you did not build. It is operational guidance, not legal advice, and anything touching the firm's professional obligations, client notification, or file handling belongs with the firm's own counsel.
Start with the bill
The invoices are the only complete record of what the firm is paying for, and they are the fastest way to find things nobody mentioned.
Pull twelve months from the current provider and from any previous one still appearing on a statement. List every number, every line, and every recurring charge. Then ask, for each item, what it is for and who uses it.
The answers separate into three groups: things the firm uses, things it stopped using and kept paying for, and things nobody can identify. That third group is the useful one, and it is never empty.
Build the number inventory
For every number the firm has, three facts: where it is published, what answers it today, and who at the firm would notice if it stopped working.
That last column is the one that reveals the risk. A number nobody would notice is a number that could fail silently for months, and it is frequently the one printed on documents in clients' filing cabinets.
Expect to find a fax line that still receives things, a number from an old advertisement, a direct dial that referring firms have saved, and at least one number that predates anybody currently at the firm. Do not disconnect anything during the audit. Measure the traffic first and decide later.
Call your own firm, every path
Twenty minutes with an outside phone, and it produces more than any amount of reading configuration.
Call the main number during business hours and listen to the whole greeting without pressing anything. Then press each option in turn and follow where it goes, timing how long it takes to reach a person. Then call after hours and do the same. Then call each direct number on the inventory.
Write down what you hear rather than what you expected. The things that turn up are consistent: an option for a practice area the firm no longer handles, a name in the directory belonging to somebody who left, a mailbox that is full, a greeting recorded in a room with an air conditioner running, and a path that ends in silence.
One firm in three finds an option that leads somewhere it should not lead at all. That is the finding that justifies the twenty minutes.
Find out who has access
Ask the provider for a list of everybody who can log in, what each of them can do, and when each account was last used.
Then compare it to the current staff list. The gap is the finding. Former employees, a contractor who helped with a project in 2023, a vendor account nobody can explain, and usually one shared login that several people use.
The shared login is the item to fix first. It makes it impossible to establish who changed anything, which matters most in exactly the situation a new owner is trying to avoid: something is misrouted, nobody knows when it changed, and the change log says one word.
Decide who should have access, at what level, and remove the rest. Then confirm that at least two current people can make changes, since a firm where one person understands the system has a different problem waiting.
The routing nobody understands
Some of what the audit turns up will make no sense, and the temptation is to assume there was a reason.
Sometimes there was. An option that routes oddly may exist because a particular referral source calls a particular way, or because a former partner wanted their calls handled specifically. Ask the longest-serving staff member before changing it. They frequently know, and the explanation takes thirty seconds.
Where nobody knows, do not simply delete it. Point it somewhere staffed, note the change and the date, and watch the traffic for a month. If nothing arrives, retire it. If something does, you have learned what it was for without breaking anything.
Greetings describing a firm that no longer exists
Recorded greetings age faster than anything else in a phone system, because changing them requires somebody to decide to.
Listen to all of them: the main greeting, the after-hours version, any closure message left switched off, and every individual mailbox on the inventory. Note anything naming a departed person, a practice area the firm has dropped, or hours that are no longer accurate.
Rerecord them properly, in a quiet room, and confirm that firm staff can do this themselves rather than needing a support request. A greeting that requires a ticket is a greeting that stays wrong.
The messaging channel, if there is one
Firms increasingly inherit a client texting arrangement, and it is usually the least documented part of the setup.
Establish four things. Who can read threads and who can send. Whether anybody has been messaging clients from a personal mobile, which is the finding with the longest tail. How long message history is retained, whether that is configurable, and how a thread is exported into a matter file. And whether there is any written rule about what may be sent.
Where there is no written rule, write one before changing anything else, because the channel is live and carrying client communication while the audit proceeds. The essentials are short: nothing that gives advice, states a deadline, assesses anything, quotes a fee beyond published consultation pricing, or implies the firm has taken a matter; messages go from the firm's number; and anything outside a small set of approved replies gets escalated.
Do not change everything in month one
A new owner has both the authority and the motivation to rebuild the whole arrangement immediately, and it goes badly for a predictable reason.
Staff have workarounds built on the current setup, some of which are load-bearing and none of which are written down. Change six things at once and something breaks that nobody can trace, in the same period when the firm is already adjusting to new ownership.
Fix the safety items immediately: access, anything routing somewhere it should not, and any greeting that is actively wrong. Then work through the rest one change at a time, with a stated expectation for each, and a note of what actually happened.
The first ninety days, in order
A sequence that works:
- Pull twelve months of invoices and build the number inventory.
- Call every path from an outside phone, during and after hours, and write down what you hear.
- Get the access list, compare it to the staff list, and remove what should not be there.
- Fix the safety items: access, wrong routing, actively incorrect greetings.
- Ask the longest-serving staff about anything that looks odd before changing it.
- Write the messaging rule if there is not one.
- Watch traffic by number for a month before retiring anything.
- Then make one change at a time, recording each and what it was expected to do.
Ask the staff what does not work
The people answering the phones know exactly what is wrong with the arrangement and have usually never been asked.
Ask three questions and listen. What do callers complain about. What do you have to work around every day. What would you change if you could change one thing.
The answers are specific and cheap to act on: an option that sends the wrong people to the desk, a transfer that drops, a mailbox nobody owns, a number that rings in the wrong room. Fixing two of them in the first month also does something a new owner needs, which is demonstrating that the questions were real.
Write the page that should have existed
The audit's output is a single document, and its value is that the next person does not have to repeat any of this.
It holds the number inventory with destinations, who has access and at what level, the greetings and where they are changed, the after-hours arrangement, the support contact and account identifier, the messaging rule, and the retention and export answers.
Keep it to one or two pages and put a review date on it. A document nobody revisits becomes wrong within a year, which is precisely how the firm arrived at needing this audit.
Common questions
How long does the audit take?
The information gathering is a few hours spread over a week. The changes take a quarter, deliberately, because doing them slowly is what keeps them from causing problems.
Should we change providers while we are at it?
Not in the first month. Audit what exists, fix what is unsafe, and understand the arrangement before deciding whether to move it. A migration decided from an incomplete inventory is how numbers get lost.
What if the previous owner is still around?
Ask them, early, while they are still willing. An hour of questions about why things are the way they are is worth more than any amount of reconstruction, and the window closes quickly.
What is the single most common finding?
Access held by people who left, and a number nobody could account for. Both turn up in most audits and both are quick to resolve once somebody has looked.
The audit checklist
One page, worked through once:
- Twelve months of invoices, every line identified.
- Number inventory: published where, answered by what, who would notice.
- Every path called from an outside phone, during and after hours.
- Access list from the provider, compared to the current staff list.
- Shared logins eliminated, two current people able to make changes.
- All greetings listened to and rerecorded where wrong.
- Messaging: who can read, who can send, retention, export, personal phones.
- A written rule for what may be sent to clients by message.
- Traffic watched for a month before anything is retired.
- The one-page document, with a review date.
Talking to Cleod9
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a Grand Prairie firm works with someone in the same metro rather than a distant queue. The platform is described on the Cleod9 services page.
The audit questions are specific and a provider should answer them plainly: the full list of numbers on the account, who can log in and what each can do, whether changes are logged, how greetings are changed and by whom, what traffic reporting is available by number, and how message history is retained and exported. Those answers are the raw material for the one-page document, and getting them is the first useful thing a new owner can do.