「support」の検索結果

Use when support operations, launch fallout, repeated customer issues, or triage ownership need a structured response layer.

日本語の概要は準備中です。原文の説明を表示しています。

Generate draw.io editable diagrams (.drawio, .drawio.svg) from text, images, or Excel. Orchestrates 3-agent workflow (Analysis → Manifest → SVG generation) with quality gates. Use when creating architecture diagrams, flowcharts, sequence diagrams, or converting existing images to editable format. Supports Azure/AWS cloud icons. Triggers on draw.io, drawio, ダイアグラム, アーキ図, フローチャート, シーケンス図.

Build a customer-facing Azure Update PowerPoint from Azure Updates MCP results, including customer classification, Japan region stamps, UPDATE Points, speaker notes, and Verify-Pptx gate checks. Use when creating or updating an Azure Update / Azure アップデート customer deck, bootstrapping a new Azure Update PPTX workspace, reviewing Deploy Region support, or re-applying manifest JSON to an existing deck.

Operate a reusable technical book manuscript workspace with writing structure, reader persona SSOT, review rules, and optional Markdown to Re:VIEW/PDF support. Use when organizing a book manuscript repo, defining or reviewing target readers, standardizing chapter/section files, setting writing/review agents, handling publisher proof comments, or assessing an existing writing workspace. Triggers on book writing workspace, reader persona, reader audience, 読者ペルソナ, persona SSOT, technical book project, 執筆ワークスペース, manuscript workflow, Re:VIEW workspace, proof PDF, annotated proof, publisher proof comments, 校正, 校正注釈, and 初校.

"Design customer service operations including tiered support (L1/L2/L3), response templates, SLA definitions, escalation procedures, and complaint handling. Use this skill when the user needs to set up a CS team, create service standards, design escalation flows, or improve response quality — even if they say 'our CS is a mess', 'how should we handle complaints', 'set up support tiers', or 'create CS SOPs'.".

日本語の概要は準備中です。原文の説明を表示しています。

Support SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze CSAT, NPS comments, reviews, and support feedback for sentiment, recurring themes, customer pain, and service improvement actions. Use for customer support and CX feedback reviews.

日本語の概要は準備中です。原文の説明を表示しています。

Frappe Helpdesk implementation and customization guidance for ticket intake, SLAs, assignment, portals, knowledge base, notifications, and support workflows. Use when work touches the Frappe Helpdesk app or customer support operations.

日本語の概要は準備中です。原文の説明を表示しています。

Build a roll-forward schedule for a balance-sheet account or account group, tying beginning balance, activity, reversals, payments, adjustments, and ending balance to GL support. Use for month-end close packages and audit support.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a task needs the judgment of a Computer User Support Specialist — triaging an inbound ticket's severity and SLA clock before troubleshooting it, verifying a caller's identity before any password/MFA/account-state change, walking a live incident through a structured troubleshooting sequence instead of guessing at a fix, deciding whether a request is an incident, a service request, or the underlying problem behind a string of incidents, or judging whether a ticket should resolve at tier 1 or genuinely needs escalation.

日本語の概要は準備中です。原文の説明を表示しています。

Audit risk simulation and decision support systems for Monte Carlo modeling quality, wargaming analysis, threat assessment, mission planning support, and course-of-action decision analysis..

日本語の概要は準備中です。原文の説明を表示しています。

Turn raw customer material into evidence-backed personas and verbatim voice-of-customer language. Two modes - analyse sources the user already has (call transcripts, support tickets, survey responses, sales notes, reviews), or source new material from public places customers actually talk. Produces quoted pains, objections, and switch triggers that other skills consume, never invented ones. Use when the user says "customer research", "voice of customer", "what do our customers actually say", "we need real quotes", "analyse these call transcripts", "read our support tickets", "build a persona from data", "find what customers complain about", or when a persona is marked provisional. For structuring the finished persona into the knowledge base, see brand-context. For the JTBD persona template itself, see customer-persona.

日本語の概要は準備中です。原文の説明を表示しています。

Write a technical tax position memo that documents a tax filing position with authorities, facts, analysis, and conclusion. Use when a tax professional says "write a tax memo", "document this tax position", "research memo for the partner", "we need to support this deduction", "document the tax treatment", "write up the authority for this position", "technical memo on [tax issue]", "MLTN analysis", "reasonable basis memo", "document the IRC section that supports this", or needs to formally document a tax conclusion. Also trigger when someone has a tax question that needs a written conclusion backed by legal authority - even if they don't use the words "tax memo" or "tax position".

日本語の概要は準備中です。原文の説明を表示しています。

Generate or suggest canned response templates for common support scenarios.

日本語の概要は準備中です。原文の説明を表示しています。

Generate a weekly support digest and post it to [Slack](https://composio.dev/toolkits/slack)

日本語の概要は準備中です。原文の説明を表示しています。

Escalate a support ticket to a [Linear](https://composio.dev/toolkits/linear) issue and notify the team on [Slack](https://composio.dev/toolkits/slack).

日本語の概要は準備中です。原文の説明を表示しています。

Scan your support inbox and batch-process tickets with quick actions (reply, tag, assign, close)

日本語の概要は準備中です。原文の説明を表示しています。

Pull open [Gorgias](https://composio.dev/toolkits/gorgias) support tickets and triage them by urgency, category, and sentiment

日本語の概要は準備中です。原文の説明を表示しています。

Summarize a support ticket thread into key points and action items.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze ticket history to identify patterns and generate reusable support macros/playbooks.

日本語の概要は準備中です。原文の説明を表示しています。

Summarize customer support/sales calls from [Dialpad](https://composio.dev/toolkits/dialpad) or [Leexi](https://composio.dev/toolkits/leexi) call logs

日本語の概要は準備中です。原文の説明を表示しています。

Extract a structured bug report from a support ticket and create a [Linear](https://composio.dev/toolkits/linear) issue.

日本語の概要は準備中です。原文の説明を表示しています。

Review a drafted support response for quality, accuracy, tone, and completeness before sending.

日本語の概要は準備中です。原文の説明を表示しています。

Rewrite a support response in a different tone - formal, casual, technical, empathetic, or concise.

日本語の概要は準備中です。原文の説明を表示しています。