customer-support-intake

Name: customer-support-intake
Availability: InStock
Author: terraleiloa

Package Seren Desktop incident evidence with consent checks and PII redaction.

2|Updated Feb 25, 2026

Search Tags:#screenshots #diagnostics #evidence collection #pii redaction #serendb #incident reporting #support intake

Ready to run

npx skills add https://github.com/terraleiloa/seren-skills --skill customer-support-intake-terraleiloa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: customer-support-intake
Source: https://github.com/terraleiloa/seren-skills/tree/main/seren/customer-support-intake
Command: npx skills add https://github.com/terraleiloa/seren-skills --skill customer-support-intake-terraleiloa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Customer support intake streamlines the collection of reliable incident evidence so support teams can diagnose failures quickly and consistently, without risking missing logs, diagnostics, chat history, or screenshots.

Core Features & Use Cases

Consent-first evidence collection: Verifies consent before gathering customer-provided evidence.
Automated incident packaging: Captures environment diagnostics, logs, chat history, and screenshots and prepares them for incident review.
PII-aware minimization: Redacts sensitive information and minimizes payload size for safe storage and handling.

Quick Start

Tell the AI: “When a user reports a Seren Desktop failure, collect an incident packet for incident_url using incident_id and customer_id, include_logs and include_chat_history, redact sensitive data, and store it with a 30-day retention policy.”

Frequently Asked Questions about customer-support-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I collect incident evidence for Seren Desktop support tickets?▼

To collect incident evidence for Seren Desktop, use a guided intake process that packages environment diagnostics, logs, chat history, and screenshots into a single shareable incident record for faster troubleshooting.

How does PII redaction work during support evidence collection?▼

PII redaction during support evidence collection works by automatically identifying and redacting sensitive information from incident payloads, minimizing data size to ensure safe storage and compliant handling of customer diagnostics.

Can I configure incident retention policies for uploaded support evidence?▼

Yes, you can configure incident retention policies during the support evidence intake process, such as setting a 30-day retention limit when packaging and storing incident records via secure connector-based uploads.

How do I verify customer consent before gathering incident diagnostics?▼

You can verify customer consent before gathering incident diagnostics by using a consent-first evidence collection workflow that checks authorization prior to capturing logs, chat history, and screenshots for incident reporting.

What is the best way to package logs and screenshots for incident reporting?▼

The best way to package logs and screenshots for incident reporting is to use an automated incident packaging workflow that captures environment diagnostics and applies payload hashing to secure the collected evidence.

Does secure evidence collection work without missing environment diagnostics or chat history?▼

Secure evidence collection ensures no missing logs or chat history by systematically capturing all required environment diagnostics and screenshots into a comprehensive incident record for support teams.