How to Add Languages to a Bus Tour: Step-by-Step

Quick answer: to add a language to a bus tour you need, for every stop, a translated script and an audio file in that language, then a test drive to check it fits the route. Start with the two or three languages your passengers actually speak, translate from one clean source script, have a native speaker read the result, and test each language before you publish. With TourChorus, the AI drafts the translation and voiceover and you review both before riders hear them.

Step 1: Which languages should you add first?

Choose from evidence, not a wish list:

• Look at who is already on your bus. Booking-form countries, ticket-seller notes and reviews that mention language are all signals.
• Ask your front-line staff which languages they get asked about most.
• Start with two or three. Every language you add is something to maintain and test. Add more once the first ones are working.
• Check your plan limits. On TourChorus, Starter supports up to 3 languages and Growth up to 10, so you can choose a small set now and widen later.

Step 2: Is your source script ready to translate?

Translation copies your problems. Before you translate:

1. Keep each stop short. About 45 seconds (roughly 110 words) per stop suits most routes. Long stops get cut off by the next trigger.
2. Avoid idioms and local jokes that don't survive translation, or flag them so the translator can adapt rather than translate them.
3. Spell out names the narrator must pronounce (streets, people, places).
4. Fix facts first. Correcting a date once in the source is cheaper than correcting it in eight languages.

Step 3: How do you translate it?

You have three realistic options:

• AI translation, then human review. Fast and inexpensive. In TourChorus, translations are drafts: nothing reaches riders until you review and publish it, and each language shows a completeness indicator so you can see which stops are missing.
• A professional translator. Slower and more costly, usually best for your highest-volume languages.
• Your own bilingual staff. Good for languages you already have guides for.

Whichever you pick, have a native speaker read the final script once, ideally someone who knows your city. Small errors in place names and tone are easy for them to spot and hard for anyone else.

If you change the source script later, TourChorus marks the translations made from it as out of date, so you know what to update.

Step 4: How do you voice each language?

You can mix and match per stop:

• Generated voiceover. TourChorus can generate voices in 16 languages, with male and female choices: English, French, Spanish, German, Italian, Portuguese, Dutch, Polish, Japanese, Chinese, Korean, Arabic, Hindi, Russian, Turkish and Swedish.
• Your own recording. Upload a recording of your own guide for any stop, in any language, instead of the generated voice.
• If your language isn't in the list, upload your own recordings. That works for any stop in any language.

Listen to every voice before publishing. Voices are a matter of taste and tone, and you can change the voice used for a language.

Step 5: Does each language fit the route?

A translation is not the same length as the original. Some languages run longer, and scripts in Japanese, Chinese and Korean are best judged by reading time, not word count. Check that each stop still ends before the next one triggers.

TourChorus's AI review estimates how long each script takes to read aloud and compares it with the time to the next stop, flagging scripts that are too long. Run it per language, and shorten anything flagged.

Step 6: How do you test each language?

1. Dry-run the route. TourChorus can simulate the drive along real roads and report stops that wouldn't trigger, so you catch pin problems before passengers do.
2. Listen in each language on a real phone, with headphones, at the stops where timing is tightest.
3. Check the fallback. If a stop has no translation yet, riders hear your default language rather than silence. Make sure that is what you want for each language while you finish it.
4. Test on a real route at least once before the first passenger boards.

Step 7: How do passengers choose their language?

Riders pick their language once, from the languages you enabled, and every stop then plays in it. The TourChorus app's own menus are available in English, French, Spanish, Ukrainian, German, Japanese, Chinese, Russian and Portuguese, and the app starts in the phone's language. Tell passengers at booking which languages you offer and that they should bring headphones.

What does adding a language cost?

On TourChorus the AI work is metered in credits: about 1 credit per 2,000 characters translated and 1 credit per 1,000 characters of voiceover. For a 30-stop route of about 45 seconds a stop, adding one language is roughly 42 credits, about $4.20 at the top-up price. Recording your own guides instead of generating voices costs nothing in credits. The worked numbers are in how much a hop-on hop-off audio guide costs.

Frequently asked questions

How many languages should a bus tour offer? Enough to cover most of your passengers, and no more than you can test and keep current. Two or three is a sensible start.

Is AI translation good enough for tourism? It is a strong first draft. Have a native speaker review important languages before you publish.

Can I use different voices per language? Yes. Each language has its own voice, and you can choose a different one from the available options.

Do I need to re-record everything when the script changes? Only the stops that changed. Voiceover is marked out of date when its script changes, so you can re-voice just those stops.

Where do I start? Start a free trial and add your first language in the dashboard, or hear the demo first. For the product page, see the multilingual audio guide for tour buses.