Osonflow docs

Osonflow puts an AI assistant on your website and in your messengers. It answers customers from the documents and pages you give it — and nothing else — and hands the conversation to your team when a person is needed.

This guide follows the dashboard from top to bottom. If you are just starting, read the Quickstart; the rest you can come back to when you need it.

After you sign up, the dashboard walks you through these steps. Most businesses finish in about fifteen minutes.

1. 01

   Switch the assistant on

   Osonflow writes answers using OpenAI. Its own keys work out of the box; add your company's key in Integrations if you want AI usage billed to your own account.

2. 02

   Tell it about your business

   Paste your website address and it reads the pages itself. Add price lists, policies and FAQs to the Knowledge base later.

3. 03

   Make it look like you

   Choose the assistant's name, the first thing it says, and the colour of the chat button in Widget customization.

4. 04

   Put it on your website

   Copy one line of code and paste it into your site. A chat button then appears in the corner of every page. See Website chat.

5. 05

   Your first conversation

   Every chat arrives in your inbox. Read along while the assistant answers and step in as a human at any point.

• You teach it. Give it your documents, prices and policies. It reads them and nothing else.
• It answers first. Every customer is answered right away, day and night, and every reply shows the source it came from so your team can check it.
• You get the hard ones. When a question can't be answered from your content, or a customer asks for a person, the conversation is escalated to your team.
• It gets better. Questions it could not answer show up in AI performance, so you know what to add to the knowledge base next.

The fastest way to a working assistant. In Set up with AI, give it your website address and it reads the site, asks you to fill in what the website doesn't say, and then writes your knowledge base, instructions and chat window.

Nothing goes live on its own: what it writes is saved as a draft for you to review and change before you publish.

The documents and web pages the assistant is allowed to answer from — the single most important page in the dashboard. The assistant answers only from what you put here, so it cannot invent a price or a policy.

When AI performance lists a question the assistant could not answer, the fix is almost always a missing document here.

When someone comes back a second time, the assistant remembers what it learned about them — their name, their order, what they asked last time — so they don't have to repeat themselves. Customer memory shows what it remembers about each person.

A chat button on your website that answers visitors with your knowledge base, day and night. Add the code once — changes you make in Widget customization appear on your site automatically.

Copy the snippet from Integrations → Website chat, where your organization ID is already filled in, and paste it before the closing </body> tag. There are ready-made versions for plain HTML, React, Next.js and vanilla JavaScript.

<script
  src="https://widget.osonflow.uz/widget.js"
  data-organization-id="YOUR_ORGANIZATION_ID"
  data-agent-id="default"
  data-position="bottom-right"
  defer
></script>

Send the snippet to whoever manages your website if you would rather not touch the code yourself.

Behaviour, copy, brand, launcher and voice for the widget your customers see. Everything is edited as a draft and published as a version you can roll back.

• Brand: the assistant's name, logo, colours, radius and typeface. Every visitor-facing colour pair is checked live for contrast.
• Copy: the greeting, the headline on the home screen and the placeholder in the message box.
• Launcher: the button that sits on your page when the chat is closed, plus an optional invitation that appears above it.
• Help content: the topics and articles shown on the widget home screen.
• Voice: let visitors talk to the assistant out loud instead of typing.

The same assistant answers in your messengers, and every conversation lands in the same inbox as your website chats. Connect each one in Integrations.

Every chat with a customer, from every channel. Read them, reply yourself, and mark them done. Each conversation is in one of three states:

You can step in as a human at any point. Your first reply escalates the conversation, so from then on the customer hears only from your team.

People who left a name, email or phone number during a conversation. Leads is your follow-up list.

If you turn on voice in Widget customization (it needs your own AI key), visitors can speak to the assistant instead of typing. AI voicechats keeps the transcript of every spoken conversation.

How often the assistant finished the job on its own, how fast it replied, and the questions it could not answer. Check it weekly — the unanswered questions tell you exactly what to add to the knowledge base next.

For questions you want answered the exact same way every time — a refund request, a booking — draw the steps on a canvas instead of trusting the assistant to improvise.

Test every run in the builder before you publish. Once published, workflow conversations appear in the inbox with their own tag, so you can filter them apart from assistant conversations.

Things the assistant can do beyond talking — look something up, write a row into a spreadsheet, book a call. Set them up in Assistant tools, then choose which ones each widget may use. For example:

• Google Sheets: find, add and update rows. The assistant collects exactly the columns you pick.
• Google Calendar: check free time and book meetings. Connect once — every calendar tool uses the same account.
• Your own API: call any HTTP endpoint with the parameters the assistant works out from the conversation, and test it in the console before it goes live.

Send a notice to Discord, Telegram, WhatsApp or your own system whenever something happens — a new chat, a message, a conversation handed to your team. Add destinations in Integrations → Event webhooks.

Developers who want signed payloads and delivery retries should use API webhooks instead.

Osonflow's own AI keys work out of the box. Add your company's keys in Integrations → Your AI keys only if you want AI usage billed to your own OpenAI or Google account. Voice is the exception: it needs your own OpenAI or Gemini key before you can choose a voice model.

Every plan includes the whole product — chat widget, shared inbox, routing and human handover. Start on Starter for free, move to Growth when the assistant is carrying real work, and talk to sales about Enterprise. Plans & Billing shows your plan, usage and invoices; prices are on the pricing page.

Move a whole setup between organizations — for example from a test organization to the real one. Data transfer exports your knowledge sources and widget as one Osonflow setup file, which you download or copy and then import into the other organization. Sources that already exist there are skipped, unless you choose to replace them.