Richardson, TX
Patient Communication Texting for Richardson TX Healthcare Offices
Most of what a Richardson practice does with patient messaging is routine. Reminders go out, confirmations come back, the schedule fills. The program is judged on a normal Tuesday and it works fine on a normal Tuesday.
Book a Demo
The days that actually test it are the other kind. The morning a water line breaks. The February when the roads ice over and half the staff cannot get in. The afternoon the internet goes down and the phones with it. On those days the practice needs to reach fifty people in twenty minutes, and it will either have prepared for that or it will not.
Cleod9 provides cloud communication for Dallas-Fort Worth businesses, including business text messaging. This page is about the unplanned day: what to write in advance, who decides, in what order things happen, and how to find out whether any of it works before you need it. It is operational guidance about communication. It does not address clinical matters and nothing here is guidance about patient care.
Three different bad days
They get lumped together and they need different responses.
The practice cannot open. Weather, a building problem, an outage, or too many staff out at once. Patients need to be told not to come, and the message has to reach them before they leave home.
The practice is open and the patients cannot reach it. The phone service is down, the internet is out, or something upstream has failed. The practice is sitting there able to see patients while its callers hear nothing.
The practice is open and the patients cannot get there. Ice, flooding, a road closure. Nobody needs to be told the office is shut, because it is not, but a great many appointments are about to be missed and the practice would rather move them than lose them.
Write all three down. The responses overlap and the messages do not.
Write the messages before the morning you need them
Nobody composes well at six in the morning with a flooded hallway and a phone that will not stop. The messages should already exist.
Four or five cover it. We are closed today. We are closed and expect to reopen on a stated date. We are open, our phones are down, here is another way to reach us. We are open but conditions are difficult, and here is how to move your appointment.
Each one written once, reviewed once by whoever reviews patient-facing wording, stored where the person on duty can find it in under a minute, and used as written with only the specifics filled in. The point is not that the wording is brilliant. The point is that it exists.
Store them somewhere reachable from a phone. A document on the office network is useless on the day the office network is the problem.
One person decides
The most common failure on a bad morning is not technical. It is that four people are each waiting for somebody else to say the office is closed.
Name the person who makes that call, and name the backup. Write down what they are authorized to do without checking with anyone: close for the day, send the closure message, change the phone greeting, and cancel the schedule. A decision that requires a conference call at six thirty is a decision that happens at nine.
Give them the authority in advance and in writing. It takes one sentence and it is the difference between a coordinated morning and a scramble.
The order of operations
Once the decision is made, sequence matters, because patients check different things in different orders and the slowest channel should not be first.
Change the phone greeting. It is the thing most patients hit first and it reaches everyone, including the patients you have no mobile number for.
Message the patients scheduled for today, in one send.
Update wherever the practice's hours are published online, since that is where patients look after a busy signal.
Tell the staff, in whatever channel they actually read, including the ones not scheduled today.
Only then start on individual calls, prioritizing whoever the practice most needs to reach personally.
Doing this in the wrong order produces the classic bad morning: the practice spends forty minutes calling patients one at a time while the greeting still says the office opens at eight.
Message today, not everyone
A closure message should reach the patients affected by the closure and nobody else.
Sending it to the whole patient list is the single most common mistake here, and it is worse than it looks. It alarms people who had no appointment, generates a wave of inbound replies at the worst possible moment, and burns the practice's credibility for the next time it needs to send something urgent.
So confirm during setup that the practice can send to a defined group, how that group is defined, and who at the practice can do it. Then check that somebody other than one person knows how. The person who knows how is disproportionately likely to be the one who cannot get in.
What the closure message says
Short, and in a specific order.
Lead with the instruction: for a medical emergency, hang up and call 911 or go to an emergency room. That comes first regardless of what else the message says, because a closure message is exactly the moment a patient needs to hear it.
Then the fact: the office is closed today, or closed until a stated date. Then what happens to their appointment, which should be a plain statement rather than an implication. Then how to reach the practice if there is a way, and when the practice will be in touch if there is not.
Keep clinical content out entirely, keep it under a screen, and do not apologize at length. A patient in a car at seven forty needs the fact.
When the outage is the phone system itself
This one deserves specific preparation, because the tool the practice would normally use to communicate is the tool that is down.
Understand in advance what happens to inbound calls when the office loses internet or power. Cloud phone service generally continues to exist above the office, which means calls can be routed elsewhere even when nothing in the building is working, but the practice should confirm what the arrangement actually is rather than assume it.
Ask three concrete questions during setup. Where do calls go if the office connection drops, and can that be set up in advance to happen automatically. Can staff change routing and greetings from a phone, away from the building. And who at the practice can do those things, with at least two people knowing how.
Write the answers on the same page as the pre-written messages. On the day, nobody will remember and nobody will have time to find out.
Run it once, on a quiet afternoon
A plan nobody has tested is a document. Thirty minutes once a year turns it into something the practice can rely on.
Pick a slow afternoon. Have the designated person actually find the messages, actually change the greeting to a test version and back, and actually send a closure message to a small internal group. Time it. Then ask what was harder than expected.
What this reliably turns up is small and important: a password nobody has, a document saved somewhere unreachable, a step that requires a person who left, a greeting that takes fifteen minutes to change because nobody has done it before. Every one of those is trivial to fix in advance and expensive to discover at six in the morning.
The staff side of a closure
Patients get most of the attention and staff communication fails just as often.
Decide how staff are told, and use something they will see at that hour. Whatever channel the practice already uses for daily coordination is usually right, with a phone call to anyone who has not acknowledged within a stated time.
Include the people not scheduled that day. They will hear about it anyway, and they are frequently the ones who can help with rebooking from home.
The day after is the real work
A closure creates a rebooking problem roughly the size of a day, and it does not solve itself.
Decide in advance who owns it and how it is prioritized. Some appointments can simply be offered new times by message. Some need a call. Some should be slotted into whatever gaps the following week has before anyone is contacted, so the practice is offering rather than asking.
Practices that handle this well tend to have written the rebooking approach into the same page as everything else, because the morning of the closure is not when anyone will think it through.
Consent, watching, and registration
The ordinary messaging discipline still applies on an unusual day.
Closure notices go to patients who have agreed to be texted, and consent is a record: the date, the number, and the wording the patient was shown. Requests to stop are honored promptly and recorded where the next person will see them, including when written in a patient's own words rather than as a keyword. Federal rules on how consumers may revoke consent have been updated in recent years, and the current requirements are a question for the practice's own advisor.
Carrier registration matters more here than anywhere, because unregistered traffic is filtered rather than rejected, meaning the practice believes it reached fifty patients and reached none. Confirm registration and check delivery reporting while things are calm.
And expect replies. A closure message produces more inbound volume than anything else the practice sends, arriving during the hour it is least able to handle it. Decide who is watching, and keep the prepared response available: it leads with the instruction to call 911 or go to an emergency room for anything urgent, says the practice cannot handle clinical questions by message, and gives a number.
Common questions
How far in advance should we message about expected weather?
Only when the practice has actually decided something. A message saying the office may close tomorrow produces calls asking whether it will. Decide, then send.
Should the closure message offer a new appointment time?
Usually not in the first message, which needs to be short and clear. Offering times works better as a second message once the practice knows what its rebuilt schedule looks like.
What if only some providers are affected?
Then the message goes to those patients only, which is another argument for confirming that the practice can send to a defined group. A blanket message about a partial disruption creates more calls than it prevents.
Who should be able to change the phone greeting?
At least two people, and both should have done it at least once. This is the single most common gap found during a drill.
The page to keep
Everything above fits on one page, and that page is the deliverable:
- Who decides, who is the backup, and what they are authorized to do without asking.
- The four or five pre-written messages, stored somewhere reachable from a phone.
- The order of operations for the morning.
- How to change the greeting and how to reroute calls, with the names of the two people who can.
- How to send to a defined group of patients, and who can do it.
- The rebooking approach for the following days.
- The date the practice last ran through it.
The channel question, answered
Practices reasonably ask which channel is appropriate for what. The answer here is clearer than usual because the vendor side is settled.
Cleod9 will sign a business associate agreement by way of Wildix, the underlying platform, covering voice, voicemail, video, call recording and transcription. Text messaging is excluded from it.
Read that as a routing rule rather than a restriction. The call, the video visit and the voicemail are the places for a conversation with any clinical content in it. The text thread is for the appointment around that conversation.
Handled that way, texting does what practices actually want from it, which is fewer missed appointments and fewer phone calls asking what time something is, without the practice having to think hard about any individual message. What the practice is required to do in its own situation remains a question for its privacy officer or counsel.
Talking to Cleod9
Cleod9 is a Dallas-Fort Worth provider supporting its own customers, so a Richardson practice works with someone in the same metro rather than a distant queue. The platform is described on the Cleod9 services page.
The concrete questions are about the bad day rather than the normal one: what happens to inbound calls when the office loses connectivity, whether failover routing can be arranged in advance, whether staff can change greetings and routing remotely, whether messages can go to a defined group, and how delivery is confirmed. Bring the one-page plan and check it against the answers.