Area: mobieusHelp (audit p7) · Surface: /help/agent, /help/agent/queue/{slug}, /help/agent/ticket/{reference} (+ reply/status/assign) · Dimension: documentation · Severity: major
The agent-facing workspace (dashboard, per-queue lists, ticket detail with reply composer, internal notes, status changes, assignment, inline AI hooks, canned-response insertion) is shipped and live, but the agent playbook is explicitly marked '(coming)' and does not exist. Agents have no how-to for the surface they use every day, and it is not discoverable via wiki search.
Evidence
Code: platform/src/Controllers/Helpdesk/AgentController.php defines dashboard() (line 83), queue() (line 105), ticket() (line 131), submitReply() (line 189), submitStatus() (line 237), submitAssign() (line 259) — the full agent triage/reply/escalate workflow. Wiki: the admin guide ('What's NOT in this guide') states verbatim: "Agent workflow — how to triage, reply, escalate. That's the agent playbook (coming)." `curl 'https://support.mobieus.io/know/search?q=helpdesk+agent'` returns `No results`. No /know/*agent* article appears in /know/index.
Suggested fix. Write the 'agent playbook' article (e.g. /know/mobieushelp-agent-guide): triage from the dashboard/queues, the reply composer + internal notes, inserting canned responses, changing status/priority, assignment, using the inline AI hooks. Remove the '(coming)' placeholder in the admin guide and link the new article.
Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.
Patrick Bass
@mobieus