The ones we hear most before teams sign up. If yours isn’t here, our support team replies within hours during business days.
+
No, and it shouldn't. FastBots is best at the high-volume, repetitive questions (hours, cards, renewals, room booking, kids' programming). Real reference work, account lookups and anything requiring judgement still belong with a librarian. Live Chat on the Business plan ($89/month) lets staff step in when a patron needs a person.
+
Not directly; FastBots doesn't have native integrations with Koha, Polaris, Sierra or BiblioCommons. The right pattern is to have the bot point patrons to your catalogue search with a link, and explain how to place a hold once they find what they need. That keeps live availability where it should be: in the catalogue itself.
+
Set the bot's house rules to never ask for library card numbers, PINs or full addresses. The chatbot is for general information and triage, not account access. For anything account-specific, the bot should point patrons to logging in to the catalogue or contacting the circulation desk.
+
Yes. FastBots supports around 95 languages, so a patron can type in their preferred language and the bot will reply in the same language. That's particularly useful for branches serving multilingual communities where the website itself may only be in English.
+
Once it's trained on your programming pages, the bot can answer what's on, age ranges, whether registration is required and where to sign up. If a session needs sign-up, the bot collects the parent's name and email through the lead form and emails the enquiry to the children's team.
+
The bot is told in its house rules to refer detailed research to a librarian rather than guess. On the Business plan, Live Chat lets a librarian claim the conversation and help directly. Otherwise, the bot captures the question and the patron's contact details and emails the reference desk.
+
Yes. FastBots adds a small embed snippet to your site; there are documented installation routes for WordPress, Drupal, Squarespace, Wix, custom HTML sites and plenty more. If you can edit your site's template, you can install it.
+
Not natively, and we wouldn't claim that. The bot can explain the booking rules, capture a request with the patron's preferred time and contact details, and email it to staff to confirm. If you use Zapier or Make, captured requests can be pushed into a spreadsheet or workflow once the chat ends.
+
New FastBots accounts start with a 14-day free trial, not the legacy Free plan. It includes 1 chatbot and a one-time allowance of 200 message credits, with no credit card required; different AI models use credits at different rates. You can try the main chatbot features and integrations, except Reseller white-labelling and scheduled automation. When the trial ends, the chatbot goes offline and no test credits remain until you upgrade, while your dashboard, settings, previous chats and Contacts stay accessible. Paid plans start at $39/month. Existing users who were already on the legacy Free plan return to it after their trial.
+
Around 5 minutes for a working first version. Point it at your library website, crawl the pages that answer the common questions, add a short set of house rules about escalation, and embed the widget. Most of the ongoing work is reviewing chat history and adding Q&A entries for questions the bot didn't quite nail.