# Free AI chatbot for websites

Everything you used a form or a survey for, asked in a conversation instead. What comes back is a clean, typed record your stack can act on, not a transcript. Free to start, live in five minutes.

## Five jobs, one chatbot

Same machine, same line. Picking a job only changes what it is trying to find out, and therefore what comes out the other end.

- **Answer For Me**: Hand over the questions you answer on repeat - hours, pricing, policies, how things work. It answers from what you gave it, and when it does not know, it says so and passes the question to you.
- **Lead Qualifier**: Qualifies visitors in conversation instead of a form, against your own criteria - need, budget, timeline, fit - and hands you the ones worth your time.
- **Collect From Many**: Everyone gets the exact same questions, so the answers line up - one row per person. Vendor quotes, RSVPs, references, testimonials.
- **Ask Someone**: Write the questions once, send the link to whoever has the answers, and get them back as clean structured fields instead of a mail thread.
- **Recurring Check-in**: Set the questions once and reuse the same link every time - weekly team updates, monthly client status, post-visit follow-ups. Each round comes back comparable to the last.

## On your site, or a page of its own

Both of these are live right now. Same Gnosari underneath, same questions, same record at the end. All that changes is where someone meets it.

- **The widget on your site**: A button in the corner that opens into a conversation. Your logo, your colours, sitting on the pages you already have.
  - One line of HTML, anywhere on your site
  - Bubble, sidebar, sidebar-push or drawer
  - Opens over the page, closes again
- **A page of its own**: No chat window and no widget. Your headline leads, the thread sits under it, and it reads like you asked rather than like software collecting.
  - Sent as a link, or scanned from a QR
  - Its own headline, caption and greeting
  - Every link counted separately
  - One responsive page: phone, tablet or desktop

## One snippet, four ways to wear it

Paste one line of HTML anywhere on your site. How the widget sits on the page is a setting, not a rebuild, and you can change it after you ship.

- **Bubble**: A floating button in the corner. Opens over your page and closes again. The default, and the one nobody has to be taught.
  - Four corners to choose from
- **Sidebar**: A fixed panel down one side, always open. For pages where the conversation is the point rather than an aside.
  - Left or right, any width
- **Sidebar push**: The same panel, but your content moves over to make room instead of being covered. Nothing on the page is ever hidden.
  - Left or right, any width
- **Drawer**: Slides in over the page when it is called, then slides away. The middle ground between a bubble and a sidebar.
  - Left or right

## Name the fields. It does the asking.

You never write a question. You write down what you need to know, and the chatbot works out how to get it in conversation.

- **01 · What you write down**: Seven types. Every value that comes back is validated against the one you picked, so a date is a date and a number is a number.
- **02 · How it should ask**: One line of plain English per field, and only where you want one. It is the difference between an interrogation and a conversation.
- **03 · What lands**: Typed, validated, and carrying the exact words it came from. Nothing the visitor did not say is ever stored.

An example schema, and the type every returned value is validated against:

| Field | Type | Required |
|---|---|---|
| Full name | text | yes |
| Email | email | yes |
| Phone | phone | no |
| Budget | number | no |
| Move-in date | date | no |
| Has pets | boolean | no |
| Must-haves | list | no |

ai_hint on “Budget”: “A range is fine. Never push if they decline.”

It asks: “Roughly what were you hoping to spend? A ballpark is completely fine.”

## One inbox, not four hundred transcripts

Every conversation that produced something useful arrives here as a row you can read in two seconds. Filter by chatbot, mark it handled, or take the whole thing as a CSV.

Every value keeps the sentence it came from, and a value the visitor never said is never stored. The chatbot cannot quote itself into your data.

From here a record can go straight on to Slack, a sheet, a Zap or your own API. The inbox is where you read them, not where they get stuck.

## Your stack gets the record, not another login

The moment a conversation produces something useful, Gnosari posts it to whatever address you give it. Signed, versioned and retried. From there it is a webhook, which means it reaches almost anything you already run.

- **Two events**: data.collected fires the first time a Gnosari collects a new kind of data. data.updated fires when a record changes, which is the one an audit trail cares about.
- **Signed, so you can trust it**: Standard Webhooks HMAC-SHA256, with webhook-id, webhook-timestamp and webhook-signature on every request. Verify before you write anything to your own database.
- **Retried, and logged either way**: A failed delivery retries on its own and the dashboard keeps every attempt with the reason it failed. Quotes from the conversation ride along only if you turn them on.

The three routes out:

- **Zapier or Make**: Paste a Catch Hook URL into your Gnosari destination. That is the whole setup. Free tier, no Gnosari app to install, and it fires instantly rather than on a poll.
  - Reaches, for example: Salesforce, HubSpot, Mailchimp, Zoho, Calendly, n8n
- **Straight to the tool**: Anything that accepts an incoming webhook takes the payload as it is. No middleman and no per-task billing. You map the fields once.
  - Reaches, for example: Slack, Teams, Notion, Airtable, Sheets, Discord
- **Your own endpoint**: Give us an https address, verify the signature, write it wherever you like. A few lines of code, and the delivery log tells you when something did not land.
  - Reaches, for example: Postgres, Supabase, BigQuery, Snowflake, Retool, Twilio

Every attempt is kept, newest first, with the reason when there is one. Failures retry on their own, and the signing secret lives in your dashboard so you can rotate it without calling anybody.

These are examples, not a partner list. A webhook reaches anything that accepts one, and Zapier and Make cover several thousand more between them. If your system takes an HTTP request, it takes a Gnosari record.

## Every conversation, already read

You are not going to read six hundred transcripts, so each one arrives summarised: what they wanted, what it was about, how it went, and what somebody needs to do next.

The summary is written from the conversation, not from the fields, so a visitor who asked three questions and never left a detail still tells you something. Those are the ones that never reach a form.

## Your brand, down to the font

Nobody should be able to tell it is us. Start from a curated look, mix your own colour and pattern, or set every design token yourself: every surface follows, from the widget to the conversation page to the link someone opens on their phone.

- **01 · Start from a preset**: Twelve curated looks, each a colour and a background pattern chosen to go together. Pick one and you are done.
- **02 · Or mix your own**: 22 colour themes and 44 background patterns, each drawn in code at four intensities. That is 3,872 combinations before you touch a single token.
- **03 · Or set every design token**: Exact hex values, fourteen fonts, bubble shape per side, corner radius, density, header and input. Explicit tokens always win over the preset. Two chats can share every line of markup and still wear two different brands: only the tokens differ.

The twelve preset themes and who they suit:

- **plain**: Corporate or formal, or let the content lead
- **clean-dots**: SaaS, B2B, dashboards
- **ocean-waves**: Wellness, travel, spa
- **forest-topo**: Outdoors, sustainability, eco
- **blueprint**: Engineering, dev tools, architecture
- **graph-paper**: Education, finance, analytical
- **circuit**: Tech, hardware, AI, electronics
- **soft-bubbles**: Friendly, lifestyle, community, care
- **sunset-glow**: Creative, marketing, bold consumer
- **emerald-grid**: Health, growth, productivity
- **confetti**: Events, kids, playful brands
- **mono-noise**: Media, publishing, premium and minimal

fontFamily accepts: Inter, system-ui, Roboto, Open Sans, Lato, Montserrat, Poppins, Source Sans 3, Nunito, DM Sans, Lora, Playfair Display, JetBrains Mono, Space Grotesk.

Set with one call, or one click in the designer. Changing it later takes the same one call, and every published surface updates at once.

## It answers from your content, and admits when it cannot

Give it your website and it reads it. Everything it tells a visitor comes from something you published, and when the answer is not in there it says so and hands the question to you.

- **Your website**: Paste the address. It looks for a sitemap, and if there is not one it finds the pages itself.
  - Auto-resolves to sitemap or discovery
- **A sitemap you name**: Point it at the exact sitemap when you want to control precisely which pages it reads.
  - You choose the crawl
- **A single page**: One URL, read on its own. For a pricing page or a policy that changes on its own schedule.
  - No crawl at all

The rule is enforced in code, not in a prompt: a value is only ever stored when it can be traced to something the visitor actually said. The chatbot's own words can never become your data.

## Not every conversation starts on a website

The same Gnosari, reached three other ways. A link, a code, or a piece of paper. All of them land in the same record.

- **01 · A link you send**: Put it in an email, a text, a booking confirmation or a signature. Each link carries its own opening line and headline, and counts its own visits, so you can tell which channel actually worked.
  - Its own greeting and headline
  - Optional expiry date
  - Counted separately
- **02 · A code they scan**: Every link comes with a QR. On a table card, a receipt, a delivery note, a door. Someone points a phone at it and the conversation starts, with no app and no typing.
  - PNG or SVG, print resolution
  - Points at the same slug
  - Old printed codes keep working
- **03 · A flyer you hand over**: A builder for the printed thing itself. Pick a template, restyle it, edit the words on the page and export a print-ready poster or card with the QR already placed.
  - Posters, cards and flyers
  - Print or PNG export
  - No account needed

## How hard it asks

One dial on your chatbot, four positions: from never asking a question to asking until every field is filled. Same visitor, same fields, four speeds.

The dial runs from "never asks" to "asks until every field is filled", and the same visitor gets a different reply at each position:

- **Passive**: That sounds like a big change. What is drawing you away from where you are now?
- **Opportunistic**: A quieter spot with room for four, got it. Roughly when are you hoping to move?
- **Active**: Lovely. So I can send the right places, what is your monthly budget?
- **Guided**: Thanks. First question of six: which areas are you considering?

Guided is the only position that takes a script of your own. The other three write their own questions from the fields you named, and every position writes the same record.

## Behaviour you write once, and stop rewriting

A trait is one rule about how the chatbot conducts itself, kept in your library and attached to whichever Gnosaris need it. Change the rule once and every chatbot wearing it changes with it.

The five traits every account starts with:

- **One Question at a Time**: Asks a single question per message - never dumps a checklist
- **Stays On Topic**: Politely refuses off-topic requests and steers back to its purpose - won't be used as a general chatbot
- **Conversational Close**: Ends an intake conversation cleanly - recaps captured details, confirms, states next step, then stops
- **Conversational Readability**: Short, scannable chat messages with a clean bolded recap, without turning replies into a formatted document
- **Acknowledge and Keep It Short**: Reflects back what the visitor said, then responds in 2-3 sentences

How traits behave together:

- **Weight settles arguments**: Two traits that want different things do not fight at random. The heavier one wins, which is why a chatbot told to be thorough still asks one question at a time.
- **Written once, worn by many**: The same trait can sit on every Gnosari you run. Edit it in the library and the change reaches all of them, without opening a single one.
- **You start with these**: Every account gets the five above on day one, and four are already attached to anything you create. Nobody has to write a personality from an empty box.

## Or just ask Claude to build it

Gnosari is an MCP server, so the assistant you already have open can create a chatbot, point it at your site, set how it behaves and publish the link. You describe it once, in a sentence, and never open our app.

You ask: “Build me a chatbot for my dental practice that books first visits. Read oaklinedental.com, collect name, phone, insurance and whether they are nervous, then give me the link.”

It calls the tools:

- **Create Gnosari**: Name, purpose, the fields to collect
- **Manage Knowledge**: Points it at your website
- **Manage Traits**: Attaches how it should behave
- **Manage Agent Links**: Publishes a link and a QR

Paste it into your client's connector settings. Sign in to Gnosari when it asks. There is no key to copy and nothing to install.

## Built by people who do not build chatbots

The people getting the most out of this are not engineers. They are the ones answering the same question forty times a week.

- **Restaurants** ([setup](https://gnosari.com/for/restaurants), [markdown](https://gnosari.com/for/restaurants.md)): Bookings, dietary notes and covers, without the phone ringing
- **Dental practices** ([setup](https://gnosari.com/for/dental), [markdown](https://gnosari.com/for/dental.md)): New-patient intake finished before they sit down
- **Property managers** ([setup](https://gnosari.com/for/property-management), [markdown](https://gnosari.com/for/property-management.md)): Viewing requests qualified on budget, beds and move-in
- **Law firms** ([setup](https://gnosari.com/for/legal), [markdown](https://gnosari.com/for/legal.md)): Enquiry triage that never gives legal advice
- **Gyms and studios** ([setup](https://gnosari.com/for/fitness), [markdown](https://gnosari.com/for/fitness.md)): Trials booked and cancellations understood, not just processed
- **Salons** ([setup](https://gnosari.com/for/beauty-salon), [markdown](https://gnosari.com/for/beauty-salon.md)): Treatment, stylist and time captured in one thread
- **Hotels** ([setup](https://gnosari.com/for/hospitality), [markdown](https://gnosari.com/for/hospitality.md)): Post-stay feedback people actually answer
- **Insurance** ([setup](https://gnosari.com/for/insurance), [markdown](https://gnosari.com/for/insurance.md)): First-notice-of-loss taken properly, day or night

Not on the list? The setup is the same whatever the trade: name the fields, point it at your site, share the link.

## The questions everyone asks

Answered here rather than hidden behind a tap, because the one you care about is probably not the first one.

**Do I need to write the questions?**

No. You write down the fields you want and the chatbot works out how to ask for them in conversation. The only mode that takes a script you wrote is Guided, and it is there for intake that has to happen in a fixed order.

**What stops it making things up?**

Two things, both enforced in code rather than in a prompt. It answers from the content you gave it and says so when it does not know. And a value is only ever stored when it can be traced back to something the visitor actually said, so the chatbot's own words can never end up in your data.

**Where does the data go?**

Into your dashboard as typed records the moment the conversation happens. From there it can reach your CRM, a spreadsheet or your own API through a webhook. There is no export step to remember.

**Can it send the data into Zapier, Make or my own system?**

Yes, through an outbound webhook. When a record is complete Gnosari posts a signed JSON payload to any address you give it, so a Zapier Catch Hook or a Make custom webhook reaches several thousand tools with no app to install on either side. Requests are signed with HMAC-SHA256 and every attempt is retried and logged.

**What happens if my endpoint is down when a record arrives?**

The delivery retries on its own, and the dashboard keeps every attempt with the outcome and the reason it failed. The record itself is never lost: it is already in your inbox, and the delivery is a separate thing that either lands or tells you why it did not.

**Does it look like Gnosari or like us?**

Like you. Twelve curated looks, your logo, your colours, your headline, on the widget and on the conversation page. The only Gnosari mark is a small "Powered by" line.

**What if someone asks something it should not answer?**

It hands the question to you rather than guessing. That is the same mechanism as the "when it does not know" case, and it is why regulated trades can use it: it is built to decline rather than improvise.

**How long does setup actually take?**

Minutes for the first working version: name the fields, paste your website address, share the link. Refining the questions and the look is something you do afterwards, on a live chatbot, without rebuilding anything.

**Do I need a developer?**

Only if you want the widget on your own site, and even then it is one line of HTML pasted once. A link or a QR code needs nothing technical at all.

**What does it cost?**

It is free to start, with no card. The paid plans and their limits are listed below.

## Free to start, and free to stay small

No card to begin. You only pay when the conversations are worth paying for, which is a decision you get to make after it is already working.

Build a chatbot, publish it, collect real records. No card, no trial clock.

## Five minutes from now you could have one collecting data.

Free to start, no card, and it is answering on your site before your coffee goes cold.

Pricing: https://gnosari.com/pricing
Full page: https://gnosari.com/