The invisible part of your market
In much of the U.S., a meaningful share of the people who need a plumber, a lawyer, a dentist, or an agent are more comfortable in Spanish than English. You don't need a statistic to check this against your own business: look at who lives in your service area, who your best customers refer, who walks in. Now consider what happens when someone from that community calls and hits an English-only greeting or voicemail. They don't struggle through it — they hang up and call a business that answers in their language. The loss never appears in any report, because the call left no trace. That's what makes it the quietest leak on the line.
Why “press 2 for Spanish” fails
The traditional fix is a language menu, and it fails for the same reason phone trees fail generally: it makes a person in a hurry do work before anyone helps them. Worse, it often over-promises — the caller presses 2 and reaches an English-speaking desk anyway, or a translated recording with no human behind it. A menu is a label, not a capability. What the caller actually needs is simple: a voice that understands them, in their language, for the whole call — not a gate at the front of one.
What good bilingual answering looks like
Whether it's a bilingual hire, a bilingual service, or an AI receptionist, hold it to the same bar:
- No gate. The caller speaks, the answerer detects the language and responds in it. Nobody presses anything.
- The whole call, one language. No switching a nervous caller to English mid-conversation because the hard part came up.
- Real capability, not a script. The answerer can ask follow-ups and take a complete message in the caller's language — hours-and-location Spanish is not intake Spanish.
- The summary arrives in yours. The call happens in the caller's language; what lands in your inbox is written for you. This is how voice.aai.dev does it — the mechanics are in the languages doc.
Where it matters most
Every phone-first trade benefits, but three feel it acutely. immigration and legal intake, where the caller is often in crisis and often calling on behalf of family — language comfort isn't a nicety there, it's whether the call happens at all. Real estate, where buyers and sellers making the biggest transaction of their lives prefer to make it in the language they think in. And home services, where the household emergency doesn't check which language the dispatcher speaks. If your trade serves the public where you live, the question isn't whether bilingual callers exist — it's who answers them today.
Test your own line this week
Have a Spanish-speaking friend call your business cold — during lunch, then after hours — with a simple, real request. Listen to what they hit. If the honest answer is “a greeting they can't use,” you've found customers you didn't know you were turning away. Fixing it doesn't require rebuilding your staff: voice.aai.dev answers in natural English or Spanish (and more languages now), detects the caller's language on the call, and emails you the summary in yours. Call the line and try it in either language — then see how pricing works.