Reporting channels & reporter experience
How this is scored
The intake side: how a reporter actually submits — web form, anonymous dialogue, phone or voice message, languages, accessibility — and whether anonymity survives first contact.
0 — Not a reporting channel; a general contact or survey form with no anonymous route and no way to reach the reporter afterwards.
3 — A web form that accepts anonymous reports, with a case number or access code the reporter can use to check the report later.
5 — Anonymous two-way dialogue through a protected mailbox or access code, the reporting page in several languages, and use on mobile devices without an app or account.
8 — Several channels (web, voice message or phone hotline, in-person meeting requests, QR or intranet entry points), broad language coverage with translation of messages, accessibility addressed, and voice distortion or another anonymity measure for spoken reports.
10 — Intake engineered around the frightened reporter: every channel usable anonymously, dozens of languages, WCAG conformance stated, no app or account required, and the vendor documents how the reporter's identity is kept out of the channel itself.
The Skeptic
What is documented is a web form reachable through a link on the customer's site, taking anonymous or named reports with multilingual, flexibly configurable forms and a secure feedback channel, plus an anonymous mailbox protected by password and ID for follow-up questions — that is the two-way anonymous pattern. But "guaranteed anonymous" is a promise, not engineering: I found no public information on the number of languages, mobile use without an app or account, any phone or voice channel, or how reporter identity is kept out of the channel itself. And the vendor's own privacy policy discloses Google Analytics, LinkedIn and US-hosted Calendly on its website, with no statement reconciling that with metadata handling at the reporting page. 6 8 9 15 5