Mansfield, TX
VoIP Phone System for Mansfield TX Law Firms
A phone system generates a record of the firm's communications continuously, without anybody deciding that it should. A Mansfield firm that has never thought about it has one anyway, and its shape was determined by defaults rather than by choice.
Book a Demo
That matters in both directions. There will be a day when the firm wants to establish that a call happened, or what was said on it, and either the record exists and can be retrieved or it does not. And there will be material sitting in the system that the firm never intended to accumulate.
Neither situation is improved by discovering it under pressure.
Cleod9 provides cloud communication for Dallas-Fort Worth businesses. This page is about what a phone and messaging system records, what to establish in writing, and how to retrieve it. It is operational guidance, not legal advice. What the firm must retain, what it must produce, and what its obligations are in any particular matter are questions for the firm and its own counsel.
What actually exists
Firms tend to think about recordings and overlook everything else. The record is broader:
Call detail. Who called, from what number, when, how long it lasted, where it was routed, and whether it was answered. This exists for every call and it is frequently the most useful item.
Call recordings, where recording is in use.
Voicemail, which is a recording of a caller's own words and sits in a different place from the recordings of live calls.
Message threads, where the firm uses business text messaging, which are written and persist.
Configuration changes, where the system logs who altered routing, greetings or access and when.
Call detail is the item most often forgotten and the one most often sufficient. Establishing that a call was placed to a particular number at a particular time, and lasted eleven minutes, answers a great many questions without anybody listening to anything.
Recording is automatic on this platform
Recording on the Cleod9 platform is automatic rather than something a person switches on for a particular call. A firm should know that before adopting it rather than discover it afterward.
The practical consequence is that the firm is not choosing per call; it is choosing a policy. Whether recording should be in use at all, for which calls, and what the firm does with what accumulates, are decisions the firm makes deliberately with its own counsel.
It also means the coverage is wider than people assume. Calls placed from mobile devices running the firm's system are calls on the firm's system, which surprises attorneys who think of a call from a car as somehow separate.
The questions to put in writing
These are factual questions with specific answers, and a provider should answer them plainly:
- How long is each type of record retained by default, and can the firm change that.
- Where is the material stored, and in what form.
- Who inside the firm can retrieve each type, and can that be limited by person or role.
- Who inside the provider can access it, under what circumstances, and is that access logged.
- How does the firm export a record, in what format, and can firm staff do it without the provider.
- How is a record deleted, who can do it, and what remains afterward.
- What happens to all of it if the firm leaves the provider.
- Is the firm notified if the provider becomes aware of a problem affecting its data.
Get the answers as a document rather than as reassurance during a sales conversation, and then take that document to the firm's own counsel. This page makes no claims about what any platform provides or satisfies; the point is to have the specifics rather than an impression.
Retention pulls in two directions
Keeping material too long and deleting it too soon are both real risks and they are opposites, which is what makes the decision a decision.
A record that no longer exists when the firm needs it is a problem. A body of recordings persisting for years in a system nobody thinks about is a different problem. Which risk matters more depends on the firm's practice and its obligations, and that judgment belongs to the firm's own counsel rather than to a default setting somebody accepted at installation.
What operations contributes is the factual half: what the default currently is, whether it can be changed, and whether a change applies going forward or reaches back into what already exists. Those three answers make the policy conversation possible.
Who can retrieve, and who can delete
These are separate permissions and they deserve separate thought.
Retrieval is the one firms notice, usually when somebody needs something. Deletion is the one that matters more, because it is irreversible and because a system where many people can delete records is a system where the firm cannot say with confidence what happened to any of them.
Ask whether the two can be separated, then decide deliberately. Most firms want retrieval available to a small named group and deletion available to fewer people still, or to nobody without a specific process.
Individual logins throughout. A shared administrative account makes it impossible to establish who retrieved or removed anything, which is precisely the question that gets asked when it matters.
Test retrieval before you need it
A capability nobody has exercised is an assumption. Retrieval is the one most commonly assumed and least commonly tested.
During setup, have somebody actually retrieve a call detail record for a specific call, export a recording, and export a message thread. Look at what comes out. Is it readable. Does it include timestamps. Does the thread include both sides. Can it be filed with a matter in the form the firm keeps things.
Twenty minutes there tells the firm what it actually has. Firms that skip it sometimes find, at the worst moment, that the export is a format nobody can open or that it omits the half of the conversation they needed.
Repeat it once a year, because systems change and so do the people who knew how.
What callers are told
Texas is a one-party consent state for recording as a general matter. That is background rather than advice about any particular firm's situation.
Whether the firm's greeting says calls are recorded, what it says, and how any of that interacts with the firm's own professional obligations are decisions for the firm and its counsel. What operations should do is make sure whatever the firm decides is actually reflected in the greeting, on every path a caller can take, rather than on the main line only.
Check it the way everything else gets checked: call each path from an outside phone and listen to what is actually said.
The records nobody knew were accumulating
Three categories turn up when a firm looks properly.
Calls made from mobile devices, which are on the firm's system and are recorded like any other, including calls made from a car or a courthouse hallway.
Video meetings, where recording behaves the same way and where the material is considerably larger. A firm that has been holding internal case discussions on video has been generating recordings of its own deliberations.
And message threads, which feel like conversation and are written records that persist. A thread on an individual's personal mobile is the version of this the firm cannot see, cannot retrieve, and cannot produce, which is the strongest practical argument for client messaging going through the firm's own number.
Write the policy after the answers, not before
Firms sometimes draft a records policy and then adopt a system, which produces a policy the system cannot support.
The better order is to get the factual answers, test the retrieval, take both to the firm's own counsel, and let the policy be written against what the arrangement genuinely does. A policy that matches reality is enforceable; one that does not is a document that creates its own exposure.
Whatever it says, it should cover at minimum: what is recorded, how long each type is kept, who may retrieve, who may delete, how something is exported into a matter file, and what happens on a departure.
The departure case
When somebody leaves the firm, the records associated with them do not.
Establish in advance what happens: whether their message history remains accessible to the firm after their access ends, whether recordings of their calls remain retrievable, and how the firm exports anything it needs before or after.
This is a specific question worth asking rather than assuming, because the answer varies and because the moment a firm needs it is a moment when nobody wants to be researching. Ask it during setup, write the answer down, and put the steps on the firm's departure checklist alongside removing access.
The annual check
Fifteen minutes once a year, and it prevents the specific failure of a firm believing something that stopped being true.
Confirm the retention periods are still what the firm decided. Confirm the list of people who can retrieve and delete still matches the current staff. Retrieve one record of each type to confirm the procedure still works and that somebody still knows how. And confirm the greeting still says whatever the firm decided it should say.
Write the date on the policy each time. A policy without a review date drifts quietly out of accuracy, and nobody notices until it is being relied on.
Common questions
Do we need to keep recordings at all?
That is exactly the question for the firm's own counsel, and the answer depends on the firm's practice and obligations. What the firm should not do is leave it to whatever the default happens to be, in either direction.
Is call detail useful without recordings?
Frequently, yes. Establishing that a call occurred, when, to which number, and how long it lasted answers a large share of the questions that arise, and it is a smaller and simpler body of material than recordings.
What about calls on an attorney's personal phone?
The firm has no record of them at all. That is the point: whatever policy the firm writes applies only to calls on the firm's system, and calls made outside it are outside everything on this page.
Can we delete something specific if we need to?
Ask, in writing, and test it. The answer varies by record type, and knowing it in advance is considerably better than finding out during the situation that prompted the question.
The page to keep
The output of this exercise is short and it is what the firm hands its own counsel:
- The written answers to the eight questions above, dated.
- What is recorded and what is not, including mobile and video.
- Retention in effect for each record type, and who can change it.
- Who may retrieve, and who may delete, by name.
- The tested export procedure, with a note of what the output looks like.
- What the greeting says about recording, on every path.
- What happens to records when somebody leaves.
- The date this was last reviewed.
The everyday uses, which are most of the value
Records get discussed as though their only purpose is a dispute. Most of what a firm gets from them is ordinary and immediate.
A client says they called on Tuesday and nobody rang back. Call detail settles it in thirty seconds, in either direction, and either way the firm knows something true rather than arguing from memory.
A message was taken and the details are wrong. The recording or the thread has what was actually said, which resolves the matter without anybody being blamed for mishearing.
A caller mentions a name, a date or a number and it was written down incorrectly. Being able to check is the difference between a correction and a second call to ask again.
And a new staff member is learning how the firm answers the phone. A handful of real calls, used with the person's knowledge and treated as a review of the process rather than of any individual, teaches faster than any amount of instruction.
None of those uses require a policy debate. They do require somebody at the firm knowing how to retrieve a record in under two minutes, which is the practical case for testing it while nothing is wrong.
Tell the firm's own people what is recorded
Whatever the firm decides about callers, it owes its own staff a plain statement of what the system captures.
Not as a warning, and not buried in a handbook nobody reads. One short paragraph during induction: calls on the firm's system are recorded, message threads persist, and configuration changes are logged. Said once, plainly, and it is done.
The reason to say it is that people behave normally when they know and awkwardly when they suspect. A staff member who has been told is not thinking about it three months later. A staff member who discovers it accidentally spends a week wondering what else they were not told.
It also removes a specific failure. Somebody who does not realize a mobile call runs through the firm's system may say something on a personal call they would not have said on a firm one, and the person most likely to make that mistake is the one nobody briefed.
Say it again when the arrangement changes. A firm that adds recording, changes retention, or starts using message threads should tell its people, in the same plain terms, at the time rather than afterward.
Talking to Cleod9
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a Mansfield firm works with someone in the same metro rather than a distant queue. The platform is described on the Cleod9 services page.
Bring the eight questions and ask for written answers, then test retrieval and export before the arrangement goes into daily use. What those answers mean for the firm's obligations is for the firm's own counsel to determine, and that determination is far easier from a page of specifics than from a general conversation about features.