Docs, guides, and the answers people ask for first.

It says so. Oprag answers only from the pages, documents, and API specs you connect, and it won't invent an answer to fill a silence. When your content doesn't cover the question, it tells the visitor the information isn't available, offers to take their contact details if you've switched lead capture on, and records the question so you can see what your content is missing.

It answers questions, so the resemblance is fair. The difference is what happens around the answer: contacts get captured with the whole conversation attached, and the questions roll up into a view of what your visitors are trying to do. Most chat tools are built to close conversations. This one is built to keep what's in them.

Switch it on for a project and lead capture triggers whenever Oprag meets a question your content doesn't cover. Instead of giving an inaccurate answer, Oprag politely asks the visitor for their name and email and records the whole exchange in your dashboard. On Growth and above it also emails your team and fires your webhook.

Every captured contact and question is logged in your Oprag dashboard on any plan, and exports as CSV. Instant email and webhook alerts, so a new contact reaches someone without anyone watching the dashboard, are available from Growth.

No-code setup takes under 3 minutes using our script tag snippet. REST API integration typically takes under 10 minutes once you have an API key from the dashboard.

Not for website sources: set a re-crawl interval and they re-read themselves on that schedule. Uploaded files change when you replace them.

Yes. Use the one script tag on any website, or call the REST API from your own backend and render the answers yourself. Mobile SDKs for iOS, Android, and Flutter are on the roadmap — route mobile traffic through your own backend in the meantime.

Oprag detects the language of each question automatically and answers in it — same language, same script, same tone — across the widget, the REST API, and the dashboard. Your documents do not have to be in that language: an English-only knowledge base still answers a Japanese question in Japanese. We have verified 60 languages end to end, including romanized and mixed input like Hinglish, and detection is not limited to that list.

See the verified language list →

Yes. Your pages, documents, and captured leads are encrypted and isolated to your account. We never sell your data or use your private business information to train public AI models.

Read our Security page →

It means the core loop — connect your content, test the answers, go live, read the conversations — runs in production today, and that we're still adding to the surface around it. It also means we answer quickly, and we'll tell you plainly when something isn't ready yet.