Comments

Email review usually happens everywhere except the email. A screenshot pasted into Slack, a PDF marked up in another tool, an approval buried in a thread nobody can find two weeks later. Comments keep that conversation on the email itself. Click what you want to talk about, leave a note, and anyone else in your organization sees it in the same place. If you have reviewed a Google Doc or a Figma file, you already know how this works. Anyone in your organization can comment. There is no reviewer role to assign and no permission to grant first.

​

Two Ways to Leave One

On the whole email. Click the email on the canvas, then click the comment icon in the email’s toolbar, next to Add to chat. Hover it and it reads “Comment on this email”. On one section. Click any section of the email, then click the comment icon at the right end of the section toolbar, past the formatting controls and Prompt. Either way, a message box opens. Type your comment and send it with the arrow. The comment anchors to whatever you picked, so the next person sees it next to the thing it’s about.

​

Close or Resolve a Thread

A thread has two controls at its top right, and they do different things:

• X closes the comment view. The thread stays where it is, unread and unresolved.
• Check resolves the whole thread, not the single comment you’re looking at. Use it once the feedback has been acted on or answered.

​

Tag a Teammate

Mention a teammate in a comment to pull them into the conversation. Brew emails them a link that opens the email at your comment, so they land on the exact element you’re asking about instead of hunting for it.

​

Reply in the Thread

Comments are threads, not one-off notes. Replies stay attached to the original comment, and everyone in your organization sees the same threads on the same email. That makes the email the record of what was asked and what was decided.

​

A Comment Is a Note for People

Commenting doesn’t change the design. A comment is feedback for your team, and it sits alongside the email rather than editing it. To actually make the change, ask for it in chat or edit inline. The Prompt Guide covers how to phrase an edit so you get what you meant.

​

Comments Are an App Surface

Commenting works in the Brew app only. There is no MCP tool or Public API endpoint for comments today, so an agent can’t read or post them. The rest of a review routine does have an agent path. Audit Email Accessibility and Preview in Real Inboxes both run from chat, an agent, or code.

​

Where It Fits in a Review

Comments cover the judgement calls: tone, offer, whether the hero image earns its place. Run the mechanical checks separately, because a person shouldn’t be the one catching a contrast failure or a broken layout in Outlook. A workable order is preview across clients, audit for accessibility, then open it for comments and send yourself a test. QA an Email Before a Big Send walks the full routine.

​

Need Help?

Our team is ready to support you at every step of your journey with Brew. Choose the option that works best for you: