Case No. 02 · Regional News
The Cape Argonaut
- 62%
- 98.9%
- 169ms
Deploy: Ghost + REST API. One full-time community manager reassigned from triage to reader correspondence.
Field Notes · Publisher Moderation
Five deployments from publishers who refused to let their comment sections rot — each one measured against the same three numbers: cost reduction, spam-block rate, and moderation latency.
Flagship Deployment · Case No. 01
The Meridian Daily — a fictional national daily averaging 38 million monthly unique readers — migrated its comment platform to Comment Castle in early 2024. Within one quarter, the newsroom cut its moderation cost per article by 73%, blocked 99.4% of inbound spam, and shipped first-pass moderation decisions in under 180 milliseconds.
The Meridian Daily's comment section had quietly become a liability. A four-person moderation team was working overnight shifts to clear the weekend backlog, while a rules-based spam filter let through roughly one in every forty abusive comments. Editorial leadership wanted to grow reader engagement without growing the trust-and-safety payroll.
Comment Castle was wired into the existing CMS in 11 days using the documented WordPress integration. The Toxicity Score v3 model was tuned to the newsroom's house style guide; a custom allowlist protected reporter names and subject-matter keywords from false positives.
Within 90 days of cutover, The Meridian Daily reported a 73% reduction in moderation cost per published article and a 99.4% measured spam-block rate against its pre-migration baseline. Average moderation latency settled at 174 milliseconds — the fastest in the publisher's own internal benchmark across three competing vendors.
"We stopped thinking about moderation as a cost center the day the backlog disappeared. Our editors started reading the comments again — and so did our readers."
— Composite quote, attributed to a fictional Managing Editor at The Meridian Daily.
Supporting Cases · Cases No. 02 – 05
A reader from any vertical should be able to scan this list and find a peer. Each account below is a clearly labeled fictional composite built from aggregated customer patterns.
Case No. 02 · Regional News
Deploy: Ghost + REST API. One full-time community manager reassigned from triage to reader correspondence.
Case No. 03 · Sports Media
Deploy: Drupal + Webhooks. The toxicity-score threshold auto-tightens during live windows and relaxes post-game.
Case No. 04 · SaaS Community
Deploy: Discourse one-click integration. Old threads re-scored retroactively to clear a five-year backlog.
Case No. 05 · Independent Journalism
Deploy: WordPress + documented API. Custom lexicon added 3,200 literary and political terms to the toxicity model.
On the Platform · Publisher Categories
The wordmarks below are representative publisher categories, not named customers. All deployment identifiers are fictional composites.
3,400+ active publisher sites since 2019. Combined reach across the platform: 180M monthly unique readers.
Step Inside · Live Walkthrough
A solutions engineer will load a sample of your recent threads into a sandboxed Comment Castle environment, run them through Toxicity Score v3 live, and show you the moderation decisions your team would have seen yesterday. No slides.