Try the Zentor App Chatbot Live.

The Zentor App live demo lets visitors test the public chatbot without creating a tenant first. It uses the same bot stack, state machine, buttons and workflow logic as tenant chatbots, but it runs through the dedicated demo channel. The demo is not connected to a customer tenant, a private knowledge base or a production inbox. Its purpose is to show the interaction model and the supported conversation flow in a controlled public environment.

A demo session is identified by a session ID and a visitor ID. These values allow the browser to reload the existing message history when the widget is reopened. The documented demo API supports sending messages, retrieving history, polling for asynchronously arriving messages, storing ratings and tracking interaction events. Voice output and transcription endpoints also exist when the corresponding feature is enabled. Those voice endpoints are restricted by an origin check for `zentor-app.de` and `www.zentor-app.de`; they are not presented as a general-purpose speech API.

Visitors can use the suggested questions or type their own requests. Useful tests include a simple product question, a follow-up that depends on earlier context and a request that should trigger a workflow such as booking an appointment. The demo can illustrate how buttons and state transitions work, but it cannot predict the exact answers of a future tenant. Production behavior depends on the system prompt, the tenant’s knowledge base, enabled channels and configured handover threshold.

Do not enter passwords, access tokens, confidential business information or personal customer data into the public demo. A demo session may expire or be replaced, and the page is not designed as a secure support channel. If the conversation history cannot be restored, the browser should start a new session rather than attempting to reuse arbitrary identifiers.

After evaluating the demo, a business can use a Demo tenant for a 14-day test or request a consultation. A Demo tenant starts for 14 days, includes mandatory branding, ends automatically and does not upgrade itself. A productive rollout still requires configuration, domain approval, content preparation and functional testing with the company’s own use cases.