A seasonal guide, first week
They follow the tour with a colleague, then find the room notes on their own. The manager sees what is validated and decides when they guide alone.
Museums and visitor sites
Keep the visitor tour intact, season after season.
Every team, every season, the same instruction.
Tour route, room notes, languages, opening, visitor safety: Tsuno keeps what your team already knows and hands it to the right person at the right time.
Delivered pre-filled from your documents.
What you recognize
A living venue, teams that rotate
Visitors expect a tour that is right, whoever welcomes them that day.
-
The tour lives in guides' heads
Stories, room order, points of attention: nothing is written in one place.
-
Every season starts over
Seasonal hires arrive with little lead time and must learn fast.
-
Several languages, several tours
Versions drift apart depending on which guides carry them, and nobody knows which is current.
-
Opening and safety run on memory
Opening, closing, evacuating a group: you rely on whoever was there.
-
Front desk and tours barely talk
A closed room, a late group: information flows poorly between teams.
-
Knowing what happened
An incident, a visitor remark, an oversight: the news arrives late, or never.
On site
Three visit situations
A German-speaking group at 3 p.m.
The front desk asks who can take it. Tsuno answers with the guides trained on the German version, and the current notes.
A door left open
The remark goes into the daily log at closing, gets assigned, and management finds it the next morning.
Your venue, in Tsuno
From venue to guide
A venue has its spaces. Each space has its notes, instructions and language versions. Teams train on them.
- Venue
- Spaces and rooms
- Visitor tour
- Teams
Ask Tsuno
Visitor site questions, in plain language
- What is the evacuation procedure for a school group?
- Who can guide in German on Saturday afternoon?
- Which room notes have changed since the season started?
- What went into the daily log this week?
Fictional examples. You ask Tsuno from Tsuno or from your AI (ChatGPT, Claude, Mistral). Short, sourced answers, and Tsuno says when data is missing.
What Tsuno keeps for you
The essentials, from the front desk to the last room
You approve what is written. Tsuno says it again to every team.
-
Tour and room notes
Key points, stories, instructions per room: approved content, dated, found by every guide.
-
Language versions
Which version exists in which language, which one is current, and who is trained to deliver it.
-
Opening, closing, safety
A checklist per space, evacuation and visitor safety instructions within reach.
-
Training guides and seasonal hires
A path per role, front desk or guide, with skills validated by a person before the first solo tour.
-
Daily log
Incidents, visitor remarks and oversights recorded, assigned and followed through to closure.
-
Season scheduling
Staffing by role and by language, to cover every tour slot.
We already have a ticketing system.
Keep it. Tsuno does not sell tickets: it takes care of what happens once the visitor is inside. The tour, the languages, safety, and teams that change every season.
Frequently asked questions
Can we load our tour documents?
Yes, that is the starting point: tour route, room notes, procedures. Tsuno is delivered pre-filled from your documents, and you validate.
What if we run several venues?
Each venue has its own spaces, notes and teams. Management sees all of them and can ask about one venue or every venue.
Does Tsuno evaluate guides?
No. Tsuno connects the facts: training completed, checklists done, incidents. It rates and ranks no one. People decide.
Try it with your documents
Three documents from your venue are enough to see what Tsuno would tell your teams.
Trial with non-sensitive operational documents, and no personal data.