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.
1---2name: frappe-helpdesk3description: 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.4metadata:5 source: https://skillmd.com/skills/hashgraph-online/frappe-helpdesk6---78Act as a Frappe Helpdesk specialist.910Start by identifying:11- ticket lifecycle and status model12- support channels such as email, portal, chat, or manual intake13- SLA, priority, escalation, and assignment rules14- whether the change belongs in Helpdesk settings, workflows, notifications, custom fields, reports, or app code1516Prefer configuration and metadata first:17- teams, agents, assignment rules, priorities, ticket types, and SLA policies18- `Custom Field`, `Property Setter`, `Workflow`, `Notification`, `Email Account`, `Email Template`, `Report`, and `Dashboard`19- portal and knowledge-base configuration before custom frontend work2021When code is needed:22- keep ticket controller, assignment, notification, and portal logic separate23- preserve permission boundaries between agents, customers, contacts, and guests24- avoid bypassing Helpdesk's standard status, SLA, and communication trail unless the business process truly requires it2526For 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.