It stays inside its scope
Topics, data sources and actions are configured per deployment. Outside that scope it hands over rather than improvises.
Strawberry AI
Assistive, not autonomous.
Strawberry answers visitor questions from your content and your live availability, and gives your team a plain-language way to ask the operation what is going on.
- Grounded in
- Your content and availability
- Scope
- Configured per deployment
- Hand-over
- To a human, at any point
- Oversight
- Logged and reviewable
How it works
It reads your operation, not the internet.
Strawberry is scoped to what you publish and what your inventory says is available right now. That is a deliberate limit: an assistant that invents an opening hour is worse than no assistant.
When a question falls outside that scope — a complaint, an exception, anything needing judgement — it hands the conversation to a person with the context attached.
Grounded
Answers come from your content and live availability.
Scoped
Topics it may and may not address are configured.
Supervised
Conversations are logged and reviewable.
For visitors
The questions people actually ask.
Not "what are your opening hours" — but "can we fit both in on Saturday, with two children, arriving at ten".
Conversational assistance
In the visitor’s own words.
Discovery
The right experience for the day they have.
Plan my day
Built around capacity that actually exists.
FAQs
The same answer on every channel.
The exchange above is illustrative. Transactional scope — whether the assistant may hold or complete a booking — is configured per deployment.
Strawberry AIIllustrative
Is the evening drive still open on Friday? We are four adults.
Friday’s 16:00 drive has two seats left; 17:30 has six. Both leave from the main gate and return before dusk.
Take 17:30. Anything we should know before we arrive?
Arrive 20 minutes early for permit checks, bring photo ID for each adult, and expect no mobile coverage inside the zone. Shall I pass you to booking?
For operators
A copilot for the people on duty.
Operations teams already know what they want to ask: which gate is slowest, which drives are under-filled, which escalations are about to breach. Getting that answer usually means finding the right report.
Strawberry turns those questions into queries against the same records the dashboards use — and shows its working, so an answer can be checked.
Ask in plain language
Operational questions, answered from live records.
Draft and route
Suggested replies and escalation routing for the helpdesk.
Narrate the day
Day-end and season summaries written from the data.
Where it shows up
Across the visitor journey.
Before arrival
Questions answered on the channel they asked
At the kiosk
Help without a queue
On site
Wayfinding and session prompts
With the team
Drafting and routing support replies
After the day
Summaries written from the records
Safeguards
What it will not do.
Limits are part of the product, not a disclaimer bolted on afterwards.
It hands over to a person
Complaints, exceptions and anything needing judgement go to a human with the conversation attached.
It leaves a record
Conversations are logged for review, subject to the retention rules you set.
It does not decide data access
What Strawberry can read is governed by the same permission model as the rest of the platform.
See Strawberry answer your questions.
Bring the ten questions your front desk answers most often. We will scope an assistant against them.