Getting Started
Set up Zentor App: first login, dashboard overview, your first chatbot.
The page “Getting Started with the Zentor App” covers the function identified by this URL. The existing summary is expanded with the actual workflow, prerequisites and known limitations. Login uses an email address and password, with optional TOTP two-factor authentication. The setup assistant contains nine steps. Widget domain approval is performed by Zentor and is not a setting in the tenant dashboard.
The first sign-in applies an email address and password, with optional TOTP two-factor authentication. After login, the dashboard displays the areas enabled for the active tenant.
The setup assistant contains nine steps for the initial bot and account configuration. Domain approval for the Widget is performed by Zentor and must not be treated as a tenant self-service setting.
Review saved values following each step. Missing menus may reflect package, add-on or administrative activation rather than a software defect. Widget creation and telephony activation are Master Admin tasks.
Finish with a controlled test of the bot, knowledge answer, handover and supplied Widget code. Record the exact step and error time without exposing credentials.
For “Getting Started with the Zentor App”, the expanded text must remain specific to https://zentor-app.de/en/hilfe/erste-schritte, use only verified facts and clearly separate tenant self-service from actions performed by Zentor. Any support case is best advised to identify this exact page, the active tenant and the observed step without disclosing credentials.
This page also explains its role within the Help Center, from the first check to the expected result, while naming verified limitations and the relevant detailed area. Statements that are not supported for https://zentor-app.de/en/hilfe/erste-schritte are not added. The expansion is therefore substantial without importing unrelated features or repeating generic filler.
When using “Getting Started with the Zentor App”, test one controlled scenario at a time and compare the visible setting, the actual system status and the expected result. If the outcome differs, record the exact time, tenant, channel and unchanged error message. Screenshots and support notes must exclude passwords, tokens and unnecessary personal data so that troubleshooting remains both useful and safe.