Documentation Index
Fetch the complete documentation index at: https://docs.enneo.ai/llms.txt
Use this file to discover all available pages before exploring further.
Basics
Enneo processes customer concerns into tickets. Tickets are created by incoming inquiries, which are transmitted via any communication channels. As soon as a ticket exists, it can be processed manually or by AI agents. Customer data establish the connection between the ticket and the customer, and form the basis for data-supported processing and automation. The fundamental building blocks are therefore: 1. Connection of communication channels For Enneo to operate, the platform requires at least one connected communication channel. Only incoming messages can generate tickets. It does not matter whether it is e-mail, voice, chat or other channels; the technical logic remains identical. The selection of the first channel is project-related. Enneo can start with any channel and later receive modular extensions. 2. Tickets Incoming messages generate a ticket, which covers the entire conversation. Tickets form the basis for processing and allow both manual activities and AI-supported steps. Without a ticket, no process processing occurs. 3. Customer data By connecting ERP or CRM systems, customer and contract data become available in Enneo, and form the basis for context-related processing and automated processes. 4. AI agents AI agents analyze contents, make decisions within defined rules, and aid processing. Operational use requires existing tickets. For data-supported processing, customer-centered data is needed so that AI agents can retrieve or update information.Recommended Implementation
This order has proven effective in integration:- Communication channel
- ERP or CRM data
- AI agents