Begin with the visitor journey
Ask every supplier to show the experience from the visitor's point of view. Scan the QR code using ordinary mobile data. Count the steps before the first track plays. Check whether the page is clear to an international visitor and whether the guide still makes sense to someone who has not heard a staff explanation.
A smooth journey normally means no forced account, no app download, readable buttons, visible language choice, transcripts, familiar playback controls, and a clear way to move to the next stop. Test on more than one phone and include someone who was not involved in the procurement process.
Check the operating model
The museum needs to know who will add stops, correct facts, replace images, publish translations, and update temporary exhibitions. A good platform should give the team enough control without turning every content edit into a technical support request.
Ask what is included at launch: QR codes, entrance posters, object labels, staff guidance, content migration, training, translation support, and analytics configuration. These details often matter more than an impressive feature that staff may never use.
Can authorised museum staff update content?
Can one guide support free and paid experiences?
Can languages be added gradually?
Can the same code keep working after an edit?
What support is available during the first weeks?
Ask how language quality is protected
Multilingual capability is not only a number on a plan. Ask whether the interface, instructions, text, transcript, and narration all change language together. Check how the preferred language is selected and whether the visitor can override it easily.
Find out who reviews generated translations and how corrections are stored. Museums should keep control of approved wording, especially for cultural terminology, proper names, community voice, and stories where a literal translation could lose meaning.
Demand useful evidence
A demo proves that software can run. Existing venue partners show whether the complete service can work in real museums. Look for named clients, visitor-facing examples, photographs of signage in place, testimonials, and an explanation of what changed after launch.
Journey Pal currently works with seven New Zealand museum and heritage clients. Its public directory shows the venues, their guide languages, selected visitor-facing guide links, and real installation photographs. That gives prospective museums something concrete to inspect before making a decision.
Compare the full commercial terms
Put subscription fees, setup work, extra languages, narration, storage, visitor limits, payment fees, white-labelling, support, and exit arrangements in the same table. For paid guides, confirm who controls the visitor price, who receives the payment, and how refunds and revenue reporting work.
Finally, ask how to export your content if the relationship ends. A good supplier should be comfortable discussing ownership, data location, privacy, backups, and portability before the contract is signed.
Frequently asked questions
What is the most important audio guide feature?
Fast, understandable visitor access. Advanced features have little value if visitors do not get from the QR code to the first useful story.
Should museums ask for references?
Yes. Named venue partners, live examples, installation photographs, and references help separate working experience from marketing claims.
Is a free trial enough to evaluate a platform?
A trial is useful for software usability, but museums should also evaluate launch support, content workflow, visitor discovery, analytics, and the supplier's real-world track record.

