Dit zijn de vragen die we het vaakst krijgen voordat teams zich aanmelden. Als jouw vraag er niet bij staat, reageert ons ondersteuningsteam op werkdagen binnen enkele uren.
+
No, and it shouldn't. It handles the repeated, factual questions — hours, prices, accessibility, how to book groups — so your team has more time for the conversations that need a real person. Membership renewals, patron-level donations, complaints and any sensitive enquiry should still go to a human, and Live Chat on Business plan and above makes that handover smooth.
+
Not directly. FastBots can explain how timed-entry works, quote prices and point visitors to your ticketing page, but it doesn't hold inventory and won't promise availability for a sold-out show. For Tessitura, Spektrix, Ticketsolve or any other ticketing platform, the chatbot is best used as a guide that hands visitors over to the live booking flow.
+
It's trained to answer from your website and the manual Q&As you add. You can set its fallback so that when it doesn't know — for example, a question about an artwork's provenance you haven't published — it says so and offers to take the visitor's details rather than guess. We strongly recommend turning off live internet search for curatorial questions so it doesn't pull attributions from random websites.
+
It answers from your accessibility page in the same plain language it uses everywhere else — step-free routes, lifts, sensory-friendly hours, BSL tours, large-print materials, assistance-dog policy. Visitors often prefer asking a chatbot privately rather than ringing the front desk, especially for questions about sensory needs or mobility. Keep your accessibility page up to date and the chatbot will follow.
+
Yes. The lead form can ask for the date range, year group or key stage, group size, learning focus and teacher contact details, then email the enquiry to your learning team. You can also push it into a CRM or shared spreadsheet through a Zapier or Make workflow once the chat ends, so it lands in the system your team already uses.
+
Yes — FastBots supports around 95 languages. A French school teacher or a Japanese tourist can ask in their own language and get a sensible reply from your English-language content. It's not a substitute for a properly localised site, but for visit-planning questions it works well.
+
Conversations are stored in your FastBots account so you can review what's being asked. FastBots states that uploaded data is not used to train OpenAI models through the API connection and its data handling is GDPR compliant. Keep your lead form to what you actually need — name, email, group size — rather than collecting more than necessary.
+
FastBots doesn't have native integrations with museum-specific systems like Tessitura, Spektrix or Ticketsolve. What you can do is use Zapier or Make to forward captured enquiries — group bookings, membership leads, hire requests — into whichever system your team uses, so the chatbot becomes the front door rather than a separate inbox.
+
The free plan includes one chatbot and 50 messages a month, with no credit card required, which is enough to test on your visit page. Paid plans start at $39/month for Essential. Live Chat, Auto Retrain, Knowledge Assistant and Email Replies are on the Business plan at $89/month — that's the tier most museums with an active visitor-services team end up on.
+
Yes. Setup is no-code: point it at your website, write a short set of house rules, paste the embed snippet into your CMS. Most of the ongoing work is reading conversations once a week and adding Q&As for things visitors ask that aren't on your site — which is honest, useful work any visitor-services lead can do.