GoBrise
AI chatbot for tour and activity operators

AI chatbot for tour and activity operators

Prospective guests ask about weather policy, group size, and what's included before every booking. GoBrise answers those from your own published terms, and hands anything about a specific booking or a weather-cancellation decision to a person.

  • What's included and what to bring repeats before every booking
  • Weather and cancellation policy is asked constantly, especially close to the activity date
  • Group size, age limits, and fitness requirements vary by tour and must be exact
  • A specific booking's weather-cancellation decision needs a person, not a policy quote

Last reviewed 20 September 2026

Quick summary

Procedural

What's included, requirements, group-size limits, and general weather policy — answered from your published tour terms.

Escalate

A specific booking's weather-cancellation call or refund decision goes to a person who can see real conditions.

$0

Unlimited human live chat on the Free plan while you evaluate AI.

24/7

Prospective guests researching at odd hours get an accurate answer before deciding to book.

What people actually ask

Real questions this page answers, drawn from the conversations teams like yours handle every day.

What's included / what should I bring

Equipment provided, what to bring yourself, and any preparation needed — answered from your published tour description.

What happens if it rains / is cancelled for weather

Your general weather policy explained clearly; the actual go/no-go decision for a specific date is made by your team, not the assistant.

Is this suitable for kids / what's the age or fitness requirement

Age limits, fitness level, and any restrictions, answered consistently from your published requirements.

Can I book for a large group

Group-size policy and any group-rate information from your published terms; a specific large booking may need direct coordination with your team.

Can I get a refund if I cancel

Your general cancellation and refund policy explained clearly, with a specific booking's actual refund decision handled by a person.

How it works

  1. Step 1

    Write your weather and cancellation policy precisely

    This is the single most-asked question category in this business — vague policy content produces the most disputes and escalations.

  2. Step 2

    Document requirements per tour or activity

    Age limits, fitness level, and what's included genuinely differ by activity — write each one explicitly rather than one combined page.

  3. Step 3

    Separate general policy from the live go/no-go call

    General weather policy is automatable; the actual decision for a specific date's conditions needs a person with real information.

  4. Step 4

    Install the widget at the booking decision point

    Tour listing and checkout pages are where pre-booking questions cluster, not just the homepage.

  5. Step 5

    Test with real pre-booking and day-of wording

    Pull actual questions, including anxious day-of-weather messages, and confirm policy answers are clear and the live decision escalates cleanly.

  6. Step 6

    Review seasonally and after policy changes

    Weather patterns and group-size rules can shift by season — refresh content before each new season starts.

Who this is — and isn't — for

An honest read on where GoBrise fits, so you can rule it out quickly if it doesn't.

A good fit if

  • Most enquiries are about published terms: inclusions, requirements, group size, general weather policy
  • You want the actual weather go/no-go or refund decision to reach a person every time
  • Your tour requirements and policies are documented per activity and kept current
  • You get meaningful out-of-hours research volume before a booking decision
  • A predictable monthly bill matters more to you than per-conversation pricing

Not the right tool if

  • You want the assistant to make the actual weather-cancellation call — that needs a person with real conditions information
  • Your requirements or policies differ by tour but aren't documented per activity
  • You need it to check a specific booking's real status or process a refund directly
  • Your policies change informally season to season without being reflected in written content
  • You have no team available to make the day-of weather decision when it's needed

Frequently asked questions

Can it decide if today's tour is cancelled for weather?

No — that's a real-time decision your team makes based on actual conditions. The assistant explains your general weather policy, not a specific day's call.

Can it process a refund for a cancelled tour?

No, it explains your refund policy; the actual refund decision and processing stays with your team.

How do we handle different requirements per tour?

Document age limits, fitness requirements, and inclusions per tour rather than one general page — a combined page produces wrong answers for tours with different rules.

Can it handle a large group booking enquiry?

It can explain your group-size policy and capture the enquiry; actual coordination for a large group booking typically needs your team directly.

What if a customer asks about a specific booking's status?

That's escalated to a person — the assistant answers general policy questions, not specific booking lookups.

Can it capture leads from people still deciding?

Yes, using the same lead-capture and handoff actions available across GoBrise.

How often should we update weather and policy content?

Before each season, and any time your actual policy changes — stale policy content is the most common source of disputes here.

Is it white-labelled?

Yes, on Growth and Business plans the widget carries your own branding, no GoBrise mark.

Try it on your own content

Start free with unlimited human live chat, add your content, and judge the answers for yourself.