At 10:40 on a Sunday night, a homeowner sends a fence company a WhatsApp message in Portuguese: "Vocês fazem cerca de madeira de 1,80 m? Quanto custa mais ou menos?" (Do you build six-foot wood fences? Roughly what does it cost?) She'd rather not try a phone call in English, and if nobody answers she'll message the next company on the list. With our Guru on that WhatsApp line, she gets an answer in Portuguese a few seconds later, taken from the company's own price sheet and service area page, plus an offer to book an estimate. Most businesses never see the customers who didn't get that answer. They just went somewhere else.
That's the customer this post is about: the one who doesn't write comfortably in English. They don't complain or leave a bad review. They decide that asking in a second language is more trouble than it's worth, and buy from someone else.
Who's in your service area
According to the Census Bureau's American Community Survey, more than one in five people in the United States speaks a language other than English at home, and more than 25 million say they speak English less than very well. In plenty of metro areas the share is far higher. For a plumber, a moving company or an online store, that can be a real slice of the people already looking for what you sell.
Then look at how those customers buy. Most people would rather buy from a business that explains things in their own language, and a meaningful share won't buy at all when it doesn't. The cost isn't a bad experience you can fix. It's a conversation that never started.
The moments you never see
The fence quote is one. Here are a few more:
- A customer who reads Korean first wants to know whether a salon takes walk-ins on Sunday.
- Someone shopping an online store at eleven at night writes in Polish to ask whether a jacket runs small.
- A patient's adult daughter emails in Arabic on her father's behalf to ask what the new-patient paperwork involves.
Each question is simple. The problem is the language, and the hour.
Answering in their language, from your information
This is what our Guru does on the text channels: web chat, email, SMS and WhatsApp. It understands and answers in about 100 languages, and it answers from your real information: your services, your hours, your prices, your policies. The homeowner who wrote in Portuguese gets an answer in Portuguese about your actual fence options. The shopper who wrote in Polish gets the real sizing note from your product page, in Polish, in seconds.
There's no per-language setup. You don't translate your website, you don't keep a Spanish FAQ and a Korean FAQ, you don't hire anyone. You write your information once, in English, and the Guru answers from it in whatever language the customer used. When you update a price or a policy and the site is re-indexed, every language picks it up at once, because there's only one source.
Booking the estimate, in Portuguese
When the homeowner says yes to the estimate, the conversation stops being a question and becomes a booking. That step isn't left to the AI. A deterministic flow takes over: it offers only the estimate slots your scheduling system reports as open, checks each answer she gives, reads the appointment back to her from your system's own data, and books it only when she says yes. If anything doesn't fit, it books nothing and offers her a person instead. We explain the design in How JSFE Brings Trusted Workflow Control to Agentic AI.
That's why we can guarantee 100 percent accuracy on transactional steps like that one. The worst case is the AI missing that she wanted to book, which most likely gets caught on her next message, never a wrong appointment.
Why accuracy matters more across languages
A customer writing in a second language has less ability to spot a wrong answer, and a confident mistake about a cancellation policy is still a mistake in Korean. That's why the Guru answers from your content, and why we measure its accuracy on real conversations: 97%+ on informational answers, rather than a fluent guess translated after the fact.
On the phone, we're specific about what we support today: the Guru answers calls in English and Spanish. For every other language, the text channels serve the customer, and for many of them a WhatsApp message is already how they'd rather reach you.
Where a person still belongs
Language handling is strongest in widely spoken languages and less reliable with heavy dialect, slang or rare languages. That's true of AI systems generally, and a small business should plan for it rather than be surprised by it.
Some conversations need a person no matter what language they're in: an upset customer, a billing dispute, a complicated job that needs judgment. The Guru hands those to your team during the service hours you set, and escalates when a customer sounds frustrated or distressed. If someone on your staff speaks the customer's language, that's who should take it.
Questions worth asking
- Which languages do your customers speak at home, in your actual service area?
- Which channel would they choose: WhatsApp, text, email or web chat?
- Are your prices, hours and policies written down somewhere an AI can answer from?
- What happens today when a message arrives at 10:40 on a Sunday night, in a language nobody on your team reads?
The same pattern shows up in schools, where families who don't read English get counted as disengaged when they were never given a way in. We wrote about that in serving families in their own language, and the multilingual customer service page walks through how it works across channels.
The quickest test is your own. Send your business a WhatsApp message in Portuguese, the way the homeowner did on Sunday night, and see what comes back. If it's an answer and an estimate on the calendar, she's a customer. If it's silence until Monday, she's already talking to the next company on the list.
