「support」の検索結果

Personal App-in-Skill customer-support desk (help desk) that triages incoming support tickets from email, WhatsApp, web chat, contact forms, and WeChat, drafts KB-grounded replies, and proposes actions, then holds every send behind a human approval queue with a pre-send quality gate (support-qa) that outputs SHIP/FIX/BLOCK, plus SLA and CSAT tracking. Use when the user invokes $kelly-support or /kelly-support, mentions 客服 / 工单 / 支持台, a support desk, help desk, customer service, support tickets, ticket triage, a knowledge base or canned macros, SLA / first-response time, CSAT, escalations, or refund requests, wants incoming tickets triaged into a needs_review → approved → done pipeline, agent-drafted replies grounded in a knowledge base and reviewed before sending, refunds and commitments gated behind human approval, or breaching-SLA tickets surfaced. This is the OPERATOR desk (agent + human), distinct from a visitor-facing chat bubble.

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

Design support metrics dashboard -- CSAT, FRT, TTR, ticket deflection rate, volume trends, and agent efficiency. Use when asked to "what metrics should support track", "build our support dashboard", "measure support quality", or "audit our support performance".

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

Write support playbook -- response templates, issue-type runbooks, tone guide, and common resolution paths. Use when asked to "write support templates", "build a support playbook", "train our support agents", or "standardize our support responses".

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

Support operations reconnaissance -- audit current ticket volume, SLA compliance, knowledge base coverage, escalation paths, and CSAT to understand where support is the constraint. Use when asked to "audit our support", "why is our response time bad", "how healthy is our support operation", or "before designing a support system".

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

Expert support operations guidance for customer service excellence. Use when designing ticket management systems, creating SLA policies, building support tier structures (L1/L2/L3), optimizing knowledge bases, defining severity levels and escalation procedures, implementing support metrics (CSAT, FRT, TTR, FCR), configuring support tool stacks, or building support-to-CS feedback loops. Covers Zendesk, Intercom, Freshdesk, and help desk best practices.

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

[omh] Support ticket your team must answer or escalate: turn a support case into a clear customer reply, severity path, and owned next step. Use when the user says: support escalation, customer support reply, ticket triage, 고객 지원 에스컬레이션, 고객 답변 초안, 지원 티켓 분류.

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

Master the AI tools that transform customer support from cost center to competitive advantage. Automate routine queries, empower agents, and delight customers at scale. Use when "customer support, helpdesk, ticketing system, chatbot, knowledge base, support automation, CSAT, customer service, support, helpdesk, chatbot, knowledge-base, customer-service, automation" mentioned.

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

Design customer support onboarding flow -- first-contact experience, proactive support touchpoints, and setup success checklist. Use when asked to "design our onboarding support", "how do we support new customers during onboarding", or "reduce early churn from setup failures".

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

Open, classify, and escalate support cases with Salesforce Technical Support via the Help portal: choosing severity, engaging Premier Success, the Escalate to Technical Support Management path, tracking incidents on the Trust site. NOT for escalating your own org's cases after N hours - use admin/escalation-rules. NOT for SLA milestone timers and entitlement processes - use admin/entitlements-and-milestones.

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

This skill should be used when the user asks to "calculate child support", "養育費を計算", "婚姻費用を計算", "養育費月額", "婚姻費用分担額", "算定表で計算", or wants deterministic computation of child support or marital cost-sharing under the 令和元年改定 standard.

Elite AI-powered customer support specialist mastering conversational AI, automated ticketing, sentiment analysis, and omnichannel support experiences. Integrates modern support tools, chatbot platforms, and CX optimization with 2024/2025 best practices. Use PROACTIVELY for comprehensive customer experience management.

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

Discovers connected MATLAB-supported hardware devices, searches by capability, and checks required support packages and add-ons. Use when the user asks what hardware is connected, finds a device that supports a capability (e.g., CAN, analog input), or checks if required support packages or add-ons are installed. Does NOT connect to, configure, or acquire data from devices — defers to device-specific skills for usage workflows.

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

Add unsigned integer (uint) type support to PyTorch operators by updating AT_DISPATCH macros. Use when adding support for uint16, uint32, uint64 types to operators, kernels, or when user mentions enabling unsigned types, barebones unsigned types, or uint support.

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

Use this skill when designing the UX and content strategy for a Salesforce-powered self-service portal or help center — pre-deflection article surfacing, Help Center search UX, friction-calibrated case submission forms, community peer support layers, and deflection measurement. Trigger keywords: design self-service portal, case deflection strategy, help center UX design, reduce support volume with self-service, knowledge base search experience. NOT for picking which contact reasons to deflect and through which channel — use architect/case-deflection-strategy. NOT for building the Experience Cloud site itself — use admin/experience-cloud-site-setup. More trigger keywords: article visibility matrix IsVisibleInCsp IsVisibleInPkb, which articles show in the customer portal, case visibility for portal users, CaseComment IsPublished customer visible comment, self-registration profile and account for a portal, Help Center template does not support login, deflection metrics SOQL KnowledgeArticleViewStat, self-service journey map, moderation policy for a support community.

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

Build SaaS customer support — tiered support models, SLAs, macros, escalation, and support-driven product feedback.

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

Add unsigned integer (uint) type support to PyTorch operators by updating AT_DISPATCH macros. Use when adding support for uint16, uint32, uint64 types to operators, kernels, or when user mentions enabling unsigned types, barebones unsigned types, or uint support.

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

Run a support investigation as a suggest-and-interpret loop, never executing anything yourself — orient to the product's support pack and follow the signal with judgment. Use when someone asks for help triaging, investigating, or resolving an operational or support issue on a deployment. Not for feature-development cards (see investigate-and-fix and implement-this).

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

Maintain a support docs pack — dedup, length budgets, and no splintering — and land changes as a reviewed pull request. Use when a support thread, or a hand-off from Support assist, surfaces a new resolution, a correction to an existing one, or a deployment quirk worth recording. Not for ordinary code changes.

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

Configures the JetFormBuilder action events system — the named events (DEFAULT.PROCESS, DEFAULT.REQUIRED, GATEWAY.SUCCESS, GATEWAY.FAILED, BAD.REQUEST, ON.DYNAMIC_STATE, never) that decide WHEN a Form Action runs. Covers declaring supported / unsupported / required events on a custom action, the validation precedence inside Base_Event::is_valid_action(), the multi-event subscription model the action editor exposes, and how to register a brand-new event type via the 'jet-form-builder/event-types' filter using Base_Event, Base_Action_Event, or Base_Gateway_Event. Use when an action needs to run only on payment callbacks, only on validation failure, only on a specific conditional state, after another action's hidden flow, or when the plugin needs to define its own event class (e.g. for inbound webhooks). Triggers on mentions of "JFB events", "action events", "GATEWAY.SUCCESS", "DEFAULT.PROCESS", "supported_events", "unsupported_events", "get_required_events", "Base_Event", "Base_Gatewa...

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

Elite AI-powered customer support specialist mastering conversational AI, automated ticketing, sentiment analysis, and omnichannel support experiences. Integrates modern support tools, chatbot platforms, and CX optimization with 2024/2025 best practices. Use PROACTIVELY for comprehensive customer experience management.

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

電子カルテに組み込む臨床判断支援を設計し、薬の相互作用や用量の検証、臨床スコアの計算、警告の重要度に応じた画面制御とテストを実装するスキル。

• 薬の相互作用とアレルギー確認の実装
• 患者情報に応じた用量検証
• NEWS2などの臨床スコアの実装

Prioritize support requests, identify owners, route internally, and prepare safe customer drafts

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

Prepares and validates research-only clinical decision-support evaluation, evidence-profile, cohort, survival, biomarker/model, privacy, and governance artifacts. Supports aggregate or synthetic research documentation and traceability, excluding patient care and live clinical operation.

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

Authoring playbook for building agents that triage and reply to customer messages — support tickets, email inquiries, chat questions, refund requests, or product issues. Use this when the user wants an agent that handles inbound customer questions, drafts replies, escalates hard cases, summarizes tickets, or follows a support playbook.

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