The Two-Way Relay Explained — How Anonymous Conversations Work

This article is for informational purposes only.

For decades, anonymous feedback was a one-way drop. Someone submitted a comment, the organizer read it, and that was the end of the exchange. If the comment was vague or incomplete or pointed at something the organizer couldn't quite identify, there was no way to ask a follow-up — not without giving up the anonymity that made the comment possible in the first place.

The two-way anonymous relay solves that problem. It's the single most useful piece of feedback infrastructure built in the last decade for community organizations, and most studio owners and event organizers have never heard of it.

Here's what it is, how it works, and why it changes what feedback can actually do.

The Problem It Solves

Traditional anonymous feedback has a structural dead end. The submitter has information you need. They send it. You read it. It's incomplete. You want to ask a clarifying question — but you can't, because you don't know who they are, and they have no way to receive your question and reply.

So you do one of three things, all bad:

1. Guess at what they meant and act on incomplete information, which often means acting on the wrong problem.
2. Send a follow-up survey to everyone and hope the original submitter responds again, which dilutes the signal and feels like you're broadcasting a private conversation.
3. Ignore the feedback entirely because you can't act responsibly without more context.

None of these gets you to the actual goal: a real conversation with the person who has the information, where they stay anonymous and you get what you need.

How the Relay Works

A two-way anonymous relay sits between two parties and passes messages back and forth, stripping or replacing identifying information in both directions. From the outside, it looks like a normal back-and-forth conversation. Underneath, neither side ever sees the other's identity.

The mechanics in plain language:

1. A member submits anonymous feedback through a form or QR code. The platform assigns the submission an internal ID — a token the organizer can reply to without ever seeing who sent it.
2. The organizer reads the submission and hits "reply." The response is stored against the same internal ID.
3. The submitter receives a notification (typically through a bookmarkable link, an in-app inbox, or an email to an address only the platform sees) that there's a reply.
4. The submitter opens the conversation, reads the reply, and can respond. Their response goes back through the same internal ID.
5. The exchange continues for as long as either side wants. Either side can stop at any time. Neither side ever sees the other's name, email, IP address, or any other identifying detail.

The platform is the intermediary. It knows just enough on each side to deliver messages without exposing that information to the other party.

What This Unlocks

Once a real conversation is possible, the dynamics of anonymous feedback change substantially.

Vague feedback becomes specific. "The instructor felt off" turns into a real account of what happened, when, and who else saw it — because you can ask.

The submitter can ask questions too. If they want to know how their feedback will be handled, they can ask. If they want to follow up a week later, they can.

You can confirm action without breaking anonymity. When you've addressed something they raised, you can tell them — through the relay — that it's been handled and what changed. That closure turns one good feedback experience into many future ones.

Hostile or unproductive submissions can be redirected gently. If someone submits something that's more vent than feedback, you can reply with a thoughtful question that re-engages them productively.

Investigation is possible. If a submission flags a safety concern that needs verification, you can ask what happened, when, and who else witnessed it — without revealing that you're investigating to anyone outside the relay.

Industry guidance consistently highlights the follow-up gap as the single biggest limitation of older systems.¹ The relay closes that gap.

What It's Not

A few clarifications:

It's not deanonymization with extra steps. A properly built relay never exposes the submitter's identity to the organizer, even if the conversation continues for months. Routing information stays internal.

It's not "anonymous to the organizer but visible to the platform's staff." Reputable platforms treat routing metadata as protected the same way message contents are protected. (Worth asking about specifically when evaluating tools.)

It's not a guarantee of perfect anonymity in extreme cases. If a member includes details only one person in the community could plausibly know — "I'm the one who broke the lamp last Tuesday" — the organizer can guess at identity from the content. The relay protects the channel; it can't protect against information the submitter chooses to include.

It's not a substitute for in-person conversation when in-person is appropriate. Some conversations should happen face-to-face. The relay is for conversations that can't happen face-to-face because the person needs anonymity to participate.

When the Relay Matters Most

Most studio owners find the relay matters most in three specific situations:

Reports about specific people. When a member flags behavior by an instructor, staff member, or participant, the relay lets you investigate without exposing the reporter — and update them on outcomes without identifying them.

Sensitive topics with low base rates. Feedback about safety, harassment, or community dynamics often comes from one or two people in a community. The relay lets that small group have an ongoing conversation with you about what they're seeing.

Recurring members with detailed observations. Some members notice things others don't. The relay lets you build an ongoing source of observations from people who want to help but don't want their identity in the loop.

In all three cases, the alternative is either no information or compromised information. The relay is the only way to get the real signal while honoring the structural reason the person stayed anonymous.

What to Look For in a Tool

If you're evaluating platforms, the relay features worth checking on:

• Bidirectional messaging — not just "you can reply to a submission" but the submitter can reply back, and you can continue the thread.
• No identity leakage in metadata. Ask the vendor specifically: does the organizer see IP addresses, email addresses, timestamps that could narrow identity, or any other identifying detail? If yes, the relay is partial.
• Persistent threads so a conversation that pauses and resumes weeks later still works.
• Easy access for the submitter to find their thread again — usually a bookmarkable link or a simple inbox.
• A clear path for the submitter to end the conversation without penalty.

The Tool

TellSafe was built with the two-way relay as a core feature, not an afterthought. Anonymous submissions via QR code or kiosk mode plus a relay that lets both sides have a real conversation without ever exposing identity. It started in the West Coast Swing dance community where the relay turned out to be the difference between feedback that could be acted on and feedback that just sat in a database.

The relay isn't a complicated idea once you see it — it's a postal box with the addresses removed in both directions. What's new is that it's standard in modern feedback tooling, and most organizers who hadn't seen it before find it changes what anonymous feedback can actually do for their community.

Sources

1. Workleap, Anonymous Employee Feedback: Best Methods and Tools (2025). workleap.com