The Colony, TX
Cloud PBX Phone System for The Colony TX Medical Clinics
A clinic in The Colony that moves to a new phone system usually switches everything on at once, because it is all available and there is no obvious reason to wait.
Book a Demo
Three months later the same clinic cannot say which change helped. Something improved, several things are configured in ways nobody chose, and when a patient complains there are four places to look.
Cleod9 provides cloud communication for Dallas-Fort Worth businesses, and everything below is configured by the practice in a browser. This page is about the order to do it in, which is the difference between a system the clinic understands and one it inherited from itself.
Before anything: two weeks of counting
Nothing here works without a baseline, and a clinic that changes first is left comparing against an impression.
Count four things for two ordinary weeks. Call volume by hour. Abandoned calls, meaning calls that ended before reaching anyone, also by hour. What people are calling about, tallied at the front desk into five or six categories. And how long captured messages waited before somebody acted on them.
The abandoned figure is the one most clinics have never seen, and it is usually the number that decides where to start. A call that rings during the opening rush and hangs up leaves no trace at all.
The category tally is the other half. Most clinics find three or four questions account for the bulk of their calls, and the top one is frequently not what anybody predicted.
Weeks one to three: get the basics right
Before adding anything, fix what already exists. This phase changes nothing patients would name and it improves what they experience.
Ring groups rather than individual extensions on every inbound path, so two or three people have a chance to answer rather than one.
A ring threshold of four, about twenty-four seconds, so calls move on rather than ringing into nothing. The instinct is to set this higher and it spends the caller's patience to protect the staff's opportunity.
A destination for every path that is not voicemail. Where a call is not answered it should reach a second group or a mobile device.
Explicit rules for lunch, evenings, weekends and holidays rather than inheriting the daytime rule by accident.
And the 911 items, which are not optional. Kari's Law requires that a person can dial 911 directly without first dialing a prefix, and that the system notifies a central point on site when a 911 call is placed. The RAY BAUM'S Act addresses dispatchable location, requiring information specific enough for responders to find the caller; the relevant compliance date was January 6, 2021 for fixed devices in a multi-line system and January 6, 2022 for non-fixed devices and certain other configurations. Confirm how location is registered for each device and verify it rather than accepting the answer.
Weeks four to six: cover one hole
Pick the single worst window from the baseline and address only that.
For most clinics it is the opening hour or the lunch period, where abandoned calls concentrate. Overflow coverage during that window is the change, and the AI Voice Concierge is the destination: it answers, asks the questions the clinic defined, books where the clinic's rules allow, captures requests, and transfers to a person.
The boundaries are set before it goes live and configured as prohibitions. No assessment of symptoms, no advice about medications, no view on whether something can wait, no sorting by severity. The greeting tells anyone facing an emergency to hang up and dial 911 before any other question. Where urgency is needed for scheduling, ask how soon the patient feels they need to be seen and route on their answer. Have a clinician review the script line by line. This page is operational guidance and not medical advice.
Decide where captured requests land, who owns them by role, at least two clearing times a day, and what happens when that person is out. A well-captured request sitting unread until Wednesday has helped nobody.
Then read the first fortnight of transcripts. Not to check the technology, which is obvious either way, but to check the questions. Patients pausing at the same question means the wording is wrong; patients answering something adjacent means it is ambiguous. Both are ten-minute fixes.
Weeks seven to nine: move one category off the front line
Return to the category tally and take the largest low-urgency item, which in most clinics is refills or billing.
Give it a dedicated path that captures what the clinic needs and delivers it to whoever handles that work at set times. For refills that is the medication, the pharmacy, the identifiers the clinic requires, and whether the patient is out or nearly out. The path collects and hands off; anything beyond collection is a transfer.
This is the change that most reduces front desk load, because the volume is high and none of those calls ever needed the front desk.
Measure it against the baseline. Volume on that path, share handled without a person, and whether the abandoned figure in the busy windows moved. If it did not, the path is capturing rather than resolving and the questions need work.
Weeks ten to twelve: close the loop outward
Only once inbound is working is it worth adding anything that reaches out to patients.
Appointment confirmations and reminders are the obvious first use. Send the confirmation within minutes of booking rather than the next morning, and the reminder one to two days ahead rather than the morning of, so a cancellation is a slot the clinic can still fill.
Business texting is available on the platform, and consent governs. Ask at booking and registration in plain words, record the answer, the number and the date, and keep appointment messaging separate from anything promotional. A patient may revoke by any reasonable method and it must be honored promptly, which is why a person reads the reply queue rather than relying on a keyword filter.
Keep the content conservative: clinic name, date, day of the week, time, and what to do next. No procedure names, no specialty, no reason for the visit. A message arrives on a device that may be shared or unlocked.
Ask Cleod9 how number registration is handled, since business messaging over standard ten-digit numbers runs through carrier registration and unregistered traffic is more likely to be filtered. Check the delivery rate before concluding anything about patient response.
Why the order matters
Each phase depends on the one before it, which is the argument against doing them together.
Overflow coverage added before the ring rules are sensible will catch calls that should have been answered by a person, which makes the clinic look worse rather than better.
A category path added before there is somewhere for captured requests to land produces a queue nobody works, and staff conclude the whole thing is unreliable.
Outbound messaging added before inbound is handled produces replies the clinic cannot answer, which teaches patients that the channel does not work.
And every phase added at once means no phase can be evaluated. A clinic that changes one thing per fortnight always knows what caused what.
Bringing the front desk with you
The staff decide in the first fortnight whether this is help or a threat, and that judgment forms before anybody looks at a number.
Involve them in the baseline. They are the ones marking the tally, and the exercise itself makes the case better than any explanation, because they can see the volume they have been absorbing.
Ask them which fifteen minutes are worst and which question the current greeting gets wrong. That knowledge exists nowhere else and a design built without it needs rewriting after the first week.
Be honest about the purpose. Covering the hours nobody can staff is an easy case to make. Automation quietly used to justify not filling a vacancy will be recognized as exactly that.
Teach 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.
What to check at each phase
Abandoned calls by hour, compared against the baseline. This is the headline measure and the one that justifies the project.
Volume by category, which shows whether the dedicated paths are taking the traffic they were built for.
Share of calls on each path handled without a person, which distinguishes a path that resolves from one that only captures.
Time from capture to action, split between new patients and routine requests.
Transfers back to a person, and whether those transfers were answered.
Read all of these by hour rather than as weekly totals. Phone problems concentrate in specific windows and an average conceals exactly the hour that needs attention.
Common questions
Can we do this faster?
Yes, and the cost is that the clinic will not know which change produced which result. Twelve weeks is not the technical timeline; it is the evaluation timeline.
What if a phase does not help?
That is a useful finding and it is only available because the phases were separated. Adjust or reverse it before moving on.
Who should own the project?
One named role, usually whoever already owns the clinic's hours and staff announcements, since those are the changes that keep the configuration current afterward.
Do we keep our numbers?
Yes. Number portability is a federal requirement. Keep the old service active until the port completes and test before closing anything.
What to leave until after ninety days
A phased plan is as much about what is deliberately postponed as about what is done, and several capabilities are worth having later rather than sooner.
Video visits. Whatever a clinic decides about them, they are a clinical workflow change rather than a phone change, and running them alongside a phone migration means two unfamiliar things at once for the same staff.
Internal team messaging. Genuinely useful, and it needs its own conventions about urgency levels and handoffs before it is switched on. A clinic that adds it during a phone project gets an unstructured channel that fills with things belonging in the patient record.
A second location or a major routing redesign. Both are easier once the clinic knows how the basic arrangement behaves in practice.
Any integration work. Cleod9 integrates with Salesforce, HubSpot and Zoho; if the clinic runs on a practice management system, ask for that integration to be confirmed explicitly in a live configuration. Worth scoping early and implementing once the paths that would feed it are settled, since integrating a workflow that is still changing means doing it twice.
Call recording is the exception that cannot be postponed, because it runs automatically. Settle the handling questions during setup rather than later: where recordings and transcripts are stored, the default retention period, whether the clinic can set its own, whether specific records can be deleted on request, and who can access them through the access control list. A clinic subject to health information rules should have its own compliance advisor review both the vendor's answers and what the clinic allows its call paths to collect.
The ninety-day review
At the end of the three phases, spend an hour looking at what actually changed rather than assuming it worked.
Put the baseline numbers next to the current ones, by hour. Abandoned calls is the headline. If it has fallen in the windows the clinic targeted and not elsewhere, the changes did what they were meant to and the untouched windows are the next project.
Re-run the front desk category tally for one week. If the top category has moved down the list, the dedicated path is working. If it has not, the path is either not being reached or not resolving anything, and the transcripts will say which.
Ask the staff two questions: what is better, and what is still annoying. The second answer is the more useful one and it is usually specific enough to fix in an afternoon.
Call the clinic's own number four times in a day, at opening, midday, late afternoon and in the evening, and write down what happened each time. Ten minutes, and it is the only way to hear what patients hear.
Then decide the next single change rather than a list of them. A clinic that keeps making one deliberate change per quarter ends up, after a year, with a system that fits how it actually works, which is not something any initial configuration achieves on its own.
The vendor agreement, and where it stops
One question comes up on every medical implementation, so it is worth answering plainly rather than leaving it to a later conversation.
Cleod9 will sign a business associate agreement through Wildix, the platform behind the service. The agreement reaches voice, voicemail, video, recording and transcription. It does not reach SMS text messaging, which sits outside it. On the platform side, Wildix holds SOC 2 Type 1 and Type 2 audit reports and encrypts call media with DTLS-SRTP, with TLS protecting signaling and web traffic.
Where it stops is worth understanding as clearly as what it covers. The agreement governs how the vendor handles information the practice puts into the platform. It says nothing about whether the practice recorded a call it should not have, left playback open to the whole office, or discussed a patient on speaker at the front desk.
Those are the practice's decisions, and what the practice is required to do about them is a question for its own privacy officer or counsel.
Talking to Cleod9
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a clinic in The Colony deals with someone in the same metro rather than a distant queue. The platform is described on the Cleod9 services page.
Start the two-week count before the conversation rather than after it. Arriving with abandoned calls by hour and a category tally turns a product discussion into a plan, and those two sheets are the part only the clinic can produce.