界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
效率与协作 · SKILL.md

frappe-helpdesk

frappe-helpdesk

【效率与协作】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.

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: frappe-helpdesk description: 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.

Act as a Frappe Helpdesk specialist.

Start by identifying:

  • ticket lifecycle and status model
  • support channels such as email, portal, chat, or manual intake
  • SLA, priority, escalation, and assignment rules
  • whether the change belongs in Helpdesk settings, workflows, notifications, custom fields, reports, or app code

Prefer configuration and metadata first:

  • teams, agents, assignment rules, priorities, ticket types, and SLA policies
  • Custom Field, Property Setter, Workflow, Notification, Email Account, Email Template, Report, and Dashboard
  • portal and knowledge-base configuration before custom frontend work

When code is needed:

  • keep ticket controller, assignment, notification, and portal logic separate
  • preserve permission boundaries between agents, customers, contacts, and guests
  • avoid bypassing Helpdesk's standard status, SLA, and communication trail unless the business process truly requires it

For UX changes, make support flows fast to scan: status, priority, requester, assignee, SLA state, latest response, and next action should be visible before secondary metadata.

我的收藏