Frequently asked questions

It says it does not know — it invents nothing. Then it offers to take contact details, and the lead lands in your work queue. The question also goes onto your missing-knowledge list. That turns "I don't know" from a lost customer into a task on your list.

Two things protect you. Structure: it may only work from the knowledge base you approved, and every answer names the page it came from, as a clickable link. And measurement: of 52 questions, the 12 deliberately unanswerable ones were correctly refused all 12 times. Anything under 100% we treat as a defect.

The chat interface ships in six languages: Hungarian, English, German, French, Spanish and Polish — your own page's language selects it. The ANSWER, however, is not tied to a list: the assistant replies in the language the visitor asked in, from your knowledge base, even when that base is in another language. Prices and currencies are never converted: “1 980 Ft + áfa” stays exactly that in a foreign-language answer. The admin panel is available in Hungarian and English.

No, and that is not the goal. It takes the recurring basics off your plate — the ones your site already answers — and hands the hard cases to a human, with contact details attached. How much it actually took over comes from the return report, not from our promise.

Yes. They can ask for a colleague in the widget, and the conversation continues in the same window — you answer from the panel, where a work queue shows who is waiting and who has been picked up. You decide when it is offered (always, only when the bot could not answer, or never) and during what hours. Outside those, or when nobody is at the panel, the visitor gets the contact form and the enquiry lands in the work queue. One limit stated up front: your colleague learns about a waiting visitor from the open panel — we do not send email or push notifications today. The feature is off by default; you turn it on per project in the panel.

On our own server, in the European Union. The knowledge base, the conversations and the leads stay with us. Producing answers involves calling a language model; the Privacy Policy lists the details.

The widget sets no cookies and stores no messages in the browser. It writes exactly one entry, bound to the tab: the identifier of the conversation in progress, for at most 30 minutes — without it the visitor would start over on every page change. The entry is removed when the tab closes or after 30 minutes. This is how the widget works technically; you have to assess the data processing of your own website and every component embedded in it (analytics, ads, video) as a whole.

Question and answer text in the conversation log expires after 90 days. If a visitor submits a lead, the full conversation copy attached to it remains until the lead is closed and for another 90 days afterwards. The original text of an unanswered question remains in the “missing knowledge” work queue until the project or account is deleted, or a deletion request is carried out. Statistics do not expire; they contain no direct contact details, but their technical conversation identifier remains.

You tell us and we carry it out: the lead row is deleted, the conversation text is deleted, and so is their unanswered question. There is deliberately no "delete my data" button in the widget, because it would let anyone delete someone else's data.

Crawling takes from minutes to a few hours depending on size. Reviewing the knowledge is up to you — that is the longest step, and the most important one. Embedding takes five minutes. An afternoon is realistic for a mid-sized site with tidy content; a large shop full of contradictions takes longer.

We re-read it weekly on our own. Reprocessing what has not changed does not consume your processing allowance — only genuinely changed pages go back to the model. The monthly fee is separate; we do not bill per page.

Yes: PDF, Word, Excel and text files. A price list becomes tabular knowledge rather than a wall of text — that is how the assistant can quote a specific price.

Yes, as separate projects with separate knowledge bases and widgets. Knowledge does not leak between them. How many projects you get depends on the plan.

The embed code loads asynchronously, so it does not block rendering. The widget only starts working when a visitor opens it.

No. After signing up you start on the Trial plan, with no card details.

Yes, after payment. You can subscribe as a company or as an individual.

Yes, at any time. A higher plan takes effect immediately, and the allowance becomes that of the new plan.

From the panel, in one click. You keep the service until the end of the period you already paid for, after which the account returns to the free tier — your data does not disappear.

No. While a human is running the conversation, not one turn uses credit, and its length does not matter either. Credit covers the bot’s answers: while the bot is answering — including the time a visitor is waiting for a colleague who has not picked up yet — that counts as one conversation, as usual.