frappe-helpdesk
SkillDocs & knowledgeFrappe 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.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the frappe-helpdesk skill
What this skill tells your AI
The instructions your AI receives, as published by dkm0315/frappe-agent in skills/frappe-helpdesk/SKILL.md and read by ahel’s review.
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, andDashboard- 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.
Signals
- GitHub stars
- 24
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
frappe-helpdesk- Source
- github.com/dkm0315/frappe-agent