fix(lead): lead-inbox nach Probe mit frischem Agenten geschärft

Beschreibung auf Auslöser umgestellt, Einladungen, weitergeleitete
Anfragen Dritter, Basecamp-Dublettensuche, Grußformel nach Stil-Skill.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
m3ta-chironandClaude Fable 5.2 committed 2026-11-13 18:26:19 +01:00
1 parent 9bf7b611e6
commit b4c7574051
2 files changed
+17 -16

No files matched your search

+8 -7
View File
@@ -30,14 +30,14 @@ Give `end_date` as an explicit time (`'<today>T23:59'`); `'now'` sometimes fails
1. `kunde_suchen` with the sender's address (for a shared mailbox: the person from the signature). Exactly one hit is needed. No hit for an internal sender → `customer_id: "guess:<address>"`, shown as such in the proposal. Several hits → `Für dich:`.
2. `dublette_suchen` for that customer. An open ticket on the same matter → no new ticket; the proposal is `notiz_anlegen` with the mail's content on that ticket.
3. Attachments: `get_email_content(cache_number=<n>, download_attachments=true, download_path='<scratchpad>/<thread>')`. Take only attachments with `isInline: false`. Base64-encode each into the article. Empty the directory after the thread is done.
4. `ticket_anlegen`: title from the matter (plain, no prefix); group `IT`; no owner, the IT triage bot assigns owner and priority. Article body in HTML: one line "Per Mail an Sascha König am <date>, von <sender>", then the original mail text unchanged.
4. `ticket_anlegen`: title from the matter (plain, no prefix); group `IT`; no owner, the IT triage bot assigns owner and priority. Article body in HTML: one line "Per Mail an Sascha König am <date>, von <sender>", then the text of the mail that states the problem, unchanged. Leave out quoted chains below it and anything holding credentials or access links; say in the proposal what was left out.
5. Read back with `GET tickets/<id>?expand=true`: customer, group `IT`, article count; attachments via `GET ticket_articles/by_ticket/<id>`. Zammad rewrites the title shortly after creation, so refer to the ticket by number.
Zammad sends the customer no confirmation for API tickets. The redirect notice is the only message the sender gets.
## Basecamp to-do
Load the `basecamp` skill; check flags with `basecamp todos create --agent --help`.
Load the `basecamp` skill; check flags with `basecamp todos create --agent --help`. The CLI prints a keyring warning before its JSON: append `2>/dev/null` when parsing.
```bash
basecamp todos create "<Titel>" --in <project-id> [--todoset <id>] --list <list-id> \
@@ -45,7 +45,7 @@ basecamp todos create "<Titel>" --in <project-id> [--todoset <id>] --list <list-
```
- Title plain. Description (Markdown, from a scratchpad file so umlauts survive): one context sentence, the core of the mail, "Per Mail von <sender> am <date>", then the AI marker.
- Target: the project the mail clearly belongs to; 👥 IT (one of the six lists) for team work; otherwise 🔒 Meins. IDs from `systems/basecamp.md`; projects with several to-do sets need `--todoset`.
- Target: the project the mail clearly belongs to; 👥 IT (one of the six lists) for team work; otherwise 🔒 Meins, in its inbox list. IDs from `systems/basecamp.md`; projects with several to-do sets need `--todoset`.
- Owner and due date come from the approval. Without both, create nothing. The owner must be a member of the project (`basecamp people list --in <id>`), otherwise the item is a `Für dich:` point.
- Read back with `basecamp todos show <id> --json`: assignee, due date, attachments.
@@ -59,7 +59,7 @@ A reply to the original mail, in `sascha-internal-communication-style`. Decide t
- A Basecamp link only for people with access to the project; otherwise name owner and due date in the text and leave the link out.
- Recipients: the sender. Keep the original Cc when that round followed the matter.
Model for tone, full form, Zammad:
Greeting and closing follow the e-mail template of `sascha-internal-communication-style`. Model for tone, full form, Zammad:
```md
Hallo <Vorname>,
@@ -70,8 +70,9 @@ Hintergrund: Anfragen an die IT bearbeiten wir im Helpdesk, damit nichts in eine
Mein Vorschlag: Stell solche Anliegen künftig direkt dort ein, über https://tickets.az-gruppe.com. Dann sparst du dir den Umweg über mich.
Viele Grüße
Sascha
Mit freundlichen Grüßen / Best regards
Sascha König
*✨unterstützt durch KI✨*
```
@@ -81,7 +82,7 @@ Sascha
`send_email(action='reply', cache_number=<n>, htmlbody='<…>')`. Set `to` / `cc` only when the proposal differs from the original recipients.
- The text is the approved one, character for character; only the ticket number or link is filled in.
- HTML: `<p>` per paragraph, nothing between the tags, `<br>` only inside the closing ("Viele Grüße<br>Sascha"). Last paragraph: `<p><em>✨unterstützt durch KI✨</em></p>`.
- HTML: `<p>` per paragraph, nothing between the tags, no `<br>`. Last paragraph: `<p><em>✨unterstützt durch KI✨</em></p>`.
- Success is the text `Reply email sent successfully` with `'status': 'accepted'`. Anything else is a failed step.
- Read back: `search_emails(folder='Sent Items', search_type='subject', query='<subject fragment>')` for today, then `browse_email_cache`: recipients, Cc and the preview match the approved text. The connector prefixes the subject with `RE:`.