Keller, TX
Cloud VoIP Phone System for Keller TX Law Firms
When a Keller firm moves to a cloud phone system it gains something it did not have before: the ability to change almost anything itself, in minutes, from anywhere.
Book a Demo
That is the main practical benefit and it comes with a question most firms never answer. Who at the firm can change what, and how would anybody know if something changed?
On an older system the answer was enforced by inconvenience. Nobody could reconfigure anything without calling somebody, so nobody did. Cleod9 provides cloud communication for Dallas-Fort Worth businesses and the firm administers its own configuration, which means the control has to come from a decision rather than from friction. This page is operational guidance rather than legal advice.
Three levels of access, decided once
Firms tend to have two states, full access or none, which produces either too many administrators or a single point of failure.
Full administration: the ability to add and remove people, change routing, alter recording settings and adjust access itself. This should be two people. One is a risk on the day they are unavailable; four means nobody is responsible.
Operational changes: greetings, hours, group membership, on-call routing. This is the level most day-to-day work sits at, and it should extend to whoever actually manages rotations and schedules rather than requiring them to ask.
Personal settings: an individual's own device, voicemail greeting and forwarding. Everybody has this and it needs no discussion.
Write down who is at each level and why. A page that takes ten minutes and answers a question the firm would otherwise resolve by accident.
Recordings are a separate question
Access to the system and access to what the system holds are different things, and firms conflate them because both arrive in the same login.
Call recording runs automatically on the platform. Access to recordings is governed by the access control list, which makes it a configuration decision rather than something inherited, and a default is almost always broader than a firm would choose.
Set it by role and keep it as narrow as the work allows. Intake staff generally need recent intake calls rather than the whole archive. Attorneys need their own matters. Administrative staff frequently need none at all.
Rule 1.05 of the Texas Disciplinary Rules of Professional Conduct treats information relating to representation as confidential, and its reach extends to what a prospective client shares even where the firm never acts. A recording archive is exactly that material, which is why the access list deserves more care than the routing configuration.
Ask Cleod9 whether access is logged and what a log shows. A firm that can say who listened to what is in a materially better position than one that cannot.
Individual logins, without exception
The rule that makes everything else in this page possible.
Shared credentials appear in small firms for practical reasons: one login for the front desk, one that everybody uses to change the greeting. It works until somebody needs to know who did something, at which point the answer is unavailable permanently.
Shared logins also cannot be revoked. When somebody leaves, a personal account is disabled in seconds; a shared password has to be changed and redistributed, and firms routinely discover months later that it was not.
Every person gets their own access at whatever level suits their role. This is not a statement about trust; it is what makes the record meaningful and departures clean.
Ask Cleod9 what account protections are available and enable what the firm can. A phone system holds client communications, and it deserves the same care as any other system the firm treats as sensitive.
Departures, which are where systems drift
This is the single most common gap, and it is not a security failure so much as a checklist failure.
Removing platform access belongs on the same departure checklist as the email account and the building key. A separate task, remembered separately, is a task done late.
The checklist should cover more than the login. Reassign the extension so the number keeps working and reaches whoever now handles those matters. Remove the person from every ring group, since group membership is where drift concentrates. Update greetings and voicemail messages that name them. Check whether they were the destination for any after-hours or overflow path.
Where the departing person had client contact on a personal mobile, that is the moment to move those clients onto the firm's channel, and somebody should own doing it.
Then verify by calling. A rule pointing at a departed colleague looks perfectly healthy on an administration screen and is obvious the moment somebody dials it.
Arrivals, which deserve the same list in reverse
A new person should be reachable on their first morning rather than three days later.
Extension assigned from the right block, membership in the right groups, access at the level their role requires, voicemail greeting recorded, and their device working. Fifteen minutes if the scheme exists, and a series of small decisions if it does not.
Add the 911 item explicitly. The RAY BAUM'S Act addresses dispatchable location, requiring the information sent with a 911 call to be 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 on-site notification when a call is placed. Registering a new person's device correctly belongs on the arrival checklist rather than in an annual review.
Show them three actions rather than a system: answer, transfer to a person, transfer to a voicemail box. Everything else can be learned as it comes up.
Knowing what changed
On a system anybody can change, the useful discipline is being able to answer what happened rather than preventing change.
Ask Cleod9 what change history is available: whether configuration changes are recorded, what a record shows, and how far back it goes. Ask the same about access to recordings.
Keep the firm's own note as well, which is lower technology and frequently more useful. A short log of significant changes, what and when and why, kept by whoever owns the system. It takes seconds per change and it is what makes a puzzling configuration explicable a year later.
Most of what a firm needs to explain is not misconduct. It is a routing rule somebody changed for a trial week and never changed back, and a note is what turns that from a mystery into a two-minute fix.
The annual review
An hour once a year keeps the configuration matching the firm rather than the firm it used to be.
- Walk the user list and confirm every account belongs to somebody who still works there.
- Walk the access levels and confirm each is still appropriate to the role, particularly recording access, which grows quietly.
- Walk the group memberships, which drift faster than anything else because nobody notices when a group is one person short.
- Listen to every greeting and voicemail message.
- Call the main number, the after-hours path and the overflow path rather than reading a screen.
- Confirm 911 location registration for every device, including any that moved and any used from home.
- Confirm the recording retention setting matches what the firm's written policy says.
That last item is worth its own attention. A policy naming twelve months while the platform retains indefinitely is worse than no policy, because it describes something untrue.
Who should own it
Name a role rather than a person, so it survives turnover, and give it four things: the routing rules and who they point at, the access list, the after-hours and failover paths, and the annual review.
In most firms this is the office manager or the firm administrator, with a partner owning the decisions about recordings, since those are professional judgments rather than operational ones.
Make sure at least two people can make changes. A configuration only one person understands is a problem on the day that person is unavailable, which is frequently the day a change is needed.
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a Keller firm has somebody in the same metro to ask rather than a distant ticket queue, but the ownership stays with the firm because the changes do.
Common questions
How many administrators should a small firm have?
Two. One is a risk on the day they are away, and more than two usually means nobody feels responsible for the configuration.
Should attorneys have recording access to their own matters?
In most firms yes, and the archive-wide access is the part worth restricting rather than the matter-specific access.
Can we tell who changed a setting?
Ask what change history the platform keeps and how far back. Keep the firm's own short log regardless, since it captures the reason as well as the change.
What if we outgrow the arrangement?
Revisit the levels at the annual review. Access arrangements are usually set when a firm is smaller and quietly become the reason a larger firm cannot move quickly.
What the firm is responsible for, and what the provider is
Firms moving to a cloud platform sometimes assume that handing over the equipment hands over the responsibility. The division is worth stating, because the gap between the two is where things go unowned.
The provider is responsible for the service running, for the platform itself, and for whatever the contract says about availability and support. Those are questions to ask before signing rather than after: what is committed, what happens when something goes wrong, and how a firm reaches somebody who can act.
The firm is responsible for everything about how the service is configured. Who has access, what the routing does, what the greetings say, how long recordings are kept, and who is in which group. None of that is the provider's to decide, and none of it maintains itself.
The office network sits with the firm as well. On a cloud platform calls travel over the same internet connection as everything else, so the connection, the router and whether desks are wired or on wifi are the firm's to get right. A provider can advise; it cannot fix a router nobody has replaced since before the current staff arrived.
And the data questions are shared. The provider answers where recordings, transcripts and message content are stored, what the default retention 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. Get them in writing and keep them with the firm's other records policies rather than in somebody's memory of a sales conversation.
Mobile devices, which sit outside the office entirely
Once extensions follow people, part of the firm's phone system is running on devices the firm does not own, and that deserves a short set of decisions rather than being left implicit.
Decide who gets the firm's extension on a personal device, which in most firms is anybody who needs to be reachable away from a desk. The alternative is what the firm already has, which is attorneys handing out personal numbers, and that is worse in every respect.
Decide what happens when the device is lost or replaced, and make sure whoever administers the system can remove access without needing the device itself.
Settle explicitly whether calls made from mobile devices on the firm's system are recorded. This is the question most often left unasked, and either answer is defensible provided the firm chose it and told the people affected.
Add device removal to the departure checklist alongside the login, since an extension still working on a former employee's phone is the clearest possible example of the drift this page is about.
And confirm how 911 location works for a firm extension used from home, since a device away from the office is exactly where the registration question is least likely to have been answered.
Talking to Cleod9
The platform is described on the Cleod9 services page, and the questions worth asking are about administration rather than features.
Ask what access levels exist, what is logged, and what a change history shows. Then write the firm's own page: who is at each level, who owns the system, and what happens on an arrival and a departure. That page is what keeps the configuration honest for the next five years.