Handling Spanish-speaking callers with AI answering

Who is calling

The Census Bureau found that 78.3% of people age 5 and older spoke only English at home in 2018-2022, and that Spanish accounted for 61.1% of those who spoke another language^[1]. In 2019, 67.8 million people spoke a language other than English at home, almost one in five residents^[2]. In many service areas, from South Texas and Southern California to Miami, Chicago and the suburbs of most large cities, Spanish-speaking homeowners, landlords and property managers are a significant share of callers.

Most of those callers are bilingual. The Census Bureau reports that 61.0% of Spanish speakers spoke English very well^[1], which leaves about 39% who spoke it less than very well, the same share the Bureau reported for 2019^[2]. A caller who is stressed about a flooded basement or a family member with a headache from the furnace may switch to Spanish even if they normally manage fine in English. The phone system has to cope with both.

Four ways to handle Spanish calls

Callbacks are weaker than they look. Eight in ten Americans say they generally do not answer calls from unknown numbers^[3], so tell callers which number you will call from. Whichever approach you choose, the safety path must work in Spanish from the first second: a caller who says huele a gas must get your approved instruction immediately.

Many companies end up with a mix: Spanish intake in the evenings and at weekends, when no bilingual staff are on shift, and a bilingual CSR during the day. What matters is that the caller never hits a dead end. Map every path a Spanish-speaking caller can take, including transfers, voicemail and the on-call alert, and make sure each one ends with a person or a clear next step in Spanish.

Trade vocabulary varies by region

Spanish is not one dialect, and home service vocabulary is where the differences show. A system tuned on textbook Spanish may miss the words your callers actually use. Build a glossary from your own calls, and test every term.

Code-switching is normal. Many bilingual callers mix languages in one sentence: el breaker se brinca cada vez que prendo el microwave. Test that the system follows the meaning, records the problem accurately and does not force the caller into one language.

What to test before you go live

1. Language detection: does the system switch when the caller starts in Spanish, and does it offer Spanish if the caller struggles in English?
2. Accents and regions: use test callers from different backgrounds, such as Mexican, Puerto Rican, Cuban, Dominican, Central American, South American and US-born Spanish speakers.
3. Numbers: callers often say phone numbers in pairs, such as cincuenta y cinco, catorce. Check the read-back and the digits in the summary.
4. Addresses: English street names pronounced in Spanish and Spanish street names in English-speaking areas.
5. Names: double surnames, accents and spelling. Confirm spelling by letter where it matters.
6. Trade terms: run your glossary through real calls, including the regional variants.
7. Code-switching: mixed Spanish and English in the same sentence.
8. Safety scripts: every safety instruction in Spanish, triggered by everyday words such as huele a gas, la alarma de monóxido está sonando or salen chispas del enchufe.
9. Disclosure: the AI disclosure and recording notice in Spanish, worded naturally.
10. Summaries: written in English for your dispatcher, with the caller's key words kept in Spanish where they help.

Mistakes that lose Spanish-speaking customers

• Machine-translating the English script word for word. The result sounds stiff, and safety instructions can lose their urgency.
• Offering Spanish in the greeting but transferring to an English-only voicemail when the caller asks for a person.
• Recording the problem in a summary that only says caller spoke Spanish, with no details, so the technician arrives blind.
• Sending confirmations and preparation instructions in English to a customer who asked for Spanish.
• Testing only with one fluent staff member whose accent and vocabulary match the system's training best.
• Treating Spanish as an add-on nobody owns, so the glossary and scripts never get updated.

Each of these tells the caller that Spanish support is a box ticked rather than a service. Assign one bilingual person to own the Spanish experience end to end, from greeting to follow-up, and give them time each month to review calls.

Disclosure and trust in Spanish

Callers in any language want honesty about what they are talking to. In Pew's 2025 survey, 76% of US adults said it is extremely or very important to be able to tell whether content was made by AI or by people^[4]. Translate your disclosure carefully rather than word for word.

Use the formal usted unless your company and community clearly prefer otherwise. Keep sentences short. And make sure the route to a person works in Spanish too: if no bilingual staff are available, say so honestly and give a firm callback time.

The human side: bilingual staff and technicians

An AI system can take a Spanish call at midnight, but the job still involves people. Record the customer's language preference in the job record, so the dispatcher can send a bilingual technician where possible and the office knows to call back in Spanish. If you have only one or two bilingual staff, protect their time: Spanish callbacks should not all land on one CSR who also runs the board.

Technicians who are not bilingual still benefit from a good Spanish summary written in English. They arrive knowing the problem, the access notes and what the customer was told. A short card of key phrases, such as good morning, I am the technician from the company, and I will explain everything before I start, goes a long way on site and costs nothing.

Finally, check the rest of the customer journey: estimates, invoices, maintenance reminders and review requests. If the phone experience is in Spanish but everything afterwards is in English, the customer notices.

Launching Spanish support step by step

1. 01

   Count your Spanish calls

   Review a month of recordings or ask CSRs to tag calls. Note when they come in and what they are about.

2. 02

   Pick the approach

   Tested Spanish intake for after-hours and overflow, bilingual callback during the day, or a mix.

3. 03

   Write and approve the scripts

   Greeting, disclosure, recording notice, intake questions, safety instructions and the out-of-area message, all reviewed by a fluent speaker familiar with your trade.

4. 04

   Test with real speakers

   At least ten calls from different callers using the list above. Score them as strictly as English calls.

5. 05

   Route the work

   Flag Spanish-preferred customers in the record so the right technician or CSR calls back, and so confirmations go out in the right language.

6. 06

   Review monthly

   Read a sample of Spanish calls and summaries with a fluent reviewer and update the glossary.

Example: a pest control company in a bilingual market

Example: a fictional pest control company in a Texas metro tags its calls for a month and finds that a meaningful share of evening calls start in Spanish, mostly about roaches, termite swarms and bed bugs. It adds Spanish intake for after-hours calls and keeps daytime Spanish calls with two bilingual CSRs. Testing finds that the system misses chinches when callers say it quickly and mishears phone numbers given in pairs. The company adds both to its test set, requires a digit-by-digit read-back and retests. It also flags Spanish-preferred customers so treatment preparation instructions go out in Spanish, which reduces callbacks the next morning.