From 2c29eed24d235ec61bc6e3b680ca07eaef4c23db Mon Sep 17 00:00:00 2001
From: Floke <floke.com@gmail.com>
Date: Sat, 28 Feb 2026 18:34:33 +0000
Subject: [PATCH] [31588f42] docs: document SuperOffice Service/Ticket module
 and categories

---
 GEMINI.md                       | 35 ++++++++++++++++++---------------
 connector-superoffice/README.md | 12 +++++++++++
 2 files changed, 31 insertions(+), 16 deletions(-)

diff --git a/GEMINI.md b/GEMINI.md
index 0101a5e1..ceb0a945 100644
--- a/GEMINI.md
+++ b/GEMINI.md
@@ -283,20 +283,23 @@ When creating sales via API, specific constraints apply due to the shared tenant
     *   `Person`: Highly recommended linking to a specific person, not just the company.
 *   **Context:** Avoid creating sales on the parent company "Wackler Service Group" (ID 3). Always target the specific lead company.
 
+### 7. Service & Tickets (Anfragen)
+
+SuperOffice Tickets represent the support and request system. Like Sales, they are organized to allow separation between Roboplanet and Wackler.
+
+*   **Entity Name:** `ticket`
+*   **Roboplanet Specific Categories (CategoryId):**
+    *   **ID 46:** `GE:"Lead Roboplanet";`
+    *   **ID 47:** `GE:"Vertriebspartner Roboplanet";`
+    *   **ID 48:** `GE:"Weitergabe Roboplanet";`
+    *   **Hierarchical:** `Roboplanet/Support` (often used for technical issues).
+*   **Key Fields:**
+    *   `ticketId`: Internal ID.
+    *   `title`: The subject of the request.
+    *   `contactId` / `personId`: Links to company and contact person.
+    *   `ticketStatusId`: 1 (Unbearbeitet), 2 (In Arbeit), 3 (Bearbeitet).
+    *   `ownedBy`: Often "ROBO" for Roboplanet staff.
+*   **Cross-Links:** Tickets can be linked to `saleId` (to track support during a sale) or `projectId`.
+
 ---
-Here are the available functions: 
-[
-  "list_directory",
-  "read_file",
-  "search_file_content",
-  "glob",
-  "activate_skill",
-  "replace",
-  "write_file",
-  "web_fetch",
-  "run_shell_command",
-  "save_memory",
-  "google_web_search",
-  "write_todos",
-  "delegate_to_agent"
-]
+This is the core logic used to generate the company-specific opener.
diff --git a/connector-superoffice/README.md b/connector-superoffice/README.md
index 0cc0c232..7b0a7111 100644
--- a/connector-superoffice/README.md
+++ b/connector-superoffice/README.md
@@ -295,6 +295,18 @@ python3 connector-superoffice/create_sale_test.py
 ```
 This script finds the first available contact in the CRM and creates a test opportunity for them.
 
+### 18. Service & Request Management (Tickets)
+
+The Service module handles incoming requests and support cases. For Roboplanet, specific categories are used to manage leads and partner interactions.
+
+**Key Categories (Roboplanet):**
+*   **Lead Roboplanet (ID 46):** Incoming potential leads.
+*   **Vertriebspartner Roboplanet (ID 47):** Communication with partners.
+*   **Weitergabe Roboplanet (ID 48):** Internal handovers.
+
+**Data Structure (Entity: `ticket`):**
+Tickets are linked via `contactId` and `personId`. They can also be associated with a `saleId` to provide a 360-degree view of a deal including its technical support questions.
+
 ---
 This is the core logic used to generate the company-specific opener.