Browser-first guest experiences
Guest experiences are delivered as responsive web applications opened from links or QR codes. Venues and events can put access on signs, badges, tickets, rooms, or tables without app store distribution.
Some flows still integrate with platform capabilities such as payments or wallet passes, but the baseline guest journey starts in the browser.
Why browser-first matters
Scoutello is often used in time-sensitive physical contexts: events, hotels, tours, destinations, and partner campaigns. A browser-first entry keeps the first action simple when guests need information quickly.
The browser-first model lets teams:
- Print or display QR codes on signs, badges, tickets, rooms, or tables.
- Share direct links in emails, newsletters, widgets, and partner sites.
- Launch temporary campaigns without app store review.
- Serve multilingual content to visitors on their own device.
- Keep guest experiences connected to the same dashboard content operators manage.
Main guest surfaces
| Surface | Typical route | What guests do there |
|---|---|---|
| Landing pages / web apps | /landing/:id | Open tiles, read information, submit forms, view offers, start tours, or navigate nested pages. |
| Tours | /tours/:id (often /tours/:id/:tourRunId when resuming a session; from a landing page also /landing/:id/tours/:tourId) | Follow stops, listen to audio, view maps/site plans, and access tour-specific support. |
| Events | Event and landing page routes | Register, check information, use event tiles, and interact with attendee content. |
| Widgets | /widgets/:id/checkout and related flows | Complete embedded purchase or registration journeys from external sites. |
| Short links | Short slugs | Reach the correct guest or marketing destination from print and campaign material. |
Operator checklist
Before launch:
- Test the public link or QR code on a real mobile device.
- Confirm the content is published in the intended organization and language.
- Verify access, payment, and widget flows outside the logged-in dashboard.
- Check that fallback copy, empty states, and contact paths make sense for guests.
- Keep physical signage aligned with the final URL or short link.
Support Notes
When a guest reports a broken experience, identify how they entered: QR code, short link, email, widget, direct landing page, or tour link. Then inspect the matching surface in the dashboard and confirm the content is active, public where expected, and attached to the right organization.
Related concepts: Product model, Reference: routes.