Reporting channels & reporter experience
How this is scored
The intake side: how a reporter actually submits — web form, anonymous dialog, phone/voice, languages, accessibility — and whether anonymity survives first contact.
0 — A web form that is an email in disguise: no anonymous route, no way to reach the reporter afterwards.
3 — An anonymous form exists but the dialogue ends there — no secured mailbox for follow-up questions, few languages, desktop-only.
5 — Anonymous two-way dialog via a protected mailbox, a usable set of languages, mobile-friendly; voice or phone intake missing or an add-on.
8 — Multiple channels (web, voice message or hotline, QR entry points), broad language coverage with translation support, accessibility considered, and the anonymous dialog is first-class rather than bolted on.
10 — Intake engineered around the frightened reporter: every channel anonymous-capable, dozens of languages, WCAG-conscious, no app install or account required, and the vendor documents how the reporter's identity is kept out of the channel itself.
The Security Auditor
Phone, web, and mobile intake runs 24/7/365 with a real hotline behind it — under 1% call abandonment, 91% caller satisfaction — and anonymous two-way follow-up via password-protected dialog is core rather than bolted on. But we found no public information on language coverage, accessibility, or how reporter IP and device metadata are kept out of the channel, so anonymity surviving first contact rests on assertion alone. 1