Content and languages
Your stories, in your visitors’ languages
WayWyser combines audio, text and supporting images in a browser-based tour. Start with interpretation your team trusts, then agree narration and languages around the people visiting your site.
Make the source story work first
A good audio stop does more than read out an interpretation panel. It helps visitors connect the story to what is in front of them. Existing research, guide notes and archive material provide the foundation; the script needs a clear purpose and a tone suited to listening on site.
AI can assist with a first draft. Your site team reviews the historical content before publication, including names, dates, local terminology and the distinction between evidence and tradition. A demonstration based on public information remains a draft until reviewed.
Choose languages around the audience
Use what you know about visitors to decide which languages matter first. Visitor enquiries, available audience information and staff experience can help frame the discussion. Agree the initial language set as part of the scope, rather than treating every available option as a launch requirement.
Our sample process provides a short English demonstration and one relevant visitor language. It gives your team something concrete to assess before planning the full tour.
Listen for meaning as well as pronunciation
When reviewing narration, pay attention to place names, personal names, specialist terms and pacing. Local pronunciation can be especially important in a heritage story. Provide corrections clearly so they can be carried through the review.
For translated content, agree who can assess meaning and tone in each chosen language. Confirm the translation review arrangements and responsibilities before approval. A natural-sounding voice alone does not establish that the historical meaning has been preserved.
Keep text, images and audio working together
Visitors may want to listen, read or refer to a stop image while exploring. WayWyser can present those elements together, alongside a map and stop information. Choose supporting material that helps people understand the place rather than adding media for its own sake.
Discuss audience and access needs when preparing the brief. Test the sample on the phones people actually use and check whether the text and controls are understandable. The right experience also depends on the route, signage and local connectivity.
Keep a clear approval and update process
Identify who coordinates corrections and approves the final script. Agree how changes are reflected across the source text, translations and narration, so different versions of a story remain consistent.
WayWyser can regenerate translations and narration when approved content changes. The work, review points and support arrangements for later updates should be included in the project discussion.
Hear a story from your own site
Send the location and any trusted interpretation you already have. Tell us which visitor language you would like to hear alongside English and who will review the sample. For the wider launch process, see how to plan an audio tour.
The approach can support unmanned heritage sites and gardens and trails without issuing handsets or requiring an app installation.
Request a sample for your site
Tell us your site name, annual visitor numbers and whether it is unmanned. Include any research or interpretation material you want us to start from.