Embed AI Chatbot on Website — What Businesses Really Need

An AI chatbot on a company website needs more than a visible chat window. What matters is a controlled knowledge source, an approved domain, a clear handover path to staff, and traceable rules for handling data. In Zentor App, the widget is created by Zentor and approved for the intended website. The tenant then receives the finished embed code. There is no self-service domain approval in the tenant dashboard; changes to the allowlist are maintained by Zentor.

On load, the widget fetches its public configuration and uses a widget embed token for protected functions. This token is shown in plain text only once and is bound to approved origins. If the website origin and the approval don't match, the request can be rejected with `WIDGET_ORIGIN_DENIED`. This means it isn't enough to simply copy the code onto a different domain. The Starter package has exactly one confirmed domain or widget; the Individual (Individuell) package has no technical limit on domains and widgets.

The substantive quality comes from the connected knowledge base. Your own FAQs, product information, PDFs, and service documents can be provided manually, via crawl, or via file upload. RAG is disabled by default and must be activated for the tenant. Without matching sources, the bot should not generate seemingly authoritative company answers. For difficult or sensitive cases, a handover to staff can be set up. The threshold ranges from 0 to 100 and defaults to 70. The live inbox works with a polling interval of eight seconds; there is no team or queue logic.

Before going live, companies should test the integration on the final domain, run through typical questions, and check whether language, greeting, knowledge sources, and handover behavior fit together. Privacy texts, consents, and internal responsibilities remain the company's organizational tasks. A widget alone does not automatically make a deployment GDPR-compliant. The technical configuration must match the actual processes, the privacy policy, and the booked channels.

The integration should additionally be tested in multiple browsers and on mobile devices. This means checking load time, overlap with cookie banners, keyboard operation, and readability. Technically correct answers are of little use if the widget is unreachable on small displays or important controls are covered. Changes to the website layout should therefore trigger a renewed widget test.