Lumisia for Business — for venues and IP partners

Turn your official character into the guide families follow through your venue.

Meet by QR, observe exhibits together, ask about approved information, and move to the next highlight. We connect the character and knowledge you already own into one in-venue journey.

Private or designated operators of aquariums, science centres, museums and family venues with an existing official character

QR → Observe → Talk → Next place
Venue and characters are illustrative. A real deployment uses only rights-holder-approved character assets and venue information.
Who it is for

A deliberately narrow first partner profile.

A strong pilot fit

  • An existing official character with clear usage rights
  • A walkable family exhibit or venue route
  • Approved FAQs, exhibit copy and maps
  • A small team able to review and decide

Outside the first pilot scope

  • Generating a new character from scratch
  • A generic low-cost support bot
  • School, medical or mental-health counselling
  • Guaranteed business outcomes before measurement
The experience

Connect the venue journey, not just a chat box.

The approved route, missions and next stops are deterministic venue data. The AI agent explains approved information; it does not invent the physical route.

01

Meet the character by QR

No visitor signup or exact age. Families choose Together or Explorer for the level of detail.

02

Look, talk and learn

Complete an observation mission, tap a quiz, or ask a question grounded in approved venue information.

03

Move to the next highlight

The next location comes from a venue-approved sequence and instruction, never an AI-generated route.

Interactive preview

Try the family-guide flow.

This preview mirrors the implemented mode, stop and completion contract. The public demo exposes the same flow.

We do not ask for an age; choose only the level of detail.
Marine
Family Experience Guide
Choose how to explore
Live demo

Try the product, not only a slide.

Open our demo aquarium and walk through the family route. A phone-sized viewport works best.

  • Choose an explanation mode
  • Complete an observation mission
  • Ask about approved information
  • Move to the next stop

This is an EISOL LLC demo environment, not a customer deployment or evidence of customer outcomes.

Open the demo aquarium
First engagement

Start with an 8–12 week paid, fixed-scope pilot.

8–12 weeksPaid pilot

We build one usable venue journey and test whether families use it and the team can operate it. Pricing is scoped to the venue, languages and state of approved information.

This is a paid pilot that tests willingness to pay and operational fit, not a free proof of concept.

Initial scope

  • One approved official character
  • One route with 3–5 stops
  • Two family modes and observation missions
  • Approved FAQs, exhibit copy and map information
  • QR launch and operator dashboard
  • Pre-launch review and in-pilot iteration

What we measure

QR launches
Launches by placement
Guide starts
Guide start count
Missions
Starts and completions
Venue progress
Completions by stop
Guide completion
Completions ÷ starts
Language
Aggregated use by language

Not in the initial scope

  • AI generation of a new character
  • Guaranteed return visits, revenue or dwell time
  • At-home follow-up without guardian consent
  • School, medical or mental-health counselling
  • Full replacement of reception or signage
Two surfaces

One contract for the family experience and venue learning.

Visitor surface

  • Start by QR without signup
  • Choose detail level without entering age
  • Venue stops and observation missions
  • Approved-information questions and quizzes
  • Venue-approved next stops

Operator surface

  • QR and guide starts
  • Mission starts and completions
  • Completions by stop
  • Aggregated language use
  • A visible notice when an aggregate read cap is reached
Safety, IP & data

Family use is not treated as an adult visitor chat.

Family-guide venues receive server-enforced safety and data-minimisation boundaries.

Checks before and after the model

Crisis and inappropriate inputs are intercepted before the AI call; responses are checked before display and can redirect to a nearby caregiver or venue staff member.

No transcript in the operator data plane

Family-guide user and AI message text is not stored in venue conversation logs or customer-voice collections.

No persistent anonymous visitor identity

Family guides do not use the return-memory visitor ID, device fingerprint or consumer character collection.

Approved IP and primary information

Only rights-holder-approved assets and venue information are used. Routes and next stops are configured, not generated.

Aggregate counters without a journey trail

QR scans increment placement totals and approved experience actions increment daily counters, without retaining a session trail from which one family's journey can be reconstructed.

No third-party trackers

Visitor /v routes disable Google Analytics, Clarity, Meta and other third-party behavioural tracking.

This is not a claim of legal compliance. Venue notices, contracts and retention requirements are reviewed for each engagement.

Expansion gate

Prove the on-site experience before extending the relationship.

01

Paid pilot

Build one route and measure launch, progress and completion.

02

Ongoing operation

Update approved information, missions, languages and wayfinding each month.

03

Evidence-gated expansion

Only then consider at-home reflection or return touchpoints with the right guardian-consent design.

Meet on site, continue at home and return is a future extension—not a delivered promise in the initial pilot.
FAQ

Frequently asked questions

Do we need an existing official character?

Yes for the first pilot. We use rights-holder-approved art, persona, voice rules and prohibited expressions. Generating a new character from scratch is outside scope.

Can children type freely?

The family surface includes pre-input and post-output checks, instructions not to solicit personal details, and redirection to a nearby caregiver or venue staff member. It cannot guarantee perfect safety, so the design assumes families use it together and the venue reviews operation.

Does a visitor need an account or enter an age?

No account is needed to start the venue guide. We do not request an exact age; families select only the level of explanation.

What conversation and activity data is stored?

The family guide does not store transcript text, a persistent visitor ID or a device fingerprint. On-device guide progress expires after 24 hours; QR scans increment placement totals and approved experience actions increment daily counters. Retention and venue notices are defined per engagement.

How many languages can you support?

We launch only languages for which the venue can provide primary information and review answers. We prioritise based on the visitor mix rather than promising every language.

What are the duration and price?

The first engagement is an 8–12 week paid, fixed-scope pilot. Pricing depends on the venue, stops, languages and readiness of approved information.

Will it increase return visits or dwell time?

We do not claim a universal improvement. We first measure product-native behaviours such as launches, mission completion and stop progress, then evaluate wider outcomes only where venue data can support it.

Start with one character and one route.

Tell us about the character, venue route and behaviour you want to validate. We will propose a fixed paid-pilot scope.