Language routing · tested · priced
Bilingual Answering Service: Routing, Cost and How to Test It
A bilingual answering service answers your line in more than one language, either by routing to a speaker of that language or by switching the greeting and prompts. What matters is which languages are live on your line today, how a caller reaches them, and what the language support adds to the published price.
A bilingual answering service answers your business line in more than one language, either by routing to a speaker of that language or by switching the automated greeting and prompts. What matters is which languages are live on your line, how a caller reaches them, and what it costs — not how long the vendor’s language list is.
This page covers the three routing patterns, how to test one honestly, what the published prices show, and what to do if most of your after-hours callers speak a language your team does not. If you have not settled the human-versus-AI question yet, start with the AI vs human comparison; language support is a feature, not a strategy.
The three routing patterns
| Pattern | How it works | Trade-off |
|---|---|---|
| Menu digit | Greeting offers “press 2 for Spanish” | Simple and reliable; costs one menu level and some callers hang up at menus |
| Language detection | The system infers the language from what the caller says and switches | No menu, but detection fails on short or mixed-language openings |
| Dedicated line | A separate number staffed in that language | Best experience, worst logistics: a second number to publish and track |
For an after-hours line, the menu digit is usually the right starting point. It costs one prompt, it is transparent to the caller, and it fails in a way you can measure — you can count how many people press 2 and how many hang up at the menu. Detection sounds cleverer and often is, until a caller opens with “hi, uh, buenas noches” and the system picks wrong.
What a bilingual greeting sounds like
The greeting is where most implementations lose people. Long bilingual greetings read as a phone tree and callers hang up. Short ones work better, and the pattern that holds up is: identify the business, state that the line is answered after hours, offer the language choice once, and let tone do the rest.
“Thanks for calling Northside Plumbing. We’re closed right now, but this line is answered 24 hours. Para español, oprima el dos. Otherwise, stay on the line and tell me what’s happening.”
Note what it does not do: it does not repeat the entire message twice. Repetition doubles the time before anyone can speak, and callers in an emergency do not want a paragraph. Repeat the choice, not the message. The script and greeting page has versions for HVAC, plumbing, medical, legal and property management.
What it actually costs
Language support is priced inconsistently. Smith.ai publishes a dedicated Spanish line as a per-call add-on at $1.00, Checked Nov 18, 2026 on smith.ai/pricing, on top of a plan whose entry tier is $300/mo for 30 calls. Upfirst states 35+ languages as included, and its entry plan publishes at $24.95/mo for 30 calls. Those are not comparable prices, because one is a human answering the call and the other is software — but both are honest, and the arithmetic is what decides it.
The trap is comparing headline plans. A per-call plan with a $1.00 language add-on at 60 calls a month costs $60 more than the plan price suggests. A flat plan with languages included costs the same in a busy month as a quiet one. The pricing page shows the full published matrix with the unit made explicit, and the Smith.ai review works through the add-on stacking.
Our own position, stated plainly
We can configure the language of the greeting and the prompts on your line. Which languages are live is a configuration question for your build, and we will confirm exactly what is supported in the demo rather than publishing a language count we have not verified. If a caller needs a human in a language your on-call team does not speak, we will tell you that our model cannot fix it.
That honesty is the point. A vendor that lists forty languages and cannot staff a Spanish-speaking human at 2 a.m. has solved the greeting and not the call. Our human layer is escalation to your own on-call person, so the language capability of your team is the real constraint, and it is worth knowing before you buy anything. The 24/7 page covers what escalation actually does overnight.
How to test it before you sign
- Call the vendor’s line after hours and speak Spanish from the first word. Note how long until someone who can hold a conversation answers.
- Try a mixed-language opening — “hi, I need help with una fuga” — and see whether the system recovers or gets stuck.
- Give a street address with a Spanish street name and check the written summary reproduces it.
- Ask for a transfer in Spanish and confirm the person who picks up can continue in Spanish.
- Count how many prompts you had to survive before speaking to anyone. More than two is a design problem.
Those five calls cost nothing and will tell you more than any language list. The same discipline applies to the rest of the buying decision: the ten-point checklist puts the questions in order, and the medical and property management pages cover the industries where a language mismatch causes the most expensive mistakes.
Tell us what your callers actually speak
Send a week of after-hours recordings or a note of what your team hears, and we will say honestly whether language support is the constraint you think it is.
Where bilingual support matters most
- Trades in metro areas. Plumbing, HVAC and restoration calls skew toward emergency, and an emergency is the worst moment to fail at the first sentence. See plumbing and HVAC.
- Property management. Tenant emergencies do not wait for business hours or for a translator, and the tenant may not be the person on the lease. See property management.
- Medical practices. A language mismatch on a clinical call is a safety issue, not a service issue. The HIPAA checklist is the page to read first.
- Legal intake. Intake in a second language is common in criminal defence and family law, and mistranscribed details are expensive later. See legal.