You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Would a Frappe Helpdesk agent plugin be welcome?
#3498
Hi Frappe Helpdesk team - would you be open to a small PR that packages common Helpdesk agent workflows as an installable plugin?
What I have in mind:
a plugins/frappe-helpdesk-operator/ package with Codex/Claude-compatible plugin metadata
one focused Skill inside the plugin for safe support workflows: ticket triage, SLA-risk review, customer-response drafting, knowledge-base lookup, escalation planning, and approval-gated updates
a few JSONL eval cases that verify the agent reads ticket/customer context first, separates evidence from recommendations, asks for approval before mutating tickets, and avoids exposing ticket contents, customer data, tool arguments, or model outputs in telemetry
I am using "plugin" as the installable package and "Skill" as a focused workflow inside that plugin. The goal would be to make Helpdesk easier to connect to agent workspaces while keeping customer-support data boundaries explicit.
If this sounds useful, I can open a scoped PR with docs/metadata/evals only and follow any preferred repo convention.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Hi Frappe Helpdesk team - would you be open to a small PR that packages common Helpdesk agent workflows as an installable plugin?
What I have in mind:
plugins/frappe-helpdesk-operator/package with Codex/Claude-compatible plugin metadataI am using "plugin" as the installable package and "Skill" as a focused workflow inside that plugin. The goal would be to make Helpdesk easier to connect to agent workspaces while keeping customer-support data boundaries explicit.
If this sounds useful, I can open a scoped PR with docs/metadata/evals only and follow any preferred repo convention.
All reactions