This article is for informational purposes only.
You set up an anonymous feedback channel. It works — people start sending real, useful feedback for the first time. Then a comment lands that's interesting but vague: "The new instructor felt off." You want to know more. Which instructor? "Off" how? When?
This is the moment most feedback programs quietly destroy themselves. The organizer, well-intentioned, starts trying to figure out who sent the message. Or they post about it publicly in a way that makes the submitter regret commenting. Or they confront the wrong person. Or they confront the right person but in a way that makes it obvious how they found out.
Any of these breaks the implicit contract of anonymous feedback. Once that contract breaks, the channel is dead. Members notice — and they tell each other. The next round of feedback drops to zero or fills with intentionally vague comments because nobody trusts the system.
Here's how to follow up productively without crossing the lines that end the program.
The Line You Can't Cross
The core rule of anonymous feedback: never try to identify the person who submitted it.
Not just "don't tell anyone who they are" — don't try to figure it out at all. Not by handwriting analysis. Not by inferring from timestamps and class attendance. Not by asking around. Not by posting "thanks to the person who mentioned X" in a way that lets people guess. Not by responding in a way that only one specific person would understand.
Industry guidance is consistent: "breaking anonymity once destroys trust forever."1 If even one person concludes their feedback was traced back to them, the channel becomes useless — not just for that person, but for everyone they tell.
Every follow-up move you make has to be possible without ever knowing who you're talking to.
The Two-Way Relay: How to Ask Without Identifying
The single biggest tool here is a two-way anonymous relay. Modern feedback platforms support this directly: when someone submits feedback, you can reply to that submission, and they can answer back, all through a system where neither side sees the other's identity.
This solves the "vague feedback" problem. The "new instructor felt off" submission becomes:
You: Thanks for raising this — can you tell me more about what felt off?
Them: Generally fine teaching the moves, but made a comment during the workshop about beginners "wasting his time." A few of us heard it.
You: Was this during the 7pm Tuesday class? Did anyone say anything to him afterward?
Them: Yes, Tuesday. Nobody said anything that I saw.
Now you have what you need. Specific class, specific incident, specific behavior. And throughout the exchange, you never knew which member you were talking to, and they could end the conversation at any point.
This is structurally different from sending a follow-up survey to everyone. The relay lets you have a targeted conversation with the person who has the information, not a broadcast back to the whole community. (More on the mechanics in The Two-Way Relay Explained.)
The Moves That Quietly Break Trust
Even with the best relay tool, several common follow-up moves damage trust in ways that aren't obvious until the damage is done.
Don't post about the feedback publicly before acting on it. "Someone mentioned the new instructor isn't working out — anyone else feel that way?" sounds like consultation but reads to the original submitter as exposure. They didn't volunteer to start a public conversation.
Don't ask relay questions only one person could plausibly answer. "Were you the one in the back of the 6pm class last Thursday?" is functionally a deanonymization attempt. Even if you don't mean it that way, the submitter will read it that way.
Don't confront the subject in a way that reveals how you found out. If someone reports an instructor's behavior anonymously and you walk up and say "I heard you said something inappropriate Tuesday night," the instructor will work out where it came from. Frame it differently: "I'm doing a check-in with all instructors about workshop tone."
Don't promise specific outcomes you can't guarantee. "Thanks for sharing this — I'll fire him by Friday" depends on facts you don't have. Investigate first. Promise a process, not an outcome.
Don't get defensive. When feedback is critical, the impulse to explain why it's wrong is strong. Resist it. The relay is for gathering information, not for arguing. If you push back, they stop responding — and you lose the only source of information you have.
When the Feedback Is About a Specific Person
The hardest case is when feedback names or strongly implies a specific person — instructor, staff, participant. You can't ignore it. You also can't act on a single anonymous report as verified fact.
A workable sequence:
- Acknowledge through the relay. Thank the submitter, ask clarifying questions, signal you take it seriously.
- Investigate independently. Look at attendance, watch the next class, ask staff who were present — without revealing what you're investigating or where the question came from.
- If the pattern checks out, address the subject directly. Don't say where it came from. Frame it as something you noticed.
- Update the submitter through the relay. Even "I looked into this and I'm taking the following steps" — without details that compromise anyone — closes the loop.
The submitter doesn't need to know everything you did. They need to know something happened. Silence after a serious report is what makes people stop reporting.
When You Genuinely Can't Act
Sometimes feedback is real but you can't act on it the way the submitter wants. A complaint about an instructor you've decided to keep. A request that conflicts with the venue contract. A criticism you've already heard and decided against.
Tell them. Through the relay, in plain language: "I hear you on this. Here's why we're not changing it right now: [reason]. I'll revisit it in [timeframe]." That's better than silence. Silence makes people assume you didn't read it. A genuine "no, and here's why" tells them you read it and weighed it. They may disagree, but they won't conclude the channel is theater.
The Public Side of Closing the Loop
Some feedback warrants a public follow-up — not naming the submitter, not quoting the message, but acknowledging that a change happened because of community input.
"A few people mentioned the morning class music was too loud. We're adjusting the speaker placement starting next week."
The submitter sees their feedback led to action without being identified. Every other member sees that anonymous feedback in this community actually changes things — which makes them more likely to give feedback next time. This is how a feedback program compounds.2
The line: keep public follow-ups to changes that affect the whole community. Don't publicly announce follow-ups on personal complaints (about specific staff, specific participants, specific incidents) — those stay in the relay and result in private action only.
The Tool That Makes This Possible
Most of these moves require a feedback platform that supports two-way anonymous messaging. Without that, follow-up is either impossible (you can't reach the submitter) or breaks anonymity (you have to identify them to reply).
TellSafe was built around this — a two-way anonymous relay lets you respond to any submission, and the submitter can reply back, without either side seeing the other's identity. It started in the West Coast Swing dance community and has been picked up by other organizers who hit the "vague feedback I can't do anything with" wall.
Whatever platform you use, the discipline is the same. Anonymous feedback is a contract: they trust you not to try to find out who they are, and in exchange you get information you couldn't get any other way. Honor it and the channel keeps producing. Break it once and the channel is over.
Sources
- JellyForm, Anonymous Suggestion Box: The Complete Guide to Building Trust Through Honest Feedback (April 2026). jellyform.com
- Lattice, Best Practices for Conducting Anonymous Employee Surveys (January 2026). lattice.com