Draft help-centre articles automatically from resolved tickets and keep a human in charge of publishing
A merged helpdesk change that, when a ticket is resolved, asks an AI whether other customers are likely to ask the same thing and writes a draft article for managers to review if none exists.
Evidence: The source shows its work: steps, screenshots, code or data you can inspect.
The business problem
Support teams answer the same questions repeatedly but rarely find time to turn answers into help-centre articles that deflect future tickets.
What was tried
On a ticket update, the AI reads the customer's question and the team's answer and decides whether it is likely to recur. If no published article or earlier draft covers the topic, it writes a draft article in a general category and reminds the managers to review it. Drafts are never published automatically, the prompt forbids customer names and data, and each ticket produces at most one draft, tracked by a source-ticket field. It is switched on by a setting and needs an AI key.
What was reported (not reported)
No results are reported. The change was merged on October 1, 2026 with five checks passing.
Limitations
The page does not say which AI model or cost is used, how draft quality is tested, how the check for existing coverage works, how failures are handled or whether tickets resolved before the merge are processed. It has no listed reviews and parts of the page failed to load.
What you need
An open-source helpdesk that includes this change, an AI provider key, and managers who review drafts.
Sources
- GitHub (tbocloud/helpdesk pull request) ↗ Code repository, published October 1, 2026
Source published: October 1, 2026. Last reviewed here: October 11, 2026. Spot a mistake? Tell us.
Related workflows
Roll out OpenClaw for inbox triage, meeting notes and CRM updates in phases with approvals and isolation
An infrastructure vendor's guide sets out business uses for OpenClaw and a phased rollout: pilot a low-risk workflow, add guardrails and approvals, then scale once value and safety are shown.
Measure true resolution, not just deflection, for an AI support agent with an escalation policy
A small open-source evaluation shows a naive support agent deflecting every ticket while resolving about half, and a policy-gated agent that deflects fewer but resolves what it handles.
Draft help-centre-cited support replies and propose refunds that a person must approve
An open-source support workbench classifies tickets into three tiers, drafts replies that cite help-centre articles, reads billing data in read-only test mode, and only proposes refunds that need a named approver.
Deflect support tickets only when a calibrated confidence score is high, and queue the middle band for human review
An open-source ticket deflection engine escalates risky tickets directly, answers procedural ones by rule, and uses retrieval over documentation with three confidence bands for auto-reply, human review and escalation.