Patrick Bass Area: Admin deep-dive (trust/safety) (audit p15a) · Surface: /admin/moderation, /admin/appeals, /admin/audit (whole trust/safety surface) · Dimension: Competitor-gap feature (#2) · Severity: major
Every helpdesk leader (Zendesk Explore, Intercom reports, Help Scout reports) ships agent productivity dashboards: tickets handled per agent, median first-response and resolution time, SLA-met percentage. Skool and Circle expose admin engagement/activity views. Mobieus stores resolved_at/resolved_by on every report and has an append-only audit log, so the inputs are present — but a tenant super-admin has no way to answer 'how fast is my mod team clearing the queue, who is carrying the load, is anything aging out?' That is the single most-requested operational view for any team running moderation at scale, and it is also what justifies the Pro/Creator-Plus tier to a buyer evaluating us against Zendesk.
Evidence
`grep -rin 'resolution.*time|avg.*resolve|time_to_resolve|mod_performance|moderator.*stats' platform/src/Controllers/` returns nothing. AdminModerationController@index surfaces a raw last-25 mod-action feed (recentModActions, lines 110-121) but computes no aggregates. AdminPerformanceController only reports HTTP latency (performance_logs), not moderation outcomes. reports has resolved_at + resolved_by (schema.sql:6762/6765) so the data to compute time-to-resolution exists but is never aggregated.Suggested fix. Add a /admin/moderation/metrics view: median + p90 time-to-resolve over a date range (TIMESTAMPDIFF(resolved_at, created_at)), open-vs-resolved counts, per-resolver throughput grouped by reports.resolved_by, and an aging buckets table (open >24h / >72h). All computable from the existing reports + audit_log tables with no schema change.
Filed by the automated tenant-app audit and adversarially evidence-verified. Status: verified. Open — not yet actioned.
Patrick Bass
@mobieus
