Analytics/Reports
Conversation insights and automatic email reports about your conversations.
The page “Analytics/Reports — Help Center” covers the function identified by this URL. The existing summary is expanded with the actual workflow, prerequisites and known limitations. Analytics includes AI summaries for the latest 30 conversations. Automatic email reports are disabled by default and require explicit opt-in.
Conversation Insights provide AI summaries for the latest 30 conversations. They help identify recurring questions and unresolved cases, but they remain machine-generated summaries. Important decisions needs to be verifyed against the full conversation history.
Automatic email reports are disabled by default and require an explicit opt-in. The tenant selects whether reports are sent daily or weekly. If a report is missing, first verify activation, recipient address and the selected schedule.
Analytics has to be distinguished from data export. A CSV export exists for reports, but there is no general knowledge-base export and no complete Article 20 portability export. The page should not imply that every displayed metric may be exported in a universal format.
Choose a clear period and question in advance of interpreting results. Individual outliers needs to not be treated as a trend. Shared reports may contain personal data and needs to be limited to authorised recipients.
For “Analytics/Reports — Help Center”, the expanded text must remain specific to https://zentor-app.de/en/hilfe/analytics-berichte, 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.
Page 25 verification note 1: this text includes only functions, values and responsibilities confirmed for this URL. It does not confuse the tenant interface with Master Admin or public API routes with internal endpoints. After product changes, the stated values must be checked again against code, database and live behaviour.
When using “Analytics/Reports — Help Center”, 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.