Guides: AI Chatbot and Omnichannel Process Automation

The guides section brings together practical material on AI chatbots, omnichannel communication, data protection and process automation. It is designed as a knowledge hub rather than a product configuration screen. Readers can use it to understand the differences between a website chatbot, a tenant-specific knowledge base, human handover and communication channels before deciding which functions are relevant for their business.

Zentor App currently supports six live-usable channels: webchat, email, WhatsApp, Telegram, SMS and telephony through the isolated Zentor SIP-Voicebot. The guides should explain these channels with their real operational boundaries. For example, telephony activation is handled by Master Admin, outgoing webhook configuration is not available as self-service, and the tenant automation interface is a simplified rule engine rather than the full n8n editor.

A useful reading path starts with the fundamentals of an AI chatbot, then moves to knowledge-base preparation and finally to integration and governance topics. Businesses should define which questions the bot may answer, which documents are authoritative and when a conversation must be handed over to a person. The knowledge base supports manual entries, website crawling and file uploads. RAG is disabled by default and must be activated for the tenant.

The section also helps separate general guidance from verified product facts. Package prices, limits and availability should always match the current product sources. Confirmed values include 500 conversations per month and exactly one domain or widget in Starter, while Individuell has no technical conversation or domain limit. Older Business, Professional and Enterprise tariffs have been removed and should not appear in current guides.

The guides are not legal advice and do not replace a company’s own privacy assessment. Articles about data protection should refer to the actual deletion process, subprocessor information and DPA request path without promising automatic retention enforcement that does not exist. The goal is to give readers a structured basis for planning, testing and operating a chatbot responsibly, with clear links to the detailed help and API documentation where implementation-specific information is required.