Claude reads the questions of the product, period and selection above and groups the ones that ask the same thing — with what to change in the product so fewer people need to ask. It takes up to a few minutes, and runs only when you press the button.
What the deep investigations found should change in the product — guide updates, bugs and features — each once,
however many conversations led to it. To do, done (live) and dismissed. They are approved in Claude Code on the owner's PC
(/helpdesk-todo): Claude makes the change, puts it on the product's test site, and after the owner's OK puts it live.
Each conversation with everything that happened to it: the questions and answers, the user's Resolved / Not resolved, their reports (GitHub issue, AI triage, contact) and the deep investigation — Not resolved conversations and reports are looked into by Claude Code on the owner's PC (every 30 minutes while it is on), which reads the product's code, checks its answer on the test site and sends it to the user. Open one to see it all in order. Copy Not resolved for the guide copies every Not resolved conversation as Markdown with a request to improve the guide.
To add a product, tell its developer (or their Claude Code) to read
and follow it, and give them the linking password
(CONNECT_PASSWORD in this help desk's .env). It links itself and gets its secret at once.
Linking is switched off: set CONNECT_PASSWORD in .env to use the Connect page.