This article provides a conceptual orientation for beginning with Enneo. It describes the functional prerequisites for Enneo to operate and shows how communication channels, tickets, customer data, and AI agents interact. The detailed integration steps are explained in the respective chapters.
Basics
Enneo processes customer requests into tickets. Tickets are created by incoming requests, which are transmitted via any communication channel. Once a ticket exists, it can be processed manually or by AI agents. Customer data establishes the link between the ticket and the customer and forms the basis for data-driven processing and automation.
The basic functional building blocks are therefore:
1. Integration of Communication Channels
In order for Enneo to operate, the platform requires at least one integrated communication channel. Incoming messages can create tickets. It doesn’t matter whether it’s email, voice, chat, or other channels; the technical logic remains identical.
The choice of the first channel is project-specific. Enneo can start with any channel and receive modular extensions later.
2. Tickets
Incoming messages generate a ticket, encompassing the entire conversation. Tickets form the basis for processing and enable both manual activities and AI-supported steps. Without a ticket, no process processing occurs.
3. Customer Data
By integrating ERP or CRM systems, customer and contract data become available in Enneo and form the basis for context-related processing and automated procedures.
4. AI Agents
AI agents analyze content, make decisions within defined rules, and support processing. Operational use requires existing tickets. For data-driven processing, customer-centered data is needed so AI agents can retrieve or update information.
Recommended Implementation
This order has proven successful in integration:
- Communication channel
- ERP or CRM data
- AI agents
The order is based on practical experience and reflects the subject matter dependencies without dictating a fixed installation sequence.
