Skip to content

Strawberry AI brings conversational planning to every visitor journey.

World's Favorite

Operating System of Travel & Tourism.

Explore ModulesTalk to us

for events, safaris, stadiums, museums, stays, parks and cities. Deployed per destination. Configured to your operating rules.

Strawberry AI

An assistant that knows what is actually available.

Visitors ask in their own words. Strawberry answers from your content and your live availability — then hands over to a human whenever it should.

  • Conversational assistance

    Answers drawn from your own published content.

  • Discovery

    Surfaces the experience that fits the visit.

  • Plan my day

    Itineraries built around real capacity.

  • Visitor FAQs

    The same answer on every channel.

Strawberry AI is a platform capability. Scope, data access, escalation rules and human hand-over are configured per deployment; the exchange above is illustrative.

Explore Strawberry AI
Strawberry AIIllustrative

  • We arrive Saturday around 10. Can we do the morning safari and the museum the same day?

  • The 06:30 drive is full, but 09:15 has space for four. The museum has timed entry from 13:00 — that leaves a comfortable gap for lunch.

  • Two adults, two children. Do the kids need a separate permit?

  • Children under 12 are covered on the family permit. I can hold 09:15 for ten minutes while you decide, or pass you to the booking desk.

Zipr

Running a destination is bigger than selling tickets.

It is capacity, access, money, people and the hour before opening. Zipr is the layer that holds all of it together.

Talk to usExplore Modules
A full indoor arena seen from the upper tier
Built for the biggest

Peak day is the design brief.

High-demand destinations do not fail gradually — they fail at the gate, at the counter and at the settlement run, all on the same afternoon. Zipr is built around that afternoon.

  • High-demand release windows

    Hold, release and resell capacity in controlled waves instead of letting a single surge decide the day.

  • Many sites, many entry points

    Venues, gates, zones and channels share one inventory, so a sale anywhere is visible everywhere.

  • Complex inventory, one model

    Sessions, seats, permits, vehicles, rooms and passes are different shapes of the same capacity record.

  • Coordinated in real time

    Operations, finance and support work from the same live state rather than three exports taken at different times.

See how it scales
Scope
Multi-site, multi-gate

One deployment across a portfolio.

Channels
Direct, agent, kiosk, partner

Shared capacity, separate rules.

Operating model
Configured per destination

Your rules, not a template.

Record
Gate to ledger

Every entry traceable to a transaction.

Your inventory. Your control.

One layer between your systems and your gates.

Zipr holds the operational truth — what exists, what is sold, what may enter — and keeps the systems around it in step.

  • Centralised inventory visibility

    Every sellable unit — a slot, a seat, a permit, a vehicle, a room — lives in one place with one availability answer.

  • Synchronised workflows

    Booking, access and back-office processes read and write the same records, so state does not drift between systems.

  • Configurable integrations

    ERP, finance, CRM, hardware and messaging systems connect through configured integration points during onboarding.

Integrations with SAP and other enterprise systems are configured per deployment. Nothing is connected until it has been scoped and tested with your team.

Integration approach
ERP / SAP
Payment gateways
Gates & turnstiles
Kiosks & POS
CRM & messaging
Partner channels
Financials, GST & tax

Money you can follow back to the gate.

Every collection, refund and allocation keeps its link to the booking, the channel and the entry it belongs to — so reconciliation is a query, not an investigation.

  • Payment visibility

    See what was collected, by which channel, against which booking — as it happens.

  • Tax and GST workflows

    Capture the tax fields each transaction needs, with structured records ready for your filing process.

  • Reconciliation

    Match gateway settlements against bookings and flag the differences that need a human.

  • Real-time reporting

    Operational and financial views built on the same records, not on a nightly export.

Payments & settlements
Settlement runState
  • Direct web salesSettledReconciled
  • Kiosk & counterSettledReconciled
  • Agent channelPendingIn review
  • Partner marketplaceScheduledNext run
  • Refunds & adjustmentsSettledPosted
Traceability
Transaction to entry

Every line keeps its origin.

Cadence
Continuous, not nightly

Reporting reflects the live state.

Venue partner payments

One collection. Every share where it belongs.

Define who earns what, once. Each transaction then carries its own allocation — through settlement, statements and reporting.

Single visitor transaction

One collection

Captured at web, kiosk, counter or partner channel

  • Venue

    Base share

    Rule-based allocation

  • Operator

    Service share

    Per experience delivered

  • Vendor

    Fee share

    Tiered or fixed

  • Platform

    Processing

    Transparent on every line

  • Configurable split workflows

    Percentage, fixed and tiered rules per partner, product and channel.

  • Settlement visibility

    Partners and finance see the same statement, built from the same lines.

  • Traceable transactions

    Each allocation points back to the booking that generated it.

Partner payment splits
Visitors laughing on a theme park ride
Visitors arriving at an attraction entrance
Visitor satisfaction

Fewer friction points, from booking to goodbye.

Most complaints are made before anyone reaches your team: a confusing booking, an unclear slot, a queue nobody warned them about. Those are operational problems with operational fixes.

  • Booking that takes a minute

    Clear availability, clear rules, and no dead ends on a phone in bright sunlight.

  • Refunds and changes with a path

    Amendments, cancellations and refunds follow configured workflows so staff never have to improvise.

  • Feedback where it happened

    Surveys triggered by the actual visit, routed to the team that owns that experience.

  • Experience monitoring

    Watch sentiment by site, session and experience rather than as one monthly average.

“A visitor judges the day at the slowest point of it.”

Operating principle behind the visitor experience module
Visitor experience
Network cabling in a dimly lit server room
Security within

Security is a property of the platform.

Access rights, identity checks and audit trails are part of how the product works — not a hardening exercise bolted on before launch.

Verify identity

Security posture

  • Web application firewall

    Integration points for WAF and edge protection in front of public surfaces.

  • Identity & verification

    Identity verification workflows, including Satyapan-style checks where a deployment requires them.

  • Access controls

    Role-based permissions, scoped to site, zone, shift and function.

  • Monitoring & auditability

    Operational events are logged with the actor, the device and the time.

Security capabilities described here are platform features and integration points. Specific firewall, identity and monitoring providers are selected and configured per deployment; no certification or third-party connection is implied by this page.

People, fleet & guides

The people who make the destination work.

Rosters, vehicles and guides are operational inventory too. Zipr plans them, deploys them and checks them at the same gate as everyone else.

Staff

  • Rosters by site, zone and skill
  • Shift check-in and attendance
  • Certification and document expiry
  • Shift-linked access rights

Vehicles

  • Vehicle and driver assignment
  • Drives, shuttles and transfers
  • Location against the planned route
  • Availability and maintenance states

Guides

  • Language and specialisation matching
  • Tour and drive allocation
  • Rating and feedback history
  • Permit and zone eligibility
AssignedChecked inAt gateOn routeReturnedSettled

  • Assignment workflows

    Plan, publish and adjust without a spreadsheet.

  • Operational permissions

    Access that expires when the shift does.

  • Tracking against plan

    See deviation, not just position.

  • Coverage reporting

    Cost, coverage and no-show visibility by site.

Workforce managementVehicle & fleet
Helpdesk & escalation

Every request has an owner and a clock.

Visitor questions and operational faults arrive through different doors and end up in the same place: a queue with a role attached and an escalation path that holds.

QueuesOwner
  • Gate & access issuesPendingDuty manager
  • Refunds & amendmentsPendingFinance desk
  • Partner enquiriesScheduledCommercial
  • Facilities & safetySettledOperations
Resolution trailToday
  1. 09:12Scanner offline at Gate 3Raised by gate steward, auto-routed to operations.
  2. 09:14Backup validation enabledEntry continues on the adjacent lane.
  3. 09:31Escalated to duty managerNo resolution inside the configured window.
  4. 09:58Device replaced, queue clearedClosed with cause recorded against the asset.

  • Messaging integrations

    Requests arrive from the channels visitors already use.

  • Escalation matrices

    Time-bound, role-based and configurable per site.

  • Support dashboards

    Open, ageing and breached, at a glance.

  • Request tracking

    A full history against the asset, site or booking.

Helpdesk & escalation
The platform

Modules that fit your needs.

Start with the part of the operation that hurts most. Add the rest when you are ready — the records underneath are already shared.

Explore Modules