Comments
Comments: pinned feedback
In the builder (you, the developer)
- Open any page in your builder, Bricks (URL contains
?bricks=run), Elementor, or the Gutenberg editor. - The Reviso panel docks bottom-right.
- Click Comment → click any element on the page → a pin drops.
- Type your comment → Enter.
In review mode (your client)
The same overlay appears on the public front-end when the page is accessed via a review token. Clients don’t see anything Reviso-related on normal page loads, only via review URLs.
Status workflow
Every comment has one of three statuses:
| Status | When |
|---|---|
| Open | Default, needs attention |
| In progress | You’re actively working on it |
| Resolved | Done, kept for the audit trail |
Filter the sidebar by status using the chips at the top.
Threads
Click any pin → opens the inline thread. Reply, mark resolved, assign to a teammate, or jump to the element it’s attached to. Threads keep the conversation visible without cluttering the main feed.
Element anchoring
Pins survive page edits via three fallback strategies:
- DOM ID, the builder’s element ID (Bricks
brxe-*, Elementordata-id, or a Gutenberg block ID), most stable. - Content hash, the element’s text or src URL.
- Position, relative coordinates within the parent.
If you delete an element, its pin shows “Element removed” but stays in the sidebar so the comment isn’t lost.
Assignees (Pro)
Click a comment’s Assign menu → pick a WP user. They get a notification email (if enabled) and you can filter the sidebar by assignee.
Rounds (Pro)
Open the Round dropdown to bump all currently-open comments into the next round. Useful for “round 2 of feedback” workflows.
Viewports
Switch desktop / tablet / mobile from the sidebar, comments are filtered to the viewport they were left on.
Status changes
Click the status chip on any comment → switch between Open / In progress / Resolved. Bulk-resolve a thread by clicking the status on the parent comment.
Deletion
Hover any comment → Delete. Confirm twice (a mini-confirm, prevents accidental clicks). Deleted comments and their replies are gone for good.
Internal feedback (your team)
When you are logged in with edit access, a Feedback button appears on your live pages so your team can pin private notes the client never sees. Internal notes are badged Internal. Each teammate can turn their own button on or off from the Internal feedback button toggle in the Reviso admin-bar menu.
Internal feedback works on every kind of page, not just single posts and pages: it also appears on listing and archive pages (a custom post type archive, a category or tag, an author or date archive), the blog index, and search results. Notes left on a listing page are kept with that specific page (for example, each category keeps its own set), so they stay where you left them.
Suggest edits on the page
Reviewers can propose new wording right where it sits, like a tracked change. Switch the cursor pill from Comment to Suggest, click a piece of text, and type your version. The page reflows live as you type, so everyone can see how the change shapes the layout.
Each suggestion becomes a card with the before and after text. Your team clicks Accept & apply to write the change straight into the page (applying edits to Bricks is a Reviso Pro feature) or Reject to dismiss it. Every applied edit takes a snapshot first, so it is always revertable, and the snapshot records who applied it.
By default only your team can apply an edit. You can let a client apply the suggestions they made themselves, either as a site default (Settings, Comments) or per review on the review’s edit screen. A reviewer can only ever apply their own suggestions, never anyone else’s.
Minimise the panel
Collapse the comments panel to a thin bar (use the minimise button in its header, or double-click the header) to see the page clearly while you keep commenting. Reviso remembers your choice for that browser, and the bar shows how many open comments are waiting. The panel also opens beside the spot you click, and remembers where you drag it.