Richardson, TX

Cloud PBX Phone System for Richardson TX Medical Clinics

The phone menu is the part of a Richardson clinic's system that every patient encounters and almost nobody at the clinic has heard in years.

Book a Demo

It was recorded once, probably by whoever was available, listing options that made sense to the practice at the time. Since then a department has changed, an option leads somewhere that is no longer staffed, and the whole thing runs about forty seconds before a caller can do anything.

Cleod9 provides cloud communication for Dallas-Fort Worth businesses, and a clinic administers its own menus in a browser. This page is about designing one that works, and about how few options that actually requires.

Call the clinic's main number from a mobile phone and listen the whole way through without skipping. Time it.

Most clinics discover three things. It is longer than they thought. At least one option is wrong or leads somewhere unattended. And the option most callers want is not first.

Do it again at half past twelve and at six in the evening, since the menu may differ by time of day and the after-hours version is frequently the one nobody has checked.

Ten minutes, and it produces a specific list of problems rather than a general sense that the phones could be better.

The first eight seconds

A caller decides in the opening moments whether this call is going to work, and three things have to happen before anything else.

The clinic's name, so somebody who dialed wrong finds out immediately rather than after listening to five options.

The emergency instruction, telling anyone facing an emergency to hang up and dial 911. This comes before any option, every time, on every version of the menu including the after-hours one.

Then the first option. Nothing else belongs in that window: no explanation that options have changed, no request to listen carefully, no announcement about the website. Callers do not need the architecture and every second of it is spent before they have been given anything.

Four options, and put the biggest first

Menus fail by being long. A caller holds about three or four options in mind, and anything past that means they either press something at random or wait for a person.

Four is the practical ceiling for a clinic. For most practices those are scheduling, refills, billing, and clinical or everything else. Records requests and referrals can sit behind one of those rather than occupying their own place at the top.

Order them by volume rather than by the clinic's internal structure. Scheduling is usually the largest and belongs first, and putting it fourth costs every one of those callers fifteen seconds.

Where a clinic genuinely needs more than four, use a second level rather than a longer first list. Two short menus are easier than one long one, though a clinic that needs three levels has a routing problem rather than a menu problem.

Describe the caller, not the department

The most common menu mistake is labeling options by the clinic's own organization.

A caller does not know whether their question belongs to the front office or patient accounts. They know they have a question about a bill. An option that says billing questions works; one that names an internal team does not.

Say the action rather than the noun where possible. To make or change an appointment is clearer than scheduling, because it tells somebody who wants to cancel that they are in the right place.

Avoid words that mean something specific inside the clinic and something vague outside it. Every practice has two or three, and the front desk can name them because they field the confused calls.

Always let somebody reach a person

Every menu needs an obvious route to a human, and it should not be hidden at the end as an afterthought.

State it plainly, and honor it without further questions. A caller who has decided they need a person is not going to be routed usefully by a system, and trying to steer them further is what produces the frustration people associate with phone menus.

Handle the caller who presses nothing. Older patients on rotary-style habits, callers driving, and anybody using a phone where the keypad is inconvenient will simply wait. That should route to a person or to the clinic's overflow path rather than repeating the menu and disconnecting.

Handle a wrong entry the same way. One repeat, then a person.

What sits behind each option

A menu only helps if the destination behind each option answers, and this is where clinics most often let the design down.

Each option should ring a group rather than one extension, so two or three people have a chance rather than one. Four rings, about twenty-four seconds, before it moves on.

Then decide where it moves to. A second group, a mobile device, or the AI Voice Concierge, which answers, asks the questions the clinic defined, books where the clinic's rules allow, captures requests, and transfers to a person. Voicemail should rarely be the destination anybody chose.

The boundaries stay firm on every path. No assessment of symptoms, no advice about medications, no view on whether something can wait. 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 finished script. This page is operational guidance and not medical advice.

Test every destination by calling it. A path that rings out looks perfectly healthy on an administration screen, and rules that were correct in the spring routinely point at somebody who changed roles over the summer.

Recording it so it sounds like the clinic

The recording matters more than clinics expect, because it is the only impression a caller has of the practice before somebody answers.

Use a real voice from the clinic rather than a synthesized one, and use the same voice across every menu and greeting so the whole system sounds like one place.

Write it out and read it aloud before recording. Sentences that read well are frequently unsayable, and anything over about fifteen words loses the listener.

Record somewhere quiet, speak slightly slower than feels natural, and listen back on a mobile phone rather than a computer, since that is how it will be heard.

Keep the same wording pattern for every option so callers can predict the rhythm. Predictability is what lets somebody stop listening once they hear their option.

The versions clinics forget

A menu is not one recording. It is several, and the ones nobody checks are the ones that embarrass the clinic.

The after-hours version, which should say the clinic is closed, when it opens, the emergency instruction, and what somebody should do if they need help before then.

The lunch version, if the clinic closes over lunch, since a caller hearing the normal menu and reaching nobody concludes the practice is disorganized rather than at lunch.

The holiday version, which needs writing before each holiday rather than being remembered on the day.

The closure version, for the ice day or the power failure. Write it in advance, because composing one during an actual closure produces something vague, and vague generates the calls the message was meant to prevent.

Because the clinic administers this itself, switching between them takes minutes from anywhere. That is only useful if two or three people know how, which means walking through it once while nothing is wrong.

The 911 requirements behind all of it

Two federal rules apply to any multi-line telephone system, and both belong on the clinic's checklist.

Kari's Law requires that a person can dial 911 directly without first dialing a prefix to reach an outside line, and that the system notifies a central point on site when a 911 call is placed, so somebody at the front desk knows an emergency call came from a treatment room.

The RAY BAUM'S Act addresses dispatchable location, requiring information specific enough for responders to find the caller. For fixed devices in a multi-line system the relevant compliance date was January 6, 2021, and for non-fixed devices and certain other configurations it was January 6, 2022.

Ask Cleod9 how location is registered for each device and how it stays current when a phone moves between rooms, then verify at go-live rather than accepting the answer.

What to measure

Time from answer to the first option, which should be under ten seconds.
Selections by option, which tells the clinic whether the order matches actual demand.
Callers who pressed nothing, which is a real group and should route somewhere sensible.
Abandoned calls by hour, meaning calls that ended during the menu or before reaching anyone.
Transfers per call at the front desk, which measures how much the menu is misrouting.

Common questions

Do patients dislike menus?

They dislike long ones and ones that trap them. A short menu with an obvious route to a person is barely noticed.

Yes, and it should be written separately rather than being the daytime menu with a line added.

Can we change it ourselves?

Yes, in minutes, from anywhere. That is what makes closure messages and holiday hours practical.

How often should it be reviewed?

Listen to it quarterly and whenever a person or a service changes. Menus decay quietly and nobody at the clinic hears them.

When the answer is fewer options rather than better ones

Some clinics improve their menu and find the calls still land in the wrong place. That usually means the menu is doing work that belongs elsewhere.

A menu sorts callers who know what they want. It cannot help somebody who is not sure which category their question falls into, and a meaningful share of patients are in exactly that position. For them, more options is not more helpful; it is more chances to guess wrong.

So the alternative worth considering is a shorter menu with a person or a capture path early, rather than a longer one that tries to anticipate everything. Two options and a route to somebody who can sort it beats five options that three quarters of callers navigate incorrectly.

The same logic applies to known callers. Pharmacies, laboratories, imaging centers and referring practices call regularly and should not be navigating a menu written for patients. Routing those known numbers directly to the right person removes a category of traffic from the menu entirely, and it is a small piece of configuration.

And some options should not be on the menu because they should not be arriving by phone at all. Where a clinic finds a large share of callers selecting an option that always ends in a form or a callback, that is a signal that the underlying process, rather than the menu, is what needs attention.

Menus change rarely, so when one does the clinic should treat it as a small project rather than an edit.

Write the whole script out first, including the after-hours, lunch and holiday versions, and read them aloud together. Reading the set in sequence catches inconsistencies that are invisible one at a time, such as an option numbered differently on the after-hours version.

Have somebody outside the clinic call the test number and describe what they heard and where they ended up. Staff cannot hear their own menu the way a stranger does, and the feedback is nearly always about pace and wording rather than structure.

Tell the front desk what is changing before it goes live, and give them the option list. They will be asked about it, and they are also the first people to notice when callers start arriving in the wrong place.

Then check the numbers after two weeks. Selections by option tell the clinic whether the order matches real demand, and it is common to find that the option placed second is the one most people want. Reordering is a five-minute change.

Leave it alone after that. A menu benefits from stability, and patients who call regularly learn the pattern. Change it when something real changes, not because a quarter has passed.

What Cleod9 will put in writing

Practices evaluating a phone platform for a medical office reasonably ask what the vendor will commit to. Cleod9 has answered that directly.

Cleod9 will enter into a business associate agreement, through Wildix, the platform the service runs on. It covers voice, voicemail, video, call recording and transcription. Text messaging is not covered by it. Wildix has completed SOC 2 Type 1 and Type 2 audits, encrypts call and video media in transit using DTLS-SRTP, protects signaling and web traffic with TLS, and runs each customer on a dedicated instance in AWS.

That settles the vendor's side of the question, and it is worth having in writing before anything is configured rather than afterward.

It does not settle the practice's side. A signed agreement and an audited platform are necessary and not sufficient. Whether the practice as a whole meets its obligations depends on how it configures the system, who has access to what, what staff are trained to do and what gets documented. That determination belongs to the practice's own privacy officer or counsel, and this page is not a substitute for either.

Talking to Cleod9

Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a Richardson clinic deals with someone in the same metro rather than a distant queue. The platform is described on the Cleod9 services page.

Call your own number first and write down what you hear, including how long it takes. That page of notes is a better starting point than any feature discussion, and it is the part only the clinic can do.