Arlington, TX
Multi-Location VoIP Control for Arlington TX Law Firm Groups
A firm group is not a fixed thing. Offices open, a smaller firm is absorbed, a location that made sense four years ago is consolidated into the one eight miles away, and occasionally a practice group leaves and takes its work with it.
Book a Demo
Most writing about multi-location phone systems assumes a stable set of offices and asks how to run them consistently. That is the easy half. The harder half, and the one that costs Arlington firm groups real money, is what happens during the months when the shape is changing.
Cleod9 provides cloud communication for Dallas-Fort Worth businesses across multiple locations. This page is about the transitions: adding an office, absorbing a firm, closing a location, and losing a group. It is operational guidance about phone and number management, not legal advice, and questions about client notification, file handling, and professional obligations during any of these events belong with the firm's own counsel.
The inventory nobody has
Every one of these events starts in the same place, and almost no firm group can produce it on request: a complete list of the numbers the group owns.
Not the main lines. Every number. The fax line that still receives things. The number on a billboard from 2019. The direct dial that three referring firms have saved. The number a practice group used before it merged in. The one on the side of a vehicle. The one printed on an old set of engagement letters that clients still have in a drawer.
For each, three facts: where it is published, what currently answers it, and who at the group would notice if it stopped working. That last column is the useful one, because it identifies the numbers nobody is watching, which are exactly the ones that get lost in a transition.
Build this once and maintain it. An hour spent now is the difference between a smooth consolidation and a quarter of quietly missed calls.
The four events, and what each one actually requires
They look different and they share most of their mechanics:
- Opening a new office. Mostly additive, and the easiest to get right, because nothing existing has to keep working.
- Absorbing another firm. The hardest, because two of everything has to become one of something without breaking either.
- Closing or consolidating a location. Deceptively simple, and the one where numbers most often get abandoned.
- A practice group departing. Rare, awkward, and worth having thought about before it happens rather than during.
An acquired firm's numbers are assets, not clutter
The instinct when a smaller firm joins is to move everyone onto the group's main number and retire the old one. It is usually the wrong instinct and it is expensive.
That number is on the acquired firm's website, in its former clients' phones, in referral sources' address books, in directory listings the group does not control, and on documents in filing cabinets. Turning it off does not consolidate anything. It removes a route that people are still using.
Port it and keep it. It can ring wherever the group decides, carry its own greeting, and be measured separately so the group can see how much traffic it still carries. Two years of that data tells the group when, or whether, it can be retired. Guessing does not.
The porting itself needs the same care as any port: nothing gets canceled with the old provider until the new service is confirmed working, the account details have to match the old records exactly, and the emergency address information for each location has to be correct before anyone relies on the line. Those steps are unglamorous and they are where port days go wrong.
What the joining office keeps, and what it adopts
The group has to decide, deliberately, what is standard across all locations and what belongs to the site. Doing it explicitly at the moment of a merger is far easier than retrofitting it later.
Things that are usually worth standardizing: the numbering scheme for extensions, how calls that reach nobody are captured, access levels for who can change what, and how the group measures its phones. Things that usually belong to the location: the greeting and how the office identifies itself, business hours, which local staff answer what, and any local number.
Where firms get into trouble is standardizing the caller-facing parts and localizing the administrative ones, which is precisely backward. Callers to the joining office should hear something appropriate to them. The group's ability to see and control the estate should not vary by site.
The extension collision
Two firms merging almost always find both were using extensions in the same range, and both have those numbers written on desks, in directories, and in people's memories.
There is no painless answer, only a choice made early. Either the joining office renumbers, which is disruptive once and finished, or the group adopts a scheme with room for both, which usually means going to a longer extension and renumbering everybody. The second is more work and it is the one that survives the next merger.
Whichever is chosen, do it on a date, communicate it twice, and keep the old extensions routing to the new ones for a stated period rather than switching them off. Announcing that old extensions stop working in ninety days, and meaning it, works far better than letting them linger indefinitely.
What callers hear during the change
A transition is audible, and the group controls how it sounds.
Decide what the joining office's greeting says and for how long. Firms usually run a transitional version that names both identities for a period, then simplifies. Whatever the group chooses, it should be written and recorded before the change rather than improvised the morning after.
The directory matters as much as the greeting. A caller who dials by name during a merger, and reaches a listing for somebody who left the acquired firm last year, has learned something about the group that the group did not intend to tell them. Directories go stale fastest during exactly the periods when the most people are joining and leaving.
Administration during the unsettled months
The temporary state is where control is most often lost, because the transition requires more people to be able to change more things than usual.
Give the transition its own access decisions rather than handing out permanent administration to whoever is helping. A small number of people who can change the estate, a larger number who can change only their own site, and everybody with an individual login rather than a shared one.
The last point is the one that matters most. Shared credentials during a merger are how a group loses the ability to say who changed what, and the change log is the only thing that answers the question three months later when something is misrouted and nobody remembers.
Then set a date to review access after the transition ends. Permissions granted for a project have a way of becoming permanent, and the review is a ten-minute meeting that prevents a much longer one later.
Closing an office without abandoning its number
Consolidation is where numbers get orphaned, because the office closing is the office nobody is monitoring.
A closed location's number should keep working and should route somewhere sensible, with a greeting that says what has happened and where the work now lives. Not a disconnection message, which sends callers to whoever is next on their list.
Keep it for longer than feels necessary. Referral sources and former clients update their records slowly, and the cost of maintaining a number is trivial against the cost of a call that reaches a disconnection recording. Measure it, and let the traffic tell the group when it can go.
The same care applies to everything else pointing at that location: directory listings, the website, printed material, the map listing that shows an address the group no longer occupies. The phone is the part that keeps working; the rest of the trail is what has to be corrected.
When a practice group leaves
This is the least comfortable of the four and the one most worth thinking about in advance, while nobody is upset.
The operational questions are specific. Which numbers belong to the group and which, if any, are leaving. What happens to extensions, and how quickly access is removed. What happens to call recordings and message threads relating to matters that are moving. How calls arriving on a familiar number are handled during the period when both the group and the departing lawyers have a legitimate interest in reaching the caller.
Almost every one of those touches obligations that are not operational at all, including how clients are notified and what happens to files. Those belong with the firm's own counsel, and the phone plan should follow the answer rather than lead it. What the operations side should have ready is the inventory, the access removal procedure, and the ability to change routing quickly and to record what changed.
Run it as a project with dates
Every one of these events goes better when it is sequenced rather than handled as it comes up:
- Build or refresh the number inventory, with the who would notice column filled in.
- Decide what is standard and what is local, in writing, before touching any configuration.
- Settle the extension scheme, including whether anyone is renumbering.
- Port or provision numbers, confirming service works before anything is canceled and checking the emergency address for every location.
- Record greetings and update directories, in advance, for the day of the change.
- Set access for the transition, with individual logins and a review date.
- Switch, on a stated date, with old routes kept alive for a defined period.
- Measure for a quarter, then retire what the data says is genuinely unused.
What tends to break
The failures are consistent across firm groups and all of them are preventable:
A number that was not on anybody's list and stopped working without being noticed.
Emergency address information that was never updated for a new or moved office.
A directory listing the group does not control, still pointing at a closed location.
Extensions that collided and were resolved differently in different places.
A shared administrative login that makes the change log useless.
Recordings and message threads that nobody decided about until they were needed.
Old routes switched off too early, on the theory that everyone had been told.
Common questions
How long should we keep an acquired firm's number?
Longer than instinct suggests, and let the traffic decide. Firms that measure usually find meaningful call volume two years on, particularly from referral sources.
Should every office sound the same to callers?
Generally no. Callers are contacting an office, and a greeting that identifies it is more useful than a uniform group message. Consistency belongs in the administrative layer rather than in what people hear.
Can each office manage its own settings?
It should be able to manage its own greetings and hours, since those change locally and a change that requires a ticket is a change that does not happen. Estate-wide settings should stay with a small group.
What if we do not know what numbers we own?
Then that is the first task, before anything else is decided. The billing records from current and previous providers are the usual starting point, and the exercise nearly always turns up two or three numbers nobody could account for.
The quarter after the change is when you learn what happened
Transitions are judged on the switch day and they should be judged three months later, because most of what goes wrong is silent at the time.
Put a review on the calendar for ninety days out and give it four questions. Which numbers carried traffic and which carried none. Where calls that reached nobody ended up, and whether anyone worked that list. Whether the joining office's callers are reaching people in the same number of steps as everyone else. And whether the access granted for the transition is still granted.
That last one catches something every time. It is also the easiest to fix, and fixing it takes about ten minutes if somebody remembers to look.
Talking to Cleod9
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so an Arlington firm group works with someone in the same metro rather than a distant queue. The platform is described on the Cleod9 services page.
Bring the number inventory. It converts a general conversation about multi-location service into specific questions about porting, per-site greetings and hours, access levels and change logging, retention of recordings and message history, and how quickly routing can be changed on a day when it has to be. The decisions about what is standard and what is local stay with the group, and they are what everything else follows from.