What you’ll get from this guide
- Ask in the visitor's language: detect it from the page's language or the visitor's browser, and show your greeting, questions, answer options, buttons and error messages in that language.
- Keep answers usable in one language: give every answer option a fixed meaning behind the scenes, so a choice made in Spanish lands in your pipeline exactly like the same choice made in English.
- Translate what the visitor reads: questions, answer options, the chat greeting and the confirmation email. Have a person who speaks the language review anything about prices, scope, guarantees or legal terms.
- Reply in the language they used, or say clearly which language your team will call in.
Many service businesses in the US serve customers who are more comfortable in Spanish, and some serve speakers of other languages too. Those visitors may read a page in English well enough, but a form full of English questions is where many of them stop. They aren't sure what a question means, they worry about picking the wrong option, or they'd rather call later and never do.
The fix isn't a second website. It's asking the few questions that matter in the visitor's language, then making sure the answers reach you in a form your team can use. This guide covers how to detect the language, what to translate and what to leave alone, how to keep scoring and your pipeline in one language, and a step-by-step setup.
Why Asking in the Visitor's Language Matters
- Qualifying questions are where people hesitate. A visitor can skim an English page, but choosing between "repair" and "replacement" or entering a budget range needs certainty.
- Wrong answers cost you more than missing ones. A visitor who guesses at an English option sends you a lead that looks qualified and isn't, or looks unqualified and is.
- The first message sets expectations. A greeting in their language tells the visitor they can explain the job comfortably and that someone will understand them.
- You learn more. People write longer, clearer descriptions of the job in the language they think in.
How to Tell Which Language a Visitor Speaks
Use the signals you already have, in a fixed order. If the page itself is in Spanish, for example a Spanish service page or a /es/ address, show the questions in Spanish. If the page doesn't say, use the language the visitor's browser asks for. If neither matches a language you support, fall back to your main language.
Always let the visitor switch. A bilingual visitor reading your English page may still want Spanish questions, and a browser set to Spanish doesn't always mean the person prefers it.
What to Translate, and Who Should Review It
| Text | Translate? | Review by a fluent speaker? |
|---|---|---|
| Greeting and chat opener | Yes | Recommended: it sets the tone |
| Qualifying questions | Yes | Yes: meaning must match exactly |
| Answer options | Yes | Yes: each must mean the same as the original |
| Buttons, required-field notes, error messages | Yes | Standard wording is usually fine |
| Confirmation email or text | Yes | Yes: it's your first written promise |
| Prices, what's included, guarantees | Yes, with care | Always, before it goes live |
| Legal terms, consent and privacy notices | Yes, with care | Always, ideally by a qualified professional |
| Your business name, brand and service names people search for | Usually no | Decide once and keep it consistent |
What Not to Machine-Translate Without Review
Machine translation is a good first draft and a poor final word for anything that sets an expectation. Have someone who speaks the language read these before they go live:
- Prices, ranges and what a price includes. A small wording change can turn "starting at" into a fixed quote.
- Trade terms. Words for parts, materials and job types vary by region, and a literal translation may not be the word your customers use.
- Guarantees, warranties, cancellation and deposit terms.
- Consent to be contacted by text or phone, and your privacy notice.
- Anything that tells the visitor what happens next, such as response times or who will call.
Rules about consent and contact differ by state. This is general guidance, not legal advice.
Keep Answers in One Language for Scoring
If a Spanish-speaking visitor picks "Reemplazo" and an English-speaking visitor picks "Replacement", your team and your scoring rules should see the same answer. The simplest way is to give every answer option a fixed internal value and translate only the label the visitor sees. Your scoring, routing and reports then work from the internal value, whatever language the visitor used.
Free-text answers are different: the visitor's own words come back in their language. Keep the original, add a translation for your team if you need one, and note which language the lead used so whoever follows up knows whether to reply in Spanish.
How to Set Up Lead Capture in Your Visitors' Languages
Pick the languages that matter
Start with the language your visitors and callers already use most besides English. For many US service businesses that's Spanish. Add others only when you can follow up in them.
Write your questions in your main language first
Keep them short and concrete: the service needed, the address or area, timing, and one or two questions that tell you whether the job fits.
Fix the meaning of every answer option
Give each option an internal value that never changes, so translations change only the words the visitor sees.
Draft the translations, then review them
Use AI or a translation tool for the first draft. Have a fluent speaker check the questions, options, greeting and confirmation email, and always the parts about price, scope and terms.
Show the right language automatically
Use the page's language first, then the visitor's browser, and let them switch.
Follow up in the lead's language
Record the language with each lead. Reply in that language, or tell the visitor up front which language your team will call in.
Review leads by language each month
Compare how many visitors start and finish your questions in each language. A step where one language drops off often points to a confusing translation.
How LeadDuo Engage Asks in Your Visitors' Languages
LeadDuo Engage turns website visitors into leads with short conversations on your site, and it matches each visitor's language. On every plan, the bubble, teaser and prompt that open the conversation, and the form's built-in text such as the greeting, buttons and error messages, switch automatically to English, Spanish or Japanese, based on the page's language or the visitor's browser.
With Grow and Scale, you can also write your own questions, answer options and chat greeting in each language your visitors speak. Engage drafts the translations with AI, and you review and approve them before they go live. Answers come back to you in one language, so your scoring and your pipeline don't change.
Engage's AI website assistant replies in the visitor's language too. See the full flow on turning website visitors into leads.
FAQ: Getting Leads From Spanish-Speaking Visitors
Do I need a separate Spanish website to get Spanish-speaking leads?▼
How does a form know which language to show?▼
Will Spanish answers mess up my lead scoring?▼
Is machine translation good enough for a lead form?▼
What if nobody on my team speaks Spanish?▼
Should I translate my confirmation email too?▼
Ask your questions in your visitors' language
LeadDuo Engage matches each visitor's language and brings every answer back to you in one language, so your scoring and pipeline stay the same.
Keep Reading
See the whole product on the LeadDuo Engage page, and how it helps you turn website visitors into leads.
Get ready for the call with how to prepare for a sales call with a website lead.
See where your leads come from in how to see which leads come from ChatGPT and other AI assistants.