Southlake, TX
Premium Cloud VoIP for Southlake TX Law Offices
Firms evaluate phone service on features. Call routing, messaging, video, recording, the mobile app. Those matter, and they are also the part that any serious provider can demonstrate in twenty minutes.
Book a Demo
The question that actually separates one arrangement from another is what happens on the morning something is broken. Who a Southlake firm calls, how quickly a person answers, what that person can do, and where calls go in the meantime. Almost nobody asks those questions during a sales conversation, and every firm eventually needs the answers.
Cleod9 provides cloud communication for Dallas-Fort Worth businesses. This page is about the failure case: how to find out about a problem, what to have documented in advance, what to ask before signing anything, and how a firm keeps working while something is being fixed. It is operational guidance, not legal advice, and anything touching the firm's professional obligations belongs with its own counsel.
Failures are not all the same shape
Three kinds, and a firm's response differs for each:
A clear outage. Nothing works, everyone knows immediately, and the only questions are how long and where calls go in the meantime.
Degradation. Calls connect and are unusable. One-way audio, dropouts, a delay that makes conversation impossible. This is worse than an outage in one specific way: nobody is certain there is a problem, so it goes unreported for hours while clients form an impression.
A single feature failing while everything else works. Messages not delivering, recordings not saving, voicemail not arriving. These are the quietest and often the longest-running, because the firm does not notice until somebody looks for something that should be there.
A firm that only plans for the first kind will handle the other two badly, and the other two are more common.
How will you find out?
Most firms discover a problem when a client mentions it, which means the problem has already cost something.
Two cheap habits close most of that gap. Somebody calls the firm's main number from an outside phone each morning and listens to it ring through, which takes fifteen seconds and catches a surprising range of failures. And staff are told that reporting a call quality problem is expected rather than a complaint, with somewhere obvious to report it, so that four people noticing the same thing produces one report rather than four silences.
Then ask the provider what notifications exist. Whether there is a status page, whether the firm is told about planned maintenance and how far ahead, and whether anyone would contact the firm proactively during an incident. Those answers vary considerably between providers and they are worth knowing before rather than after.
The escalation path, written down
On the morning something breaks, nobody should be searching an inbox for a support address.
One page, printed and also saved somewhere reachable from a phone, containing: the number to call for support and the hours it is answered, the account identifier the provider will ask for, the name of anyone the firm already deals with, and what to do if the first attempt does not get a response within a stated time.
Include the firm's own account details, because a person calling in a crisis will be asked to identify the account and will not have it. And include the two people at the firm who are authorized to request changes, since a provider that will make changes on any caller's say-so has a different problem.
This page is worth building on the day service is installed, when everyone has the information in front of them, rather than assembled later from memory.
What to ask about support before signing
Features get demonstrated. Support gets described in general terms, and general terms are worth very little.
Ask specifically. What hours is support answered by a person. What is the target response time for an outage, and for something less urgent. Is the first person a firm reaches able to look at the account, or are they taking a message. What is the path to somebody more senior and how is it triggered. Is anybody local, and does that change anything.
Ask for the answers in writing. Not because a firm expects to enforce them, but because a provider willing to write down its support commitments has usually thought about them, and one that will not has told you something useful.
The size and locality of a provider matters here in a way it does not for features. A firm that deals with a provider in the same metro is generally talking to somebody who can be reached and who knows the account, rather than entering a queue.
Where calls go when the provider is the problem
This is the arrangement that has to exist before it is needed, and it is the single most valuable thing on this page.
Cloud phone service generally lives above the firm's office, which means calls can often be routed elsewhere even when the building is dark. The important question is what the firm's specific arrangement is, and it should be established as a fact rather than assumed.
Three things to settle during setup. Where inbound calls go if the office loses connectivity, and whether that can be configured in advance to happen automatically. Whether staff can change routing and greetings from outside the building, from a phone. And who at the firm can do it, with at least two people who have actually done it once.
Write the answers on the same page as the escalation path. Nobody will remember on the day, and nobody will have time to work it out.
The failure that is not the provider's
A meaningful share of what firms report as provider problems are the firm's own building. The office internet connection, the power, a network device nobody owns, a wireless network that was fine until the office next door installed something.
This matters practically, because a firm that reports everything to the provider will spend the first thirty minutes of every incident establishing whose problem it is.
Know two things in advance: who to call about the office internet connection, with an account number, and whether the office network equipment is the firm's responsibility or somebody else's. A firm in shared premises frequently discovers mid-incident that the answer is neither.
What clients and counsel are told
A firm whose phones are down needs to say something, and improvising it is where the reputational cost accumulates.
Write two short messages in advance. One for clients: the firm is reachable at an alternative number or by email, and the phones are being restored. One for the courts, opposing counsel, and other professionals, which is the group most likely to be trying to reach the firm about something time-bound and least likely to try twice.
Then decide how those messages get out when the usual channels are the problem. Email and text messaging usually survive a phone outage, and a short note to the firm's active matters and its regular professional contacts costs very little.
Nothing about a service problem changes what the firm owes anyone. Anything with a date attached is the firm's own responsibility to manage and, where there is any question, a matter for its own counsel rather than something to be resolved by the fact that a vendor had an outage.
Keep working while it is being fixed
The point of the preparation is that the firm does not stop.
Mobile devices running the firm's system continue to place and receive calls from the firm's numbers over any working internet connection, which for most incidents means the office being unreachable does not mean the firm is. That is worth confirming as a fact about the firm's setup rather than assuming.
For the case where nothing works, have the low-technology fallback: the alternative number staff will use, and the list of the numbers everybody actually needs. A printed page in a drawer feels absurd until the morning it is the only thing that works.
Afterward, ask what happened
When service is restored, most firms move on. Asking for an account of the incident is worth ten minutes.
What happened, what the cause was, how long it lasted, and what is being done so it does not recur. A provider that answers those questions plainly is one a firm can rely on. A provider that does not is telling you how the next incident will go.
Keep the answers. Three incidents with a common cause is a conversation worth having, and no firm has that conversation without the notes.
What the contract says about all this
The commercial side belongs to the firm's own counsel, and there are a few things worth putting in front of them.
What the provider commits to on availability and support response, if anything, and what happens when it is not met. What notice either side gives to end the arrangement. What happens to the firm's numbers if it leaves, which is the term that matters most and the one least often read. And how the firm gets its data out, including call records and message history.
That last pair is the practical definition of whether a firm is locked in. Numbers a firm can port and records a firm can export mean the arrangement continues because it works, which is the only durable reason for it to continue.
Common questions
How much outage should a firm expect?
Ask the provider what its recent record actually is rather than what it promises. A provider that will discuss specific past incidents is more informative than one that quotes a percentage.
Is a second provider worth having as a backup?
For most firms of this size, no. The cost and complexity are real and the benefit is largely covered by mobile devices and a documented failover. Firms with unusual exposure should raise it with their own advisors.
Who at the firm should own this?
One named person, with a backup, and neither of them the busiest attorney. The role is small: maintain the one page, run the morning check, keep the incident notes, and be the point of contact.
Does any of this change with a local provider?
The questions do not, but the answers frequently do. Reaching a person who knows the account is easier when that person is in the same metro, and it matters most on exactly the day everything else is going wrong.
The one page to keep
All of it fits on a single sheet, printed and also saved where a phone can reach it:
- Support number, hours it is answered, and the account identifier.
- The named contact at the provider, if there is one.
- The escalation step if the first call gets no response within a stated time.
- Who to call about the office internet connection, with the account number.
- How to reroute calls and change greetings from outside the building, and the two people who can.
- The two pre-written notices, for clients and for professional contacts.
- The alternative number staff will use, and the numbers everyone needs.
- The date this page was last checked.
Describe the problem in a way that gets it fixed
Support conversations go badly for a mundane reason: the firm reports a feeling and the provider needs facts, so the first twenty minutes are spent extracting them.
Tell staff what to note when something goes wrong, and keep the list to five items. What time it happened, to the minute if possible. Which number was involved, on both ends where known. Which device and where the person was sitting. What actually happened, described physically rather than interpreted, such as the caller could hear me and I could not hear them. And whether it happened once or repeatedly.
That is the difference between the phones are acting up, which starts an investigation, and at 9:14 this morning a call to the main line rang four times and dropped, on the desk phone in the front office, and it has happened three times since Monday, which frequently produces an answer in one call.
Give them somewhere to put it. A shared note, a channel, a form on the wall by the front desk. Anything that collects the reports in one place, because the same problem reported by four people at four moments looks like four small annoyances and reads as one clear pattern the moment they sit together.
Then have one person carry it to the provider. A firm where four people call support separately about the same issue gets four partial investigations and no resolution, and everyone involved concludes the provider is unresponsive.
Talking to Cleod9
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a Southlake firm works with someone in the same metro rather than a distant queue. The platform is described on the Cleod9 services page.
The conversation worth having is the one about the bad morning: support hours and response, who answers, failover routing arranged in advance, remote changes to greetings and routing, notification during incidents, and how numbers and records come out if the firm ever leaves. Build the one page from those answers on the day service starts, and check it once a year.