Southlake, TX
Premium Cloud VoIP for Southlake TX Medical Practices
Medical practices change shape more often than they used to. A Southlake practice joins a larger group, absorbs a retiring physician's panel, opens a second location, or consolidates two offices into one.
Book a Demo
The clinical and business sides of that get planned carefully. The phones get handled in the last week, by whoever is available, and the result is a period of several months during which patients cannot reliably reach anybody.
This is avoidable, and most of the work is not technical. It is deciding, early, what patients will experience and then making the configuration match.
Cleod9 provides cloud communication for Dallas-Fort Worth businesses. This page is about the transition: what happens to numbers, extensions, message history and access, and what patients need to be told. It is operational guidance about communication and workflow. It does not address clinical matters, and questions about records, patient notification, and continuity of care belong with the practice and its own advisors.
The old number belongs to the patients
The instinct when two practices combine is to consolidate onto one number and retire the other. It is almost always the wrong move and it is expensive in a way nobody measures.
That number is in patients' phones, on the refrigerator, in a pharmacy's records, in other practices' referral files, in directory listings the practice does not control, and on paperwork in drawers. Turning it off does not consolidate anything. It removes a route people are still using and sends them to whoever is next in a search result.
Port it and keep it. It can ring wherever the practice decides, carry its own greeting, and be measured separately so the practice can see how much traffic it still carries. Two years of that data tells you when it can be retired. Guessing does not, and most practices that guess are wrong by a wide margin.
The porting itself needs the ordinary care: nothing gets canceled with the old provider until the new service is confirmed working, account details have to match the old records exactly, and the emergency address information for every location has to be correct before anyone relies on the line.
Build the inventory first
Every transition starts in the same place, and almost no practice can produce it on request: a complete list of the numbers involved.
Not just the main lines. The fax number that still receives things. The direct line the referring offices use. The number on an old sign or a vehicle. The scheduling line printed on appointment cards from three years ago. The number a departing physician's patients still have.
For each one: where it is published, what answers it today, and who at the practice would notice if it stopped working. That last column identifies the numbers nobody is watching, which are exactly the ones lost in a transition.
Tell patients before they discover it
Patients find out about a change in one of two ways. The practice tells them, or they call and something is different.
The second version generates calls, confusion, and a quiet number of patients who conclude their practice closed. It is entirely preventable with a short message and an updated greeting.
What patients need is narrow and factual:
- That the practice has changed, in one plain sentence, without the internal detail.
- That their existing number still reaches the practice, if it does.
- That appointments already booked still stand, or exactly what is happening to them.
- Where to go, if the address is changing, with enough detail to actually find it.
- Who they will see, if that is changing, or that it is not.
What the practice may say about a change in ownership, about records, and about a provider who is not continuing are questions for the practice and its own advisors, and the wording should be settled with them before anything is sent.
What patients hear when they call
The greeting is doing more work during a transition than at any other time, and it is the cheapest thing to change.
Most practices run a transitional greeting that identifies both names for a period, then simplifies. Decide how long that period is rather than letting it drift, and record it properly rather than from a phone in a hallway.
Keep the emergency instruction first. Whatever else the greeting says about the change, it opens by telling anyone with a medical emergency to hang up and dial 911, and that stays first throughout.
Check the whole tree from an outside phone after the change, pressing every option and following where it goes. Transitions are when menus most often point at destinations that no longer exist, and nobody inside the practice hears their own menu.
The extension collision
Two practices combining almost always find both were using extensions in the same range, both written on desks 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 then finished, or the combined practice adopts a scheme with room for everybody, which usually means renumbering everyone. The second is more work and it survives the next change.
Whichever is chosen, do it on a stated date, communicate it twice, and keep old extensions routing to the new ones for a defined period rather than switching them off. Announcing that the old numbers stop working in ninety days, and meaning it, works better than letting them linger forever.
Two front desks doing the same job differently
The technical side of a merger is easier than this. Two teams that have each answered the phone their own way for years now have to sound like one practice.
Write the standard down: how the practice answers, what it says about the change, what happens to each category of call, and who decides same-day requests. One page, agreed by both sides, used by everyone.
Then expect it to take a couple of months. The useful mechanism is listening together rather than issuing instructions. A short weekly review of a few calls, with both teams present, treated as a review of the process rather than of the people, does more than any amount of written procedure.
Access during the unsettled months
Transitions require more people to be able to change more things than usual, and that is where control is lost.
Give the transition its own access decisions rather than granting permanent administration to whoever is helping. A small number of people who can change anything, a larger group who can change only their own site, and individual logins for everybody rather than a shared account.
The shared account is the specific failure worth naming. It makes it impossible to establish who changed what, and the change log is the only thing that answers that question three months later when something is misrouted and nobody remembers.
Set a date to review access after the transition ends. Permissions granted for a project become permanent by default, and the review takes ten minutes.
Message history and call records
A practice that has been texting patients for two years has a body of message history, and a transition is when somebody should ask what happens to it.
Settle the factual questions with Cleod9 in writing before the change: how long history is retained, whether that is configurable, who can see it, how it is exported, and what happens to it if an account is closed or consolidated. The same questions apply to call recordings if the practice has them.
Then take those answers to whoever advises the practice on its obligations and let them decide what the practice must do. Nothing here makes claims about what any platform satisfies, and a transition is exactly when a practice should be asking rather than assuming.
The provider who is not continuing
When a change means a physician or other provider is not part of the new arrangement, their patients will call and ask about it, and the front desk will be asked first.
What the practice says about that is not an operational decision. It touches patient notification, records, and continuity of care, and it belongs with the practice and its own advisors, settled in writing before the change rather than improvised at the desk.
What is operational is making sure the front desk has that agreed wording, knows where to find it, and knows who to route the question to when the answer needs to come from somebody else. Staff without an answer will invent one, kindly and inconsistently.
Closing a location without abandoning it
Consolidation is where numbers get orphaned, because the office closing is the one nobody is monitoring.
A closed location's number should keep working and route somewhere sensible, with a greeting that says what happened and where the practice now is. Not a disconnection message, which sends patients to a search result.
Keep it longer than feels necessary. Patients and referring offices update their records slowly, and the cost of maintaining a number is trivial against the cost of a call that reaches nothing. Measure it and let the traffic decide when it can go.
Correct the rest of the trail at the same time: directory listings, the website, printed material, and the map listing showing an address the practice no longer occupies. The phone keeps working; the paper does not correct itself.
Common questions
How long should we keep the old practice's number?
Longer than instinct suggests, and let the traffic decide. Practices that measure usually find meaningful volume two years on, particularly from pharmacies and referring offices.
Should both locations sound the same to callers?
Generally no. A caller is contacting a specific office and a greeting that identifies it is more useful than a uniform group message. Consistency belongs in the administrative layer, not in what patients hear.
When should patients be told?
Before the change takes effect, with enough notice to absorb it, and again as it happens. The exact timing and wording should be settled with the practice's own advisors, since patient notification during an ownership or provider change is not purely a marketing decision.
What breaks most often?
A number nobody had on the list, and emergency address information never updated for a new or moved location. Both are prevented by the inventory and both are discovered at the worst possible moment otherwise.
The transition checklist
One page, worked in order:
- The number inventory, with the who would notice column filled in.
- What is standard across locations and what belongs to each site, decided in writing.
- The extension scheme, including whether anyone renumbers and on what date.
- Ports and provisioning, with service confirmed working before anything is canceled and emergency addresses verified for every location.
- Greetings recorded in advance, emergency instruction first, and the whole menu tested from an outside phone.
- The patient message, with wording agreed by the practice's own advisors.
- Transition access, individual logins, and a review date.
- Retention and export settled in writing for message history and recordings.
- A ninety-day review of traffic by number before retiring anything.
The staff who are deciding whether to stay
Transitions are usually planned as though the team is a constant, and the team is the part most likely to change.
Front desk and clinical support staff go through a merger or acquisition with very little information and a great deal of uncertainty, and some of them leave during exactly the months when the practice can least afford to lose them. The person who knows which pharmacy takes which fax, who the difficult callers are, and what the workaround is for the scheduling system is rarely the person anyone thinks to brief.
Two operational habits help. Tell staff about phone and system changes before patients hear them, so nobody at the desk is answering a question they did not know had an answer. And write down the local knowledge while the people holding it are still there: the referral contacts, the recurring workarounds, the standing arrangements with nearby offices.
That written record is worth the afternoon it takes. A practice that loses two front desk staff in the same quarter as a merger, with nothing written down, spends the following six months rediscovering things that were never hard, only unrecorded.
Put arrivals and departures on the same checklist as everything else, including access to the phone system and messaging. During a transition people join and leave more often than usual, and access that accumulates is access nobody decided to grant.
The questions to ask any provider, and Cleod9's answers
A practice comparing providers should ask the same short set of questions of each and keep the answers in writing. Cleod9 has answered them as follows.
Will you sign a business associate agreement? Yes, through Wildix, the platform the service runs on. Which services does it cover? Voice, voicemail, video, call recording and transcription. What is excluded? SMS text messaging. Where do recordings live and for how long? In the platform's AWS environment, for a period the practice selects, from one week up to ten years. What independent audits do you hold? SOC 2 Type 1 and Type 2. How is call audio protected in transit? DTLS-SRTP for media, with TLS for signaling and web traffic.
Those answers are the vendor's half of the arrangement. The other half is the practice's own configuration, access decisions, training and documentation, and whether all of that meets the practice's obligations is a matter for its own privacy officer or counsel rather than for any vendor to assert.
Talking to Cleod9
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a Southlake practice 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 turns a general conversation into specific questions about porting, per-site greetings and hours, emergency address records, access levels and change logging, retention and export of message history, and how quickly routing can be changed on a day when it has to be. The decisions about what patients are told stay with the practice and its advisors.