Dallas, TX
Enterprise Cloud VoIP for Dallas TX Law Firms
A phone system for a firm of eight people is a set of rules. For a firm of eighty across three offices it is a set of decisions about who gets to make rules, and that is a different problem.
Book a Demo
Dallas firms at that size usually arrive at the same place: each office has evolved its own arrangement, nobody can say with confidence what happens to a call at five o'clock in the Uptown office, and every change requires finding the one person who understands the configuration.
Cleod9 provides cloud communication for Dallas-Fort Worth businesses, and a larger firm administers its own configuration. This page is about the governance questions that come with scale rather than the features. It is operational guidance rather than legal advice.
Decide what is standard and what is local
The central question at this size, and firms that never answer it end up with either rigid uniformity nobody follows or three systems wearing one name.
Some things should be identical everywhere. The intake sequence and its prohibitions, the conflicts questions and their order, recording handling and retention, the access model, and the way the firm identifies itself when it answers. These are professional and reputational rather than operational, and variation in them is a liability.
Some things should be local. Hours, ring groups, who covers which function, on-call rotations, and the routing inside a particular office. The people who run those days know things a central function does not.
Write the split down explicitly, in a page. Firms that leave it implicit discover the boundary during an argument about who authorized a change.
The test for putting something in the standard column is whether an inconsistency would embarrass the firm or create professional risk. If it would merely be different, it belongs to the office.
Central intake or local reception
Multi-office firms face this and it is worth deciding deliberately rather than by inertia.
Centralized intake means new inquiries reach one trained group regardless of which number they called. The screening is consistent, conflicts inputs are gathered the same way every time, and the firm can see its whole inquiry flow in one place. The cost is that a caller with a local relationship reaches a stranger.
Local reception means each office answers its own calls. Callers reach somebody who knows the building and the people, which matters for existing clients. The cost is variation, and the firm cannot easily tell how consistently new inquiries are being handled.
The arrangement most firms settle on is a split by caller type rather than by office. Existing clients reach their office; new inquiries route to a central intake group wherever they arrive. That takes the most consequential conversation and makes it consistent while leaving the relationship calls where they belong.
Whichever way it goes, the boundaries do not vary: conflicts inputs before anything invites narrative, and no legal advice, no view on whether there is a case, no fee quotes beyond published consultation pricing, no predictions, nothing implying the firm has taken the matter.
Delegating administration without losing control
A firm at this size cannot route every change through one person, and it should not give everybody the ability to change everything.
Three levels work for most firms. A small number of full administrators, two or three, who can change the standard items and the access model itself. An operational level in each office covering greetings, hours, group membership and rotations. And personal settings for everybody.
Give the operational level genuine authority over the local column. A design where an office manager must ask permission to change an on-call rotation is one where rotations stop being changed and start being worked around.
Keep recording access separate from system administration. They arrive in the same login and they are different questions: Rule 1.05 of the Texas Disciplinary Rules of Professional Conduct treats information relating to representation as confidential, including what a prospective client shares where no representation follows, so archive access deserves narrower treatment than routing configuration.
Ask Cleod9 what access levels exist, whether access to recordings is logged, and what a change history shows. Then write the firm's own page naming who sits at each level and why.
The numbering scheme is now infrastructure
At eight people an extension scheme is a convenience. At eighty across three offices it is the thing that makes internal reachability possible.
Use blocks that mean something across the whole firm rather than per office: attorneys in one range, paralegals and assistants in another, administrative in a third, shared and non-person extensions in a fourth. Anybody who knows the scheme can then guess correctly regardless of which office somebody sits in.
Leave gaps inside each block. Numbering in steps of two or five leaves room for years of hiring without renumbering, and renumbering later is disruptive because numbers get printed, learned and embedded in habits.
Extension-to-extension dialing has to work across every office and every remote worker. That single property is what makes transferring a caller to a colleague at another site a two-second action rather than a callback promise.
Build ring groups by function rather than by address, so a group contains whoever performs that function today. Adding or removing a person becomes a membership change rather than a redesign.
Each office needs its own hours
A detail that matters more than it sounds, and the one that most often forces a firm to rebuild its routing later.
Give every location its own inbound number and its own schedule, even where both ring the same group most of the day. That is what allows one office's hours, holidays or closure to change without touching another's.
Define the fallback for each location explicitly. The smallest office is where two people being busy simultaneously is normal rather than exceptional, and it is the site most likely to have calls ring out unnoticed.
Where the firm adds a location, the design should extend rather than be rebuilt. That is the practical test of whether the original design was any good, and it is worth asking before signing rather than after.
Reporting that a managing partner will actually read
Scale brings the ability to measure and the risk of measuring nothing useful.
- Abandoned calls by hour and by office, meaning calls that ended before reaching anyone. Most firms have never seen this and it is where the missed business is.
- New inquiries captured outside business hours, which is usually the clearest justification for after-hours coverage.
- Time from inquiry to first human contact, by office, which surfaces an office that is quietly slower than the others.
- Share of captured inquiries that reached a consultation, which measures whether intake is sorting rather than merely collecting.
- Transfers per call at reception, which measures how much traffic is landing in the wrong place.
Read these by office and by hour rather than as firm-wide totals. An average across three locations conceals the one that needs attention, which is the entire reason to measure at this size.
Onboarding at scale
At eighty people the firm is adding and losing staff continuously, and the phone system either keeps up or drifts.
Attach it to the processes that already exist. Extensions, group membership, access level and device setup belong on the same arrival checklist as the email account and the building access, and the same list in reverse on departure.
The departure half matters more. Reassign the extension so the number keeps working, remove the person from every group, update greetings that name them, and check whether they were the destination for any after-hours or overflow path.
Include the 911 registration item on both. The RAY BAUM'S Act addresses dispatchable location, requiring information specific enough for responders to find the caller, with compliance dates of January 6, 2021 for fixed devices in a multi-line system and January 6, 2022 for non-fixed devices and certain other configurations. Kari's Law separately requires direct 911 dialing without a prefix and notification to a central point on site when a call is placed. In a multi-floor office that is the difference between responders reaching a building and reaching a suite.
Teach three actions rather than a system: answer, transfer to a person, transfer to a voicemail box. Everything else is learned as it comes up.
Attorneys who are rarely at a desk
At this size a substantial share of the firm is in court, at depositions, at client sites or working from home on any given day.
An extension that follows the person, with the firm's caller identification on outbound calls, is what keeps client contact on the firm's system rather than on personal mobiles. When an attorney hands out a personal number because the office line does not reach them, the relationship moves off the firm's system entirely and leaves with them.
Set availability rules per person rather than firm-wide, and write the trial week variant at the same time as the normal one, since the moment a firm needs it is the moment nobody has time to design it.
Settle explicitly whether calls from mobile devices on the firm's system are recorded. This is the question most often left unasked at scale, and either answer is defensible provided the firm chose it and told the people affected.
Common questions
Should every office use the same greeting?
The way the firm identifies itself should be consistent. The specifics of hours and options belong to the office.
How many administrators?
Two or three at the full level, with a named operational owner in each office. One is a risk on the day they are unavailable; giving everybody full access means nobody is responsible.
Can we standardize intake without centralizing it?
Yes. A single configured intake sequence used everywhere gives consistency even where the people answering sit in different offices.
What happens when we add an office?
A number, hours, groups and devices. The routing logic is not in any building, which is what makes a new location a configuration change rather than an installation.
Consolidating three arrangements into one
A firm that grew by opening offices, or by absorbing a smaller practice, is rarely migrating one system. It is reconciling several, and the reconciliation is the project rather than the technology.
Start with an inventory per office: every number, every rule, every voicemail box, and every line that is not a telephone. Alarm systems, elevators and certain equipment use telephone lines with their own requirements and are not ported like a business line.
Expect surprises. Firms consistently find numbers nobody knew they owned, a rule pointing at somebody who left two years ago, and at least one office paying separately for something the firm already has.
Then decide, office by office, what to carry forward and what to replace. The temptation is to reproduce each arrangement on the new platform, which wastes the only cheap opportunity to fix any of it. The opposite temptation, imposing one design everywhere on day one, breaks things that were working for local reasons.
Sequence it by office rather than all at once. One location, configured and tested and run for a fortnight, teaches the firm what its own standard should be. The second and third then go faster and the mistakes are made once rather than three times.
Do not cancel any existing service until the port has completed and testing confirms it works. A number released by cancellation may be unrecoverable, and at this size the firm's main numbers are on filings, letterhead and directories the firm cannot update.
What the firm owns and what the provider owns
Worth being explicit at scale, because the gap between the two is where things go unowned in a larger organization.
The provider is responsible for the service running, and for whatever the contract commits about availability and support. Ask those questions before signing: what is committed, what happens when something goes wrong, and how the firm reaches somebody who can act rather than log a ticket.
The firm owns the configuration entirely. Who has access, what the routing does, what greetings say, how long recordings are kept, and who is in which group. None of that maintains itself, and at eighty people the drift is faster because more people are joining and leaving.
The office network sits with the firm as well. Calls travel over the same connections as everything else, so the connection, the equipment and whether desks are wired or on wifi are the firm's to get right in each building.
The data questions are shared. The provider answers where recordings, transcripts and message content are stored, what the default retention period is, whether the firm can set its own, and whether specific records can be deleted on request. The firm decides what to do with those answers, and at this size the decision should be written down and applied identically across every office.
Ask what leaving looks like as well. Numbers port out because portability is a federal requirement; recordings, transcripts and message history are a contract matter, and it is an easier question before signing than during a change.
An annual review that scales
At this size the review cannot be one person walking the whole configuration, so split it.
Each office reviews its own local column: greetings, hours, group memberships, on-call routing, and the destinations that captured calls land in. An hour per office, done by the named operational owner.
The firm reviews the standard column centrally: the intake sequence and its prohibitions, recording retention against what the written policy says, the access list, and the numbering scheme.
Both halves include the same verification step, which is calling the paths rather than reading a screen. Ring the main number and let it go unanswered, ring after hours from a mobile, trigger the overflow path, and confirm 911 location for every device including any that moved.
Then compare the offices against each other. A location whose numbers differ noticeably from the others is either doing something better, which is worth copying, or has drifted, which is worth correcting. That comparison is the main advantage a multi-office firm has and almost none of them use it.
Talking to Cleod9
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a Dallas firm deals with someone in the same metro rather than a distant ticket queue. The platform is described on the Cleod9 services page.
Bring the standard-versus-local page, even in draft. A firm that has decided what must be identical everywhere and what belongs to each office gets a configuration that matches how it is actually governed, rather than one that becomes the governance by default.