OyeChats
FeaturesSolutionsIntegrationsPricingDocsBlogContact us

Frequently asked questions

Short answers to the questions that come up before people commit.

Setup

How long does it take to go live?
Minutes of your attention. Crawl time depends on how many pages you index; you can install the widget before training finishes.
Do I need a developer?
Only someone who can paste a script tag into your site or your tag manager. Everything else is dashboard configuration.
Will it slow my site down?
The snippet goes at the end of the body, the loader waits for the page to finish parsing before it does anything, and the chat panel is only built when a visitor opens it. The initial page load carries very little.
Can I use one chatbot on several websites?
Technically yes. Add each hostname to the allowlist. But one knowledge base answering for two different businesses produces worse answers for both. Use one chatbot per site unless the content genuinely overlaps.

Answers

Will it make things up?
Answers are assembled from passages retrieved from your own content, and the chatbot is instructed to say it does not know when the content does not cover the question. That makes invention much less likely than an ungrounded assistant, but no language model can be guaranteed never to err. Test with your real questions, and keep anything that must never be disclosed out of the knowledge base entirely.
Can I stop it discussing certain topics?
Yes. Set a services list to restrict it to specific topics, and use the system prompt for standing instructions. See Controlling answers.
What languages does it support?
The underlying models are multilingual and will generally reply in the language a visitor writes in. The widget's own buttons and labels are not auto-translated. You set those strings yourself. See Appearance and copy.
Can I correct a bad answer?
Not by editing a stored reply. There is no answer cache to edit. You fix the source: add or rewrite the content it drew from, then re-crawl. That fixes every future phrasing of the question, not just the one that was asked.

Data and control

Who owns the data?
You do. For visitor conversations you are the controller and OyeChats is the processor. See Data and privacy and the DPA.
Is my content used to train models?
Your content is indexed to answer your visitors' questions. What each third-party provider does with data passed to it is set out in Sub-processors. Read that page if this matters to your procurement.
Can I export everything?
Leads and analytics export to CSV, invoices download as PDFs, and the REST API can read anything the dashboard shows.
What happens if I cancel?
You keep access until the end of the period you paid for, then drop to Free limits. Reactivating before the period end is free. See Billing.

Not available yet

These appear in the dashboard marked as planned, and are listed here so nobody buys on the expectation of them:

  • WhatsApp as a channel.
  • Facebook Messenger as a channel.
  • A general-purpose Conversation API for talking to your chatbot from your own app or backend.
  • Native one-click CRM connectors. Today the route is webhooks plus an automation platform.

Something here wrong or missing? Tell us and name this page. We will fix it.