What problem does it solve? Customer support engineers handling Nordic technical cases risk sending replies with unconfirmed root causes, vague next steps, or missing repro details, and they lack a structured way to triage issues or plan escalation strategy. ## Core Features & Use Cases - Reply Review (Mode A): Checks draft customer replies against a six-point checklist covering specific acknowledgment, evidence-based root causes, committed next-touch times, and loop closure. - Issue Triage (Mode B): Classifies reported issues as technical or process-related, routes deep technical work to specialized debugging skills, and produces a triage summary plus a suggested customer message. - Strategy Discussion (Mode C): Acts as a sounding board for escalations, customer relationships, and recurring case patterns without writing anything to disk. - Use Case: A support engineer drafts a reply about a WiFi disconnect issue; the skill flags that the draft asserts an unverified firmware cause and lacks a committed follow-up time before it is sent. ## Quick Start Ask the assistant to review this draft customer reply before sending it to the customer.