El Paso dentists: reminders that arrive in the wrong language
The front desk switches languages all day in El Paso. The reminder system does not. Here is the small daily cost, the free fix, and where it stops holding.
Show contents
Ask every patient which language they want for written messages, write it on the chart, and send the reminder in that language. Then work the recall list by hand, one name at a time, in the language on the file. That fills chairs this month. The hard part is keeping the list from growing faster than anyone can call it.
It is 8:40 on a Tuesday at a practice on the Eastside of El Paso, Texas, and the front desk has already switched languages four times. A call in Spanish about a crown that came loose over the weekend. A walk-in asking in English about a cleaning. A text thread about moving Thursday's appointment. The reminders that went out at 6 p.m. last night were English only.
Three small things went wrong.
The first was a confirmation. The message asked the patient to reply C. She replied "Sí," the system logged no answer, and the front desk read silence as a maybe.
The second was a no-show that was really a misunderstanding. The patient texted back in Spanish that she could not come. The reply matched no keyword and sat unread until the chair was empty.
The third was a recall that never went out. The hygienist marked six months, the template only existed in English, and the patient ignored a message she could not read.
None of this is a translation problem. The front desk speaks both languages all day and does it well. The reminder system was built once, in one language, and nobody wrote down what each patient wants.
What a wrong-language reminder costs a dental practice
An empty chair at 9:20 is not one lost cleaning. It is the cleaning, the exam, whatever the dentist would have found, and the patient's next two years of hygiene.
Start with your own numbers. Your practice management report counts no-shows and late cancels by provider, and it knows what a hygiene hour produces. Multiply the two and you have the monthly cost of empty chairs before you count the treatment that never got diagnosed.
The language piece is harder to see. Ask the front desk how many patients prefer Spanish and you will get a number from memory. Ask how many charts record it in a field and you will get a shrug. One of those is evidence. The other is a feeling.
A language preference that lives in a scheduler's memory disappears at 5 p.m., on the day she takes vacation, and on the Saturday the temp covers the desk. Write it where the next person looks, or it does not exist.
Why it happens here
- The front desk is bilingual. The templates are not. The reminders were written by whoever set the system up, and the Spanish version became a project nobody owned.
- The preference lives in a person's head. The desk knows that Mrs. Reyes prefers Spanish. Nobody wrote it down, so the newest hire does not know.
- The chart has no field for it. Clinical notes, insurance, recall date, and no line that says which language to use for a text.
- The system shipped in English. Reminder tools arrive with English defaults.
- Recall is manual and monthly. It happens when someone has an hour, which is rarely the week it needs to happen.
- Families share phones. A daughter books for her mother, the mother reads the reminder, and the language that matters is the one on the lock screen.
There is also the borderland habit of switching mid-sentence in El Paso, which makes the gap easy to miss. A patient who answers in English at the desk may read Spanish more comfortably on a phone at 9 p.m.
The manual fix
Six steps, one afternoon, no software.
-
Ask at intake, in both languages, and write the answer on the chart.
"Would you like reminders in English or Spanish?" and "¿Prefiere los recordatorios en inglés o en español?" Use the same field every time.
-
Read the confirmation back in that language.
Date, time, provider, what to bring. Have the patient repeat the day before you hang up.
-
Keep a bilingual script at the desk.
Two cards, or one page in the binder, so the newest hire reads the same words as the office manager.
-
Print the recall list monthly and work it by hand.
Sort it by language, call in that language, write down what happened.
-
Leave a note for the next person.
"Prefiere español," the date, and who asked, where the next scheduler will look.
- Ask for the review in the language of the visit.
| Moment | English | Spanish |
|---|---|---|
| Confirmation, three days out | "[Practice]: you have an appointment on Thursday at 9:20. Reply C to confirm or R to reschedule." | "[Consultorio]: tiene una cita el jueves a las 9:20. Responda C para confirmar o R para reprogramar." |
| Day before, no reply yet | "[Practice]: we have you down for tomorrow at 9:20. Reply C to confirm." | "[Consultorio]: le tenemos mañana a las 9:20. Responda C para confirmar." |
| Rescheduled | "Moved. You are now on Tuesday the 14th at 3:40. Does that work?" | "Listo. Quedó el martes 14 a las 3:40. ¿Le sirve?" |
| Overdue recall | "[Practice]: it is time for your next visit. Reply C and we will find a time this month." | "[Consultorio]: ya es tiempo de su próxima visita. Responda C y le buscamos una hora este mes." |
Neither column names a procedure. "Su cita" protects a patient whose phone sits face up on a kitchen table, and the English column has the same obligation.
HIPAA does not change with the language on the screen. A Spanish reminder may contain what an English one may: no diagnosis, no treatment name, no balance, no result. Writing the message twice does not create a second set of rules.
Where the manual version breaks
The manual version works while one person holds it together, and that is the whole problem.
- Nobody reads the note. A new hire, a temp on Saturday, a hygienist covering lunch. The note is in the file and the reminder goes out in English.
- The list grows. Recall is a monthly job, December is when it stops happening, and February is when the backlog becomes a number nobody says out loud.
- The script becomes one person's copy. It lives in a drawer, gets edited by whoever is at the desk, and drifts from the version patients actually understand.
- Confirmations still need an English keyword. "Sí" matches nothing, so the answer sits in the inbox looking like silence.
- Nobody can count it. Without a record of how many Spanish-preference patients were recalled or confirmed, the practice cannot tell a working process from a full drawer.
The honest threshold: it holds while the office has slack, and there is no slack on the Monday after a holiday weekend.
What a system does differently
The alternative is to make the language part of the record instead of part of someone's memory, and this is where the software question arrives.
The mechanism is the same one behind every reminder. An appointment is booked, a workflow starts, and before each message it reads a language field on the contact. If the field says Spanish, the Spanish variant goes out. If it is blank, the bilingual version goes out once and the reply decides. The answer lands in a shared inbox, on the same record as the appointment, so the next person sees the language before they dial.
That is what we use GoHighLevel for. The reason to name it is not the text message, which plenty of tools send, but that the field, the two branches and the trigger live together, so nobody maintains two sequences that drift apart.
What it still cannot do: it does not read a Spanish reply for you, and it does not put the preference on the chart unless someone asks the patient and fills the field. It is not a translation service, and it will not fix a schedule that double-books. If the front desk is overwhelmed, reminders reduce the phone calls, not the workload behind them.
Two branches are not two campaigns. The trigger, the timing and the stop condition are shared, and only the copy changes. The day a practice builds a separate Spanish sequence is the day it starts drifting out of sync and dies when the person who built it leaves.
The same system, assembled and running in a week.
Most of what is described in this story can be done by hand until it cannot. When that happens, this is the stack we use, what it costs, and where it stops.
What it costs
The entry plan runs $97 a month and covers one practice. The $297 tier is for groups running several locations. A HIPAA configuration costs extra, so ask what it covers before you budget, and confirm current pricing before you commit.
Usage is the rest. SMS runs about a cent per segment, and a confirmation thread is usually four to ten segments. A2P 10DLC registration carries small one-time and monthly fees. A single practice usually lands between $110 and $180 a month all in before the HIPAA configuration.
Compare that with one empty hygiene chair, or one crown that walked away because the recall never arrived. The chair is the expensive part.
A business associate agreement is required before protected health information touches a vendor, including the reminder platform and the SMS provider. Confirm in writing that the vendor will sign one, and read the HHS privacy guidance before you send anything. The platform is not an EHR: no chart notes, treatment plans, imaging or billing ledger. The clinical record stays in your practice management system.
What to measure
Five numbers, checked monthly, tell you whether the language work is real.
- Charts with a language recorded, against new patients. It makes the others possible.
- Confirmed versus scheduled, split by language. A gap here is the first sign that the Spanish branch is not landing.
- No-shows and late cancels, split by language. Watch the Spanish column, and watch whether it improves after the field exists.
- Recall sent versus recall booked. Recall is the cheapest production in the practice and the easiest to leave on a template nobody checks.
- Replies that matched no keyword. A rising count usually means patients are answering in the other language.
If confirmations are fine but no-shows are not, the reminder is arriving and the patient still is not coming, which is a scheduling problem rather than a language one.
Why this matters in El Paso
About four in five El Paso residents are Hispanic or Latino, according to the U.S. Census Bureau, and switching languages inside one conversation is ordinary here. A practice that sends English reminders to a Spanish-reading household is not rude. It is quiet in a way nobody reports, which is why the empty chair shows up as a no-show instead of a complaint.
El Paso, Texas is also a rotation market. Fort Bliss moves families through the post every year, and the Eastside and Horizon keep adding households choosing a dentist for the first time here. Those patients have no habit to fall back on. They book whoever confirms in a way they understand.
The border runs through daily life here and does not need a number attached to it. Some patients read Spanish, some read English, many read both, and the only honest way to know is to ask once and put it where the next scheduler will find it. Start with the El Paso edition, read the follow-up section, and compare it with dental reminders in Boise, where the language question does not come up.
The front desk already switches languages ten times before lunch. The reminder should not need a person to remember.
Can we just translate the English reminders and be done?
You can, and patients will notice. Machine translation tends to produce stiff, formal Spanish that reads like a government form, which undercuts a two-line text message. Have someone fluent review both versions, and keep them the same length and tone.
What if a patient never answers the language question?
Send the bilingual version once, then record what the reply tells you. Do not default to either language. A bilingual message costs a segment more and lets the patient choose, which is worth more than the penny it costs. That is a better trade than guessing.
Do reminders to +52 numbers work the same way?
Not reliably. A U.S. A2P 10DLC campaign covers U.S. traffic, and Mexican carriers sit outside it, so test delivery before you promise a patient that reminders will arrive. Where they fail, the front desk should call, and the workflow should create that task.
Does asking about language slow down intake?
It adds one question and a few seconds. The alternative is a reminder the patient ignores, an empty chair, or Spanish sent to a household that wanted English. Once the question is on the form, nobody thinks about it again.
Do we need a bilingual staff member to run this?
No, but you need someone who can write the Spanish copy and someone who can read a Spanish reply during business hours. The workflow routes and the person handles the conversation. If nobody on shift can read it, the Spanish branch should promise a callback at a stated time.