Bubble
display_mode="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
What changes from one job to the next is what it asks, where it lives, and where the record goes. Pick the job below and you get the exact setup for it.
It greets the visitor, asks what they need, and gets name, email and budget or timeline before you ever reply. Every conversation lands as a lead record you can export or push to your CRM.
It opens with
What comes back
typed · validated · deduped
There is no form to fill in. A build wizard asks what the agent is for and who it talks to, and you answer the way you would brief a new hire: "Capture leads for my real estate agency" or "Collect feedback from my restaurant customers". You can run the same setup from Claude, ChatGPT or Cursor instead, over MCP.
Plain English / No jargon / No code
Point it at your website and it reads what you published, whether that is the whole sitemap, a section you name or a single page. Everything it tells a visitor comes from your own content, and when the answer is not in there it says so instead of inventing one.
Your site / You choose the pages / No invented answers
List what every conversation has to return: name, email, budget, rating, availability, whatever the job needs. The agent asks for them naturally as the conversation goes, and a record counts as complete when it has them.
You choose the fields / Asked as questions / Typed records back
Records land in your dashboard the moment a conversation produces one, and from there Gnosari posts them to any address you give it. That reaches Zapier, Make, n8n, your CRM or your own API, signed and retried, with nothing to install on either side.
Signed webhook / Zapier, Make, n8n / Straight to your CRM
You get an address like joina.chat/your-business. Send it, print it as a QR code, or paste one script tag into your site. Records start arriving on the first conversation.
Instant link / QR code / One script tag
Examples from real users:
display_mode="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
display_mode="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
display_mode="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
display_mode="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
Chat with the live Gnosari right here - no signup needed.
What the eight jobs have in common, and what changes between them.
A working AI agent that does one job for your business: captures leads on your website, takes intake before an appointment, collects survey answers, or books a slot. Gnosari builds it from the fields you name, publishes it at a public address, and stores every completed conversation as a typed record you read in the dashboard, export as CSV or send onward with a webhook.
Set up the one you need working first, then add the others. Gnosari does not limit you to a single agent: each has its own link, its own questions and its own records, so lead capture on your website and a feedback agent in your shop stay completely separate. A clinic often runs pre-visit intake and a patient feedback survey as two agents feeding one dashboard.
No. You describe the job to Gnosari in plain English and name the fields you want back, and it builds the conversation. Putting it on a site is one script tag pasted once, which a marketing manager can do inside any website builder, and the shareable link and QR code need nothing at all. Developers who want the API or the MCP server find both documented.
Yes. You build and publish your first Gnosari agent for free, with no card and no trial clock, and collect real records on the free plan. What the paid plans add, and what each one costs, is listed on the pricing page. The decision to pay comes after the agent is already doing the job.
A structured record, not a transcript. The fields you asked Gnosari for arrive as typed data you read in the dashboard, export as CSV, or send onward with a signed webhook into your CRM, Zapier, Make or n8n. The conversation itself stays underneath if you ever want to read how an answer was given.
Yes, at any time. In Gnosari you change what the agent asks, what it collects, how it looks and where it sends records, and the public address stays the same, so printed QR codes and embedded widgets keep working. Records you have already collected are not affected by any later change.