Skip to content
Business-based routing using rules defined by administrators
Qisutu AddOn
Kim – Automatic Routing
Kim classifies new email tickets and assigns them exclusively to queues and priorities approved by an administrator.
Version1.0.1
CompatibilityQisutu 1.0.1 or newer
Languages11
LicenseAGPL-3.0-or-later
Module overview
Kim – Automatic Routing
The key use cases and capabilities at a glance.
Optional prioritization based on concrete operational impact
Suspected spam is moved safely to a review queue and is never deleted
Route new email tickets to an approved queue and optionally a priority using controlled business rules.
Only new tickets created from incoming customer emails are processed.
Each filter describes a request type and its target queue. The input queue comes from the respective email account.
Each filter describes evidenced operational impact and its target priority.
Capabilities in detail
Capabilities in detail
The following capabilities are part of this independent Qisutu module.
- Define the filter conditions and select exactly one target queue.
- Describe clearly which type of request belongs in this queue.
- Define the filter conditions and select exactly one target priority.
- Describe concrete operational impact. Wording such as “urgent” or “immediately” is not sufficient.
- Queue and priority actions that are not marked as binding may be overridden by Kim. All other postmaster actions always remain unchanged.
- Suspected messages are moved only and are never deleted.
- Available directly in the module: Latest AI decisions.
- Available directly in the module: Processed.
- Available directly in the module: Unclassified.
How the module works
How the module works
The typical workflow is integrated directly into day-to-day work in Qisutu.
- 01
Business-based routing using rules defined by administrators
- 02
Optional prioritization based on concrete operational impact
- 03
Suspected spam is moved safely to a review queue and is never deleted
- 04
Define the filter conditions and select exactly one target queue.
- 05
Describe clearly which type of request belongs in this queue.
- 06
Define the filter conditions and select exactly one target priority.
Requirements
Requirements
These technical and organizational requirements are relevant for deployment.
- Qisutu 1.0.1+
- Kim API token
- Qisutu daemon
- Incoming customer emails
Administration and operation
Administration and operation
Configuration, background processing, and control remain centralized in Qisutu.
- Only new tickets created from incoming customer emails are processed.
- Each filter describes a request type and its target queue. The input queue comes from the respective email account.
- Each filter describes evidenced operational impact and its target priority.
- Suspected messages are moved only and are never deleted.
- The API address and Kim model are fixed in the module and cannot be changed by customers.
Security and control
Security and control
Credentials, permissions, and automated decisions are handled transparently and securely.
- Queue and priority actions that are not marked as binding may be overridden by Kim. All other postmaster actions always remain unchanged.
- Describe concrete operational impact. Wording such as “urgent” or “immediately” is not sufficient.
- Suspected messages are moved only and are never deleted.
Scope and boundaries
Scope and boundaries
The module extends Qisutu for a defined purpose while remaining separate from the Qisutu core.
- Installation through Administration → AddOns
- Independent ZIP module with no changes to Qisutu core files
- 11 fully supported interface languages
- AGPL-3.0-or-later
Questions about this AddOn?