How to Respond to Non-English Speaking Real Estate Leads

In this article
Here is how to respond to non-English speaking real estate leads: reply in the lead's own language within 60 seconds, ask four short questions (goal, property, timeline, availability), offer two showing times, and save the language in the CRM so the next person who touches the lead speaks it too.
What you need at a glance
Set these six items up once. Every non-English lead then follows the same path.
| Item | Why it matters | Where to find it |
|---|---|---|
| CRM field "Preferred language" with values English, Spanish, Portuguese, Mandarin, Other | Every later message and handoff matches the lead's language | Custom field on the contact record |
| Language rule: the language of the first message wins | Removes guessing from a name or a phone area code | Lead form, inbound text, or the first words on a call |
| Reply templates in each language, checked by a fluent speaker | Keeps the first reply short and correct | Saved templates in your CRM |
| Consent text and consent date fields | Stores what the lead saw, in the language they saw it | CRM consent field and the lead form footer |
| Calendar slot of 30 minutes with a "bilingual host" tag | Offers only times a fluent person can attend | Calendar settings |
| After-hours rule: reply now, a person calls back at 9 a.m. local time | The lead gets an answer tonight and a human tomorrow | Team policy document |
Why do language gaps cost you real estate leads?
The audience is large. According to the U.S. Census Bureau (2022 languages story), Spanish was the most common non-English language spoken in U.S. homes (62%) in 2019. That is a share of everyone who spoke a language other than English at home, so plan for Spanish first and add other languages from your own lead sources.
Speed is the second gap. A report from Florida Realtors (2026 Pied Piper study) found that, in a study of 2,198 inquiries to 21 brands, 68% of website inquiries received no response within 24 hours and only 18% resulted in communication with an agent within that time. Those figures cover all inquiries, not only non-English ones. A lead who needs a different language starts from the same weak baseline.
For timing targets in English, see the lead response timing and scripts guide. The steps below add the language layer on top.
How do you respond to non-English speaking real estate leads, step by step?
Follow these steps in order. Each one names the system and the setting it touches.
- Capture the language at the door. Add a "Preferred language" dropdown to every lead form, with the values from the table above. For calls and texts, set the field from the language of the first message.
- Tag the lead source. In the CRM, tag each lead with its source (portal form, home-valuation form, open-house sign-in, website chat). Language patterns differ by source, so the tag shows you where to hire or translate first.
- Reply in under 60 seconds in the lead's language. Use your saved template for that language. Keep it to three sentences: who you are, the property or request they named, and one question.
- Ask the same four questions in every language. Goal, property, timeline and availability. Use fixed answer options so the CRM stores clean data (see the intake table below).
- Offer two 30-minute slots with a bilingual host. Show only times when a fluent agent or a booked interpreter can attend. Confirm by text in the same language.
- Set the after-hours rule. Reply right away, then a person calls back at 9 a.m. local time using the booked appointment or CRM record.
- Store consent wording and date. Save the form's consent text, its language and the date in the CRM consent field before you send marketing follow-up.
The intake questions keep every language on one scorecard:
| Question | Answer options stored in the CRM | Why you ask |
|---|---|---|
| What is your goal? | Buy, sell, rent, both | Picks the buyer or seller path |
| Which property or area? | Listing ID, address, or neighborhood | Ties the lead to a specific home |
| When do you want to move? | 0 to 30 days, 1 to 3 months, 3 to 6 months, later | Sets follow-up priority |
| When can you meet? | Weekday morning, weekday evening, weekend | Matches a slot with a bilingual host |
Example: Assume a hypothetical team gets 200 inbound leads in a month and 15% of them prefer a language other than English. That is 30 leads. Assume one bilingual agent can personally answer 20 of them in a day and the rest arrive when that agent is off. Ten leads wait for a reply, so the team needs either a second fluent person or a reply system that works around the clock.
For timing across all leads, compare your numbers with the 2026 response time benchmarks.
What should the first reply say in another language?
Keep the first reply short. Name yourself, name the property, ask one question, and give a clear way to switch to English if the lead wants. Have a fluent speaker review every template before it goes live.
Example call script (illustrative, not a recording)
Scenario: a Spanish-speaking buyer fills out a portal form for a three-bedroom home.
Agent: Hola, le llamo del equipo inmobiliario sobre la casa de tres recámaras que usted pidió. ¿Tiene un minuto?
Lead: Sí, dígame.
Agent: ¿Quiere comprar para mudarse pronto o está empezando a mirar?
Lead: Queremos mudarnos en dos meses.
Agent: Perfecto. ¿Prefiere ver la casa entre semana por la noche o el fin de semana? Tengo el sábado por la mañana o el martes a las seis.
In English: "Hello, I'm calling from the real estate team about the three-bedroom home you asked about. Do you have a minute?" "Are you buying to move soon or just starting to look?" "Do you prefer a weeknight or a weekend showing? I have Saturday morning or Tuesday at six."
Example text script (illustrative, not a recording)
Scenario: a Portuguese-speaking seller submits a home-valuation form after hours.
Text: Olá! Recebemos seu pedido de avaliação da casa. Você pretende vender nos próximos três meses? Responda SIM ou NÃO. Para parar, responda PARE.
In English: "Hello! We received your home valuation request. Do you plan to sell in the next three months? Reply YES or NO. To stop, reply STOP."
A person then calls at 9 a.m. local time from the CRM record to book the listing appointment. The follow-up templates article has English versions of these messages you can translate and adapt.
If your CRM cannot store the language field, tags, or consent wording cleanly, fix that first. The CRM comparison lists how popular systems handle follow-up.
Where Swiftleads AI fits
The AI responds to inbound leads in under 60 seconds, 24/7/365. It responds by voice, SMS, email or WhatsApp, in 15+ languages. It asks the qualification questions on the call, books the appointment on your calendar, and syncs the lead's details to your CRM.
Scope is real estate only, covering inbound leads and previously consented follow-up. Outbound calls stay with your people. Swiftleads AI pricing is by custom quote, based on lead and call volume, channels, integrations and workflow. See the pricing overview for how a quote works.
Swiftleads AI supports TCPA, A2P 10DLC, DNC, consent handling and call recording. Your staff still own the human work: the bilingual host runs the showing, and the agent makes the 9 a.m. callback from the CRM record.
Frequently asked questions
Do I need a bilingual agent to answer non-English leads?
A bilingual agent helps most for showings and listing appointments, where trust matters. For the first reply and basic qualification, reviewed templates or an AI reply system can cover the gap until a fluent person joins.
Which language should I reply in?
Reply in the language of the lead's first message or form selection. Do not guess from a name or phone area code. Offer a simple option to switch to English if the lead prefers it.
How do I store a lead's language in my CRM?
Create a custom contact field called Preferred language with a fixed dropdown. Fill it from the form or first message, and tag the lead source so you can see which channels bring which languages.
Should I use machine translation for replies?
Machine translation is fine for drafting templates, but have a fluent speaker review them before use. Short, plain sentences with one question translate better than long messages and lower the risk of confusing wording.
What if no one on my team speaks the lead's language at showing time?
Book the showing only for slots tagged with a bilingual host, or arrange an interpreter before the appointment. Confirm the plan with the lead in their language by text so nobody is surprised.