The Speak-up inbox and case status
One row per anonymous report that carries a return code, a coarse status you set, and an acknowledgement count, on Business and Enterprise or the trial preview.
On this page
The Speak-up inbox is a tab on a poll that lists every anonymous report whose reporter took a return code, with a status you set and the conversation so far. It exists so a compliance or HR lead can see at a glance which reports are still waiting to be acknowledged, and can move each one through received, acknowledged, under review and closed without ever learning who wrote it. Use it on an always-on speak-up channel, or on any poll with a written question where replies are turned on.
The reporter holds the only key to their side of the conversation. We can't recover it, look it up, or link it to a person. The inbox is built entirely from what your own browser decrypted.
When to use it
- You run an internal reporting channel and need to track acknowledgement and feedback per report.
- An obligation, contractual or regulatory, asks you to show that reports were handled within a time.
- Several people share the job of reading reports and need one place that shows status.
For how a reply actually works, from the return code to the encrypted thread, read Replying to an anonymous report. This page covers the inbox and the status values.
Where it is
Open a published poll that has a written question. The Speak-up inbox tab sits beside Results. At the top is the Anonymous replies switch, which offers each respondent a return code from that point on; answers already collected have no code and can't gain one. If public results are also on, a warning appears here, because a public results link lets its holders read reporters' follow-ups.
Below that, the inbox fills in once results are open, which means at least three responses. Under the floor there is nothing to read and nothing to acknowledge.
What a row shows
One row per report that carries a return code. A response that answered two written questions is still one row, because it's one reporter and one conversation.
| Part | What it means |
|---|---|
| Week badge | the week the reporter's browser recorded |
| Age | "This week", "1 week ago", "3 weeks ago" |
| Status | Not opened yet, or the value you set |
| Thread | the reporter's follow-ups |
| Composer | reply to this report |
There is no date anywhere, only a week, and it's the reporter's own, sealed inside their response. We hold no submission time for a report, so a week is the most precise thing anyone can honestly say.
Your own earlier replies appear as "You replied" with a note that the text is encrypted to the reporter's return code and can't be shown back to you. That's a property, not a gap: nobody holding a shared results link can read what you wrote either.
Case status
Status is one of four coarse values. It's the one thing about a report the server can see in plain text, because it holds no content and lets the reporter glance at whether there's news.
| Status | When |
|---|---|
| Received | the default before anyone acts |
| Acknowledged | you've seen it |
| Under review | someone is looking into it |
| Closed | handling has finished |
Who changes it. Anyone in the workspace who can open the poll's results can set status from the inbox or from the report's written answer on the results tab. Reporters can read status on the reply page and can't change it. Sending a reply marks a report acknowledged on its own, so there's no state where you've answered someone and the record says you haven't.
The acknowledgement count. A chip above the rows says "N reports awaiting acknowledgement, oldest from week 2026-W36", counting reports nobody has opened plus those still at Received. When there are none it reads "Every report here has been acknowledged."
Return codes
A return code is 26 characters in five groups, drawn in the reporter's browser before they submit. It's the key to their side of the conversation, not a lookup token, which is why we can't recover a lost one. The reporter enters it on the reply page, on a form, and it's never carried in a link: URLs end up in browser history, proxy logs and chat previews, and a code that leaked that way would let someone else read the reply.
Until you've opened a report, the reply page tells the reporter "Not read yet. Check back later." There's no notification, because a notification needs an address and collecting one would undo the anonymity the channel exists for. Tell people when to check back.
What respondents see
A checkbox before submit, ticked by default on a poll with replies on: get a return code so we can reply. The code is shown once after submitting, with copy, download and print. Later, the reply page shows the status you set and anything you've written, and lets them send a follow-up. Nothing on their side shows other reports or anything about the poll's results.
Why the statuses exist
Directive (EU) 2019/1937 asks organisations above a size threshold to acknowledge a report within seven days and give the reporter feedback within a reasonable period not exceeding three months. Acknowledgement and feedback to an anonymous reporter are impossible without a route back, and a coarse status per report is the smallest record of handling that fits inside the anonymity model.
Not legal advice
This is a description of product behaviour, not a compliance opinion. InviziPoll isn't a regulated or certified hotline provider, and whether a setup meets an obligation in your jurisdiction is a question for your own counsel.
Two of the clocks are yours to run. We hold no submission time, so the seven days and three months are counted from the week the reporter declared, by you. And acknowledgement only reaches a reporter who kept their code and comes back.
Limits and gates
- Business and Enterprise, and any workspace trying the Business features preview during a trial. On other plans the tab shows a card saying the inbox is on Business and Enterprise, with a link to plans. Turning replies on at all needs an active plan or trial.
- The gate is your entitlement, not your plan name. A trial workspace with the preview on sees the inbox.
- No case management: no assignment, no due dates, no evidence uploads, no export for counsel.
- A conversation caps at forty messages, each at roughly twenty-four kilobytes of text.
- Conversations are deleted with the poll's responses under the poll's retention setting. Set retention long enough to cover any feedback period you've promised.
- Follow-ups aren't authenticated. Anyone who can decrypt the poll's responses, including a holder of a public results link, can read a reporter's follow-ups and post into an open thread. Keep a speak-up poll off public results.