Analyzing Results4 min read

Comments

Per-test discussion threads. Live updates, every role can post (including viewers), and authors can delete their own comments.

Comments

Per-test discussion threads with live updates. Every account member — including viewers — can leave comments; authors can delete their own at any time.

Every test has its own comments panel on the test detail page. Use it for hypothesis discussions while a test is running, interpretations once results come in, or just a record of decisions made. Comments are per-test, so each thread stays focused on one experiment.

Comments are intentionally the one place where every role can take an action — viewers included. Review is a collaborative activity, and viewers are usually the reviewers, so they can react and ask questions even though they can't edit the test itself.

Who can do what

Posting a comment

Available to every role: owner, admin, member, and viewer. Comments are the one collaborative action viewers can take.

Deleting a comment

Only the original author can delete their own comment. Admins and owners can't remove other people's comments through the dashboard.

Editing

Not supported. Delete and repost if you need to change something significant. For small typos, most teams just leave them — comments are conversational.

Live updates

The comments panel subscribes to a WebSocket channel for the test, so new comments and deletions appear in everyone's view immediately — no refresh required. Your own comments also appear through the same channel; you don't see a momentary form reset before the comment shows up.

What's not supported (yet)

  • @-mentions — tag teammates and ping them. Today, write the name in plain text; they'll see it when they next open the test.
  • Markdown / rich text — bold, links, code blocks. Plain text only for now.
  • Editing — see above; delete and repost if needed.
  • Threaded replies — comments are a flat list ordered by post time.
  • Slack/email notifications — the Notifications system covers test lifecycle events, not comments. We're tracking comment-to-Slack as a future improvement.
  • Inclusion in shared report links — shared reports are read-only and externally-facing; comments stay private to the account.

Comment etiquette

State your hypothesis when you start. A comment at launch explaining what you expect and why gives the team a clear reference point when results come in.

Record the decision when you complete. A short note explaining why you shipped, didn't ship, or extended the test makes the comments thread a real experiment log.

Use comments, not test descriptions, for conversation. The test name, hypothesis, and description are dedicated fields — keep them as the authoritative statement of the experiment. Comments are where teammates respond and discuss.

Delete instead of edit. Since edits aren't supported, posting a correction below your original comment is fine — but for clarity, you can also delete your original and post a fresh one. Either is normal.

Frequently asked questions

Quick answers to the questions teams ask most about this part of Otter A/B.