--- title: "Chatbot: answers from your own pages | Briks" url: https://briks.dev/docs/chatbot description: "Switch on a chat that answers visitors from your published pages, passes what it cannot answer to a verified email, and keeps every chat for you to read." last_updated: 2026-10-08 --- # Chatbot: answers from your own pages The chatbot puts a small chat button on every page of your published site. It answers questions using only what your pages say, and when it can't, it offers to pass the question to you by email. It's off until you switch it on, and every plan has it. 9 minute read Checked against the studio on 8 October 2026 ## Before you start - **The site must be published.** The chatbot reads your pages each time the site is published, so a site that hasn't been published gives it nothing to read. - **Answers don't use your credits.** There is a daily cap instead, covered under Limits below. - **Hand-offs go to a verified address only:** a workspace member's sign-in address, or an outside address whose owner has confirmed it. - **Every conversation is kept for you** for 90 days after its last message, under **Settings**, **Chats**. - **Who can do what:** Owners, Admins and Editors can switch it on, change it and read the chats. Adding outside addresses is for Owners and Admins. ## Switch it on Where 1. Projects 2. Your project 3. Chatbot 1. Open the Chatbot tab Where: Top bar Click **Chatbot** in the row of tabs under your project's name. The page opens with a card headed **Chat widget on** your site's address. 2. Turn on the switch Where: Enable chatbot It sits at the right of that heading. It's off for every new project. 3. Pick a tone Where: Tone **Friendly** is warm and plain, **Concise** is brief with no small talk, and **Formal** is polite and formal. Friendly suits most small businesses. 4. Choose who gets hand-offs Where: Hand off to The list holds verified addresses only: you first, then Owners and teammates, then outside addresses that have been confirmed. 5. Choose how it opens Where: How it opens Optional. Set its words' language, its title, its opening line, the questions visitors can tap and where the button sits. The section below covers each. 6. Save Where: Save Click **Save**. The chat appears on the live site within a minute, with no need to publish again. 7. Check what it read Where: What it knows This card says how many pages it read, how many characters, and when. If it says nothing has been read yet, the chat learns your pages at the site's next publish. ## How it opens The **How it opens** part of the card sets what visitors see before they type anything. A **Preview** beside the card shows the chat in your site's own colours, with **Light** and **Dark** to see it on either background. Anything you leave empty falls back to a sensible default, shown greyed out in the field. | Setting | What it does | | --- | --- | | **Language of its words** | The language of its buttons, prompts and greeting, one of 12. Answers always follow the language each visitor writes in. | | **Title** | The name at the top of the chat window. Left empty, it is the site's name. | | **Opening line** | What the chat says first. Left empty, it says “Hi. Ask anything about” and your site's name. | | **Questions to tap** | Up to four questions shown under the opening line until the visitor asks something. Left empty, they come from the questions and pages on your site. | | **Label on the button** | Switch on **Show a label on the chat button** to put a few words beside the round button. Left empty, it says “Chat with us”. | | **Side** | **Left** or **Right**: which bottom corner the button sits in. | ## Add a shared inbox for hand-offs If questions should go to an inbox that isn't a workspace member, such as a front desk or bookings address, add it under **Other addresses** on the same card. 1. Type the address Where: Other addresses Enter it in **Email address** and click **Send confirmation link**. 2. Confirm it from the inbox Where: The inbox Briks emails a link that works for 48 hours. Until someone opens it, the address shows **Waiting for confirmation**. If the link runs out, use the button beside the address to send it again. 3. Choose it Where: Hand off to Once it shows **Verified**, pick it in **Hand off to** and click **Save**. | Plan | Outside addresses you can add | | --- | --- | | Free | 1 | | Starter | 1 | | Pro | 3 | | Studio | 10 | | Agency | 30 | One for each project the plan allows, shared across the workspace. Members' own addresses don't count towards it. The card shows how many you have added, such as “1 of 3 added”. At the limit, the form gives way to a note: “You have added as many addresses as your plan allows. Remove one, or move to a larger plan.” **Remove** takes an address off the list. ## What visitors see A round chat button sits in a bottom corner of every page, the right one unless you chose **Left**, in your site's own colours and typeface, light or dark as the site is. Opening it shows the title, the opening line and the questions to tap. - Visitors type a question, or tap one, and see moving dots while the answer is written. - A **Talk to a person** link at the top takes them straight to the hand-off form. - When the chat isn't sure, it says so and shows **Send this question to the team**. - The hand-off form asks for **Your email** and **Your question**, then says “Sent. The team will reply to” followed by their address. - On the visitor's side, the conversation lives in that browser tab only and is gone when they close it. Your copy is kept in the studio (see Every chat, below). ## What it will and won't answer The chatbot has no knowledge of its own and no separate list of answers to fill in. It reads the words on your published pages and keeps to them. - **It will** answer from anything your pages say: services, prices, opening hours, areas covered, how to book. - **It will** reply in the language the visitor writes in, in one to four short sentences, in the tone you chose. - **It won't** invent prices, opening hours, availability, policies, people, addresses or contact details. If no page says it, the chat says it isn't sure and offers a hand-off. - **It won't** chat about things unrelated to your business; it declines politely. - **It won't** say how the site or the chat was made. - **It only reads words.** Text inside pictures isn't read. It reads up to about 60,000 characters across the site, home page first and at most 14,000 from any one page, so on a very large site the last pages may be cut short. If you use [AI agents](https://briks.dev/docs/ai-agents), the chat can also answer from what they know about the business, once you share those facts with it from the agents' **Memory**. The Chatbot tab says how many shared facts it has. ## Hand-offs A hand-off is a question the chat passes to a person. When the chat can't answer, or the visitor asks for a human, it offers to send the question on, and the visitor leaves their email address with it. You get an email titled “New question from” your site's name, with the question and the conversation before it. Reply to that email and your answer goes straight to the visitor. The bell in the studio tells you too: “A visitor to” your site “asked for a person”. The question also appears under **Questions passed to you** on the Chatbot tab (the latest 20), marked **email not sent** if the email failed. The weekly analytics email counts them too. A hand-off that reads as spam is kept and marked **Likely spam**, with **held, not emailed** beside it, and nobody is told. If it is a real question, an Owner, Admin or Editor presses **Not spam** to take the mark off. Nothing is emailed late, so reply to the visitor yourself from the address shown. ## Every chat Where 1. Projects 2. Your project 3. Settings 4. Chats **Every chat**, at the top of **Questions passed to you**, opens **Chats**: every conversation visitors had with your site's chat in the last 90 days, newest first, 50 to a page. Each row shows **When**, the **First question**, the number of **Messages**, the **Page** it started on and the **Country**, with a **Passed to you** tag on those the visitor sent to the team. Click the first question to read the whole conversation as plain text. - **Search.** Type in **Words in a chat** to find conversations that mention a product, a price or a name. - **Export CSV** saves the conversations as a spreadsheet file. - **What is kept.** The visitor's messages and the replies the chat really gave, up to 200 turns a conversation. A conversation is removed 90 days after its last message. - **Who can read them.** Owners, Admins and Editors. Viewers cannot open the Chats section. Read the chats for gaps Questions the chat answered vaguely, or that visitors asked twice in different words, are the facts your pages are missing. They make the best changes to ask for next. A hand-off A physiotherapy clinic in Bristol > A visitor asks: “Can I claim your sessions on my health insurance?” The site lists treatments and prices but says nothing about insurers. The chat says it isn't sure and offers **Send this question to the team**. The clinic's front desk inbox gets the question, set to reply to the visitor. ## Make its answers better The chat only knows your pages, so the way to improve it is to improve the pages. Every hand-off is a gap on your site. 1. Collect the gaps Where: Questions passed to you Read the list, and **Every chat**, every week or so. Questions that come up twice belong on the site. 2. Ask for a change Where: Studio Describe the missing facts in plain words. A change holds 5 credits and is charged for the work it takes. 3. Check after it publishes Where: What it knows The date on the card updates with the publish. Ask the chat the same question on your live site. A change request Closing the insurance gap > Add a short questions section to the Prices page: we're registered with most major health insurers, patients pay us and claim the money back, and we email a receipt after every session. Once published, the chat answers the insurance question from that section instead of handing it off. ## Limits | Limit | What visitors see when it's reached | | --- | --- | | 400 questions per site a day | “The chat is resting for today. Please use the contact details on this site.” | | 20 messages per visitor in 10 minutes | “You have sent a lot of messages. Try again in a few minutes.” | | 5 hand-offs per visitor an hour | “You have sent a few already. The team will reply by email.” | | 100 hand-offs per site a day | “This site has passed on many questions today. Try again tomorrow.” | Every question a visitor sends counts once towards the 400, so a conversation of five questions uses five. A visitor's message is read up to 1,000 characters. ## Turn it off Turn the switch off on the Chatbot tab and click **Save**. The button leaves the live site within a minute. Questions already passed to you stay listed, and past conversations stay under **Chats** until their 90 days are up. ### Can I read every conversation? Yes, for 90 days after its last message, under **Settings**, **Chats**, if you are an Owner, Admin or Editor. Analytics also counts the first question of each conversation under **Enquiries**, without its words. ### Does it work on my own domain? Yes. It loads on every page of the published site, at your own domain as well as the preview address. ### It gave a wrong answer. What now? It answers from your pages, so check what the page says first. If the page is right, add a clearer sentence or a short questions section and publish. ### Does it cost anything? No credits. The daily cap of 400 questions per site is the limit. ## Read next - [Your site's features **Analytics** See who visits your site, where they come from and what they do, counted without cookies. Ask about your visits in plain words, set goals and get weekly emails.](https://briks.dev/docs/analytics) - [Working on a project **Making changes** How to change your site by writing to Briks: what to say, adding pictures, what a change holds and costs, inner pages, queued requests and fixing a miss.](https://briks.dev/docs/making-changes) - [Workspaces and account **Members and roles** Invite people by emailed link and give each one a role: Owner, Admin, Editor or Viewer. See what each role can do and how many people each plan holds.](https://briks.dev/docs/members-and-roles) - [Your site's features **Forms** Add a form to your Briks site, test it in preview, find every entry in the studio, get each one by email in production and pass them on with a webhook.](https://briks.dev/docs/forms) Still stuck? Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.