Prospecting in two languages and two cities at once
Selling in an English city and a French or Spanish one? Run one prospect list per city, write each first message in its own language and keep the reps apart.
Part of the guide AI employee for sales prospecting
To prospect in two cities that speak different languages, run the same search in both but keep everything after it separate: one list per city, first messages written in each city's own language by someone (or something) that writes it well, and each list going only to the reps who speak it. The search and the scoring can be shared; the words cannot. A translated English pitch reads as a translated English pitch, and in many markets that is enough to lose the reply.
This is for sales teams that cover two language markets: Toronto and Montreal, Brussels and Antwerp, Madrid and Lisbon, Geneva and Zurich, Singapore and Kuala Lumpur, or a head office selling into a neighbouring country. It covers how to set the work up, a worked example built on real counts from Toronto, the mistakes that make bilingual outreach feel foreign, and the AI employees that do it.
Share the search, split the words
Most of a prospecting routine does not care about language. Finding the businesses, removing duplicates, skipping existing customers and scoring fit are the same in every city. Three parts must change by city:
- The first message. Written in the city's language from the start, with local forms of address (formal or informal, first name or surname), local date and number formats, and a reason to call that makes sense there.
- The person who follows up. A rep who cannot hold the call in that language should not be sending the email.
- The timing. Public holidays, working days and the hours people answer messages differ, even between cities a short flight apart.
So the clean way to build it is one routine copied for each city, with the city, the language and the reps as the only differences. In xMap Flows, linked copies of one flow do exactly that: change the search or the scoring once and every city's copy follows, while each keeps its own city, message language and recipients.
A worked example: salons in Toronto and Montreal
Say a company selling booking software to beauty salons covers Toronto in English and Montreal in French. For a sense of scale on the English side, xMap's places database lists 838 beauty salons within 10 km of the centre of Toronto (November 2026). Of the 414 nearest the centre that have an opening date, 31 opened in the twelve months before.
Nearly all the salons near the centre are independent, which suits software sold to owners. The Montreal side needs its own search; the counts there are for the flow to find, not for us to guess. What follows is a made-up week, to show the shape of the routine:
| City | New salons this week | Scored 70 or more | Message language | Goes to |
|---|---|---|---|---|
| Toronto | 7 | 4 | English | Two English-speaking reps |
| Montreal | 5 | 3 | French | One French-speaking rep |
Invented weekly figures, for illustration only.
Each Montreal salon gets a first message written in French, addressing the owner as a French speaker would expect, and mentioning something true about the salon from its own data, such as its opening this autumn or its strong rating. The Toronto salons get their own English messages. Neither rep ever sees the other city's list.
Mistakes that make bilingual outreach feel foreign
- Translating the English template. Word-for-word translations keep English sentence shapes and idioms. Ask for a message written in the language from scratch, with the same facts.
- Guessing the language from the city alone. In bilingual cities, a business's name and website often show its main language. Let the message follow the business, and default to the city's majority language when unsure.
- One sender for both. A reply in French to an English-only rep stalls the deal. Route each list to the rep who speaks it.
- Ignoring local calendars. A message landing on a regional public holiday gets buried. Set each city's schedule in its own time zone and skip its holidays.
- Different rules in each city. If the cities score fit differently by accident, you cannot compare them. Keep the scoring shared, and only the words local.
The AI employees that run it
Build the routine once, then make a linked copy for the second city:
- Schedule: every weekday at 8, each copy in its city's own time zone, skipping its public holidays.
- Area of interest: the city.
- Nearby places: beauty salons opened in the last 6 months, or Map business scan for the newest.
- Only new, then Match with my table to keep only salons not already customers.
- xMap LLM to score fit with the shared rules, and a second xMap LLM to write the first message, told to write in French (or English) for an owner in that city, from the salon's own facts only.
- Outreach with approval, sending from and to the right rep, or Email the list to that rep.
What lands in each rep's inbox: only their city's new salons, best first, each with its score, the reason and a draft first message in their language, waiting for a yes in Outreach. The sales manager sees both cities' AI employees side by side in the Team inbox and can change the shared scoring once for both.
Questions
Can xMap Flows write prospecting messages in other languages?
Yes. Tell xMap LLM in its instructions which language to write in and for whom, and it writes each message from that business's own facts. Have a native speaker check the first ones.
Should I translate my English pitch?
It is better to have each message written in the language from the start, with the same facts and offer. Translated sentences often sound foreign to native readers.
How do I stop the two cities' lists mixing?
Run a copy of the routine per city, each sending only to its own reps. Linked copies keep the shared parts in step while the city, language and recipients stay separate.
Can each city run on its own timetable?
Yes. Each copy's Schedule has its own time zone, and it can skip that country's public holidays.